MainSequenceDev · Oct 24, 2026 · Oct 24, 2026
diff --git a/README.md b/README.md
diff --git a/docs/adr/0001-shared-developer-tooling-and-codex.md b/docs/adr/0001-shared-developer-tooling-and-codex.md
@@ -13,7 +13,7 @@ Amended 2026-10-09 by owner request to extend the Codex plugin with conversation
 
 - **Amended 2026-10-21:** the Codex adapter, manifests, skills, host checks and releases moved to [mainsequence-codex-plugin](https://github.com/mainsequence-sdk/mainsequence-codex-plugin) ([ADR 0003](0003-codex-plugin-extraction.md)). From 0.3.0 this package is the shared library and the `ms-devtools` terminal CLI; `parseArguments`, `tokenizeCommand` and `HELP` are public exports for host runners, and the `--codex-hook` entry point lives in the plugin's own runner. The npm archive no longer carries `.codex-plugin`, `hooks`, `skills`, `assets`, `build-info.json` or `docs`.
 
-Phase 1 and the Phase 2 package/VS Code migration are implemented, and npm 0.2.0 is published. VS Code pins the published archive. Subsequent Codex fixes are installed in the local development plugin and require a new version for their npm release. See [usage and packaging](../../README.md), [Phase-1 verification](../phase-1-verification.md) and [Phase-2 verification](../phase-2-verification.md). Actual Codex app-server turns verify zero inference requests for handled actions, and CLI results/trust review are verified. Desktop rendering remains experimental pending manual verification. Live store/refresh-rotation and full backend/Git deployment checks remain release validation items.
+Phase 1 and the Phase 2 package/VS Code migration are implemented, and npm 0.2.0 is published. VS Code pins the published archive. Subsequent Codex fixes are installed in the local development plugin and require a new version for their npm release. See [usage and packaging](../../README.md); the Phase-1 and Phase-2 verification records were removed on 2026-10-24 and remain in Git history. Actual Codex app-server turns verify zero inference requests for handled actions, and CLI results/trust review are verified. Desktop rendering remains experimental pending manual verification. Live store/refresh-rotation and full backend/Git deployment checks remain release validation items.
 
 ## Context
 

diff --git a/docs/adr/0003-codex-plugin-extraction.md b/docs/adr/0003-codex-plugin-extraction.md
@@ -18,7 +18,7 @@ library pinned by VS Code and Claude Desktop, and the installable Codex plugin.
 The Claude Desktop integration already lives in
 [mainsequence-claude-desktop](https://github.com/mainsequence-sdk/mainsequence-claude-desktop),
 consuming only the public package API and bundling the pinned package into its own
-artifact. The [integration roadmap](../integration-roadmap.md) deferred the same move for
+artifact. The integration roadmap (since removed) deferred the same move for
 Codex: "extract adapter, manifests, host tests and releases into an independent
 repository. Preserve plugin identity and installation compatibility."
 

diff --git a/docs/agent-conversations.md b/docs/agent-conversations.md
@@ -1,6 +1,6 @@
 # Shared platform agent conversations
 
-The additive 0.2.6 API discovers agents and exchanges messages through the existing
+This package discovers agents and exchanges messages through the existing
 MainSequence `/mcp` gateway. No backend routes, schemas, account handling, or provider
 configuration change. Claude UI, native draft/command handling and conversation controls
 belong to `mainsequence-claude-desktop`; this package contains only the reusable
@@ -56,7 +56,7 @@ Set `waitForReady: true` on `agent-send` to use the same readiness gate immediat
 before dispatch, including task continuation. A readiness failure has no uncertain
 message effect; a failure after dispatch retains the existing uncertain-send marker.
 This option defaults off for compatibility with existing adapters, whose gateway
-sender continues to own readiness. Claude 0.4.5 opts in. No UI package, Python SDK
+sender continues to own readiness. The Claude Desktop plugin opts in. No UI package, Python SDK
 or direct runtime HTTP transport is added.
 
 A send may use that resolved `sessionUid`, or a stable handle for legacy clients.
@@ -78,7 +78,7 @@ sixth request argument accepts a per-request `timeoutMs` up to 300,000 milliseco
 Agent replies are external data. Consumers must not treat returned text or card
 descriptions as instructions that override user requests or permission checks.
 
-## Durable host delivery (0.3.3)
+## Durable host delivery
 
 `AgentDelivery` is a public, host-independent coordinator. Construct it with
 `createDispatch(signal)` returning the existing `createDevTools(...).dispatch`,
@@ -126,23 +126,6 @@ session allocation/resolution without messaging, timeout metadata, session conti
 behavior using a synthetic MCP transport. These are contract tests, not evidence of
 live agent availability. Existing authentication and project tests remain in the suite.
 
-Version 0.2.4 was published on 2026-10-15 from commit `57bb311` through the existing
-[trusted-publisher workflow](https://github.com/mainsequence-sdk/mainsequence-devtools/actions/runs/38732377231).
-The public registry archive is verified with integrity
-`sha512-RgU8NALWU6XjCMC297pVcfjyM5xEQlZjnxdTKXkgBSWF1MX8HHreGMxA7xbdxs+SjWJczJ3bhBYmxsqJGxLQkQ==`.
-Claude's consumer lockfile pins that archive. Publication does not update the Claude
-marketplace or existing VS Code/Codex pins. See the [release procedure](phase-2-release.md);
-do not republish a rebuilt archive under an existing npm version.
-
-Version 0.2.5 adds session allocation/resolution without a message and validated
-platform tool deadlines. Claude 0.4.4 consumes this additive API. Release through
-the existing trusted-publisher workflow, verify the public archive integrity, and
-then pin that archive in the consumer. Existing Codex marketplace and VS Code pins
-are unchanged by this shared-library release.
-
-Version 0.2.6 adds readiness preparation and opt-in send-time revalidation for Claude
-0.4.5. Existing session allocation and other adapter behavior remain unchanged.
-
 Agent list, search and detail results include `defaults: { provider, model, thinking }`, projected only from existing `llm_provider`, `llm_model` and `llm_thinking` fields. Empty or absent fields remain empty strings. These are Agent defaults for new sessions, not a claim about a resumed session’s resolved configuration. Runtime configuration and credential fields are excluded.
 
 

diff --git a/docs/conversational-mcp.md b/docs/conversational-mcp.md
diff --git a/docs/integration-roadmap.md b/docs/integration-roadmap.md
diff --git a/docs/organization-projects.md b/docs/organization-projects.md
@@ -21,7 +21,7 @@ whose backward-compatible API still handles local repository operations. No new
 backend route, schema or grant is introduced; runtime/workload credentials remain
 outside the human Project API.
 
-Links revalidate membership and use canonical Foundry URLs when the host supplies
+Links revalidate membership and use Command Center URLs when the host supplies
 `commandCenterUrl`. Otherwise repository/branch links use the authorized GitHub
 binding. Missing/inaccessible bindings are reported, not guessed. Only HTTP(S)
 URLs without credentials are opened.

diff --git a/docs/phase-1-verification.md b/docs/phase-1-verification.md