fix(code-context): accept bound create-resume rounds in 0.2.8

[alphali]

When TRD creation pauses for more evidence, the original connection may resolve to a new pre_create Round. The helper rejected it solely because its DQ code differed, even with the original connection_round_code and matching workspace. Accept that server-bound successor while retaining both checks and writing submissions against the actual successor ID.

Bump the plugin and all host manifests to 0.2.8 so installed clients can receive the fix. Paired with TRD #507, the post-merge fixes for #480; the shared contract is getdoable/trd:docs/change-sets/pre-create-code-context-toggle.yaml. Older backends retain their existing behavior.

Validation:

• npm test: release verification and 3 helper tests passed, including rejection of missing/wrong connection IDs and different workspaces.
• Disposable PostgreSQL/PostgREST + real TRD API/repository + this helper: prepare, answer, create, and two consecutive create-resume rounds passed; ordinary follow-up flows passed too.
• The same create-resume replay failed against released 0.2.7 with Doable returned a different pre-create round code.
• Authentication dependencies and TRD model/session storage were fixtures. No live coding-agent host, model generation, production mutation, or installation update was performed.