Prepare open-scaffold@0.34.0 release sync

[graphanov]

Summary

• Prepare the open-scaffold@0.34.0 release-sync candidate from current main without performing any release action.

Scope

• Bumps package metadata to 0.34.0, adds the v0.34.0 changelog candidate entry, records the repo-native plan/evidence note, and refreshes the live-corpus hash test for those records.

Out of scope

• No merge, npm publish, workflow dispatch, tag, GitHub Release, branch protection, settings, secrets, or post-publish smoke was performed.

Verification

• ./verify.sh --strict → 10 pass / 0 fail / 0 warn; npm test -- --run → 51 files / 625 tests passed; npm run build → passed; npm pack --dry-run --json → open-scaffold@0.34.0, 228 files.

Risk

• Release-prep metadata touches package version and .osc release evidence by issue Release open-scaffold@0.34.0 — ambient capture trust package sync #239 scope; publish/release follow-through remains owner-gated.

Linked issue

Refs #239 — keep open for owner-gated npm publish, tag/GitHub Release, and post-publish proof after review/merge.

Authority boundary

Draft PR only; no merge, publish, release, tag, workflow dispatch, settings, branch protection, force-push, or secrets authority used.

[graphanov]

Status: blocked — draft promotion is blocked by release-gate path changes.

Evidence:

• PR Prepare open-scaffold@0.34.0 release sync #240 head 52be6fb is mergeable/CLEAN with CI pass, zero review threads, and local verification passing: ./verify.sh --strict && npm test -- --run; npm run build. Diff includes package.json:version, package-lock.json:version, and .osc/releases/**, which are configured forbidden paths.

Needed: Explicit owner decision to move this release-sync PR out of draft and request independent review despite those forbidden-path changes. Merge, publish, release, tag, and workflow-dispatch remain separate owner gates.

[graphanov]

Status: blocked — draft promotion and Codex review are owner-gated by configured release-path changes.

Evidence:

• PR Prepare open-scaffold@0.34.0 release sync #240 head 52be6fb is MERGEABLE/CLEAN; CI is green; review threads are zero; local configured verification passed (./verify.sh --strict && npm test -- --run) and npm run build passed. The diff changes package.json/package-lock.json versions and adds .osc/releases/**, which are configured forbidden paths. Issue Release open-scaffold@0.34.0 — ambient capture trust package sync #239's latest proceed-intent comment is useful release context, but it does not explicitly authorize moving this draft PR to ready or requesting review despite those forbidden-path changes.

Needed: Owner approval with exact scope, for example: APPROVE JOHN-LOMEIN PR #240 DRAFT PROMOTION: mark PR #240 ready and request Codex review for head 52be6fb despite package version and .osc/releases path changes; do not merge, publish, tag, create a GitHub Release, dispatch workflows, force-push, change settings, or touch secrets.

[graphanov]

APPROVE JOHN-LOMEIN PR #240 DRAFT PROMOTION: mark PR #240 ready and request Codex review for head 52be6fb despite package version and .osc/releases path changes; do not merge, publish, tag, create a GitHub Release, dispatch workflows, force-push, change settings, or touch secrets.

[graphanov]

Status: ready for review on approved draft-promotion gate.

Evidence:

• Owner approval comment authorizes draft promotion and Codex review for head 52be6fb; merge/publish/release/tag/workflow-dispatch remain excluded.
  GitHub: MERGEABLE/CLEAN, CI success, zero review threads.
  Local: ./verify.sh --quick --quiet; git diff --check origin/main...HEAD; ./verify.sh --strict && npm test -- --run; npm run build -> passed.

Next: Requesting one Codex review for the current head; no merge, publish, release, tag, workflow dispatch, force-push, settings, or secrets action taken.

[graphanov]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 52be6fb70c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[graphanov]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Breezy!

Reviewed commit: 442924f8e7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".