Release: Safer Acceptance, Release, And Codex Stub Workflows

Forgeflow 4.3.19 tightens the operational edges around code-map acceptances, support bundles, post-publish verification, release-note issue context, and generated Codex agent stubs. The release keeps the improvements local-first and avoids new GitHub or network behavior.

Code Map And Support

• /forgeflow-code-map now reports lifecycle warnings for local acceptances that are missing notes, use invalid dates, are expired, or have become stale.
• Local acceptances can include date-only accepted_at and expires_at metadata without changing exact-match acceptance behavior.
• /forgeflow-support now includes code-map acceptance health, post-publish verification status, and direct next actions when either surface needs attention.

Release Workflow

• /forgeflow-release-readiness --post-publish --save-post-publish can save a local post-publish verification snapshot.
• /forgeflow-release-readiness --post-publish --compare-post-publish-last compares current evidence against the last saved post-publish snapshot.
• render-release-notes.js --issues <path> can enrich release drafts with public-safe issue context from a repo-relative local { "issues": [...] } JSON file.
• Release-note issue output is labeled as issue context so curated metadata is not mistaken for proof that a commit fixed or referenced an issue.

Codex Porting

• generate-codex-agent-stubs.js no longer emits vague TODO instructions when a mapped agent has no summary or selected sections.
• The fallback now points maintainers to canonical_source, canonical_sha256, and .codex/agent-canonical-map.json so incomplete stubs are explicit and actionable.

Validation

• node scripts/forgeflow/test-show-code-map.js
• node scripts/forgeflow/test-render-support-bundle.js
• node scripts/forgeflow/test-render-release-readiness.js
• node scripts/forgeflow/test-render-release-notes.js
• node scripts/forgeflow/test-generate-codex-agent-stubs.js
• Full scripts/forgeflow/test-*.js suite