chore(release): Development Kit v0.11.2

[eybersjp]

Description

Prepares Development Kit release v0.11.2, consolidating:

• Development Modes (Rapid, Balanced, Specification-Driven, Documentation-Driven, Maintenance & Evolution)
• IDEA Authority Hardening (provenance, one-at-a-time fingerprinted interactions, journal restart recovery, replay protection receipts, source-bound Idea Brief approvals)
• Workflow Modernization (GitHub Actions updated to checkout@v7, setup-node@v7, configure-pages@v6, upload-pages-artifact@v5, deploy-pages@v5)

All release validations and test suites pass cleanly across Windows and Ubuntu.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ba722a914d

ℹ️ 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".

[chatgpt-codex-connector]

Publish the new capabilities under a minor version

This release adds user-facing runtime capabilities—Development Modes and IDEA Authority Hardening—while changing 0.11.1 to the patch version 0.11.2. The repository's docs/08-maintenance-release/versioning-policy.md explicitly reserves MINOR releases for backward-compatible runtime capabilities and user-facing features, and PATCH releases for fixes, documentation, validation, and maintenance. Publishing these additions as 0.11.2 therefore violates the advertised compatibility contract and cannot be repaired after that npm version is published; use the next minor version and align the other release references.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Reconcile project memory with the v0.11.2 release state

After changing the baseline here to a v0.11.2 release candidate, this file still labels Development Modes and IDEA Authority Hardening as post-v0.11.1 mainline work and states at lines 59 and 66 that v0.11.1 is published while those capabilities remain unpublished; meanwhile README, STRATEGY, ROADMAP, and the new release notes now describe v0.11.2 as released. This leaves the repository's release authority contradictory both before publication and afterward, so these remaining sections should consistently describe either a candidate or the completed v0.11.2 release.

Useful? React with 👍 / 👎.