release: prepare archctx 0.14.1 #582

Release slice of archctx / archctx-contracts 0.14.1. It follows docs/runbooks/npm-release.md, using the 0.14.0 precedent (#573, PR #578).

Blocked by #579 and #580. It starts from main after both merge.

Scope

• Version authorities move to 0.14.1, the same 12-file shape as chore(release): prepare archctx 0.14.0 (#573) #578:
  • the root and five package manifests;
  • the five bun.lock workspace entries;
  • product-version.ts;
  • the contracts fixtures archctx-capabilities and product-version-manifest;
  • the practice catalog manifest, with catalogDigest regenerated and cross-checked.
• A new deploy/release-checklists/archctx-0.14.1.md, read from the merged code of docs apply: the v4 re-baseline refuses a v3 manifest that has minimumRendererVersion #579 and projection: repo-harness/v1 renders 20 agent-context regions into root AGENTS.md and CLAUDE.md #580:
  • docs apply: the v4 re-baseline refuses a v3 manifest that has minimumRendererVersion #579: a v3 manifest with floors re-baselines;
  • projection: repo-harness/v1 renders 20 agent-context regions into root AGENTS.md and CLAUDE.md #580: no root agent-context regions under repo-harness/v1; owned regions are retired; the ADR-0056 §9 amendment.
• The release candidate PR is merged by the owner after hosted Verify passes on its head. The advisor runs the dry run and both preflights at the RC head and records the tree hash. Publish, tag and the GitHub Release are owner actions.

Tier Medium, one GPT review.

Seat: orchestrator t7