loadout-ai 0.9.1 → 0.9.3

package/CHANGELOG.md

@@ -2,6 +2,54 @@
 
 ## Unreleased
 
+## 0.9.3 - 2026-09-07
+
+### Changed
+
+- Unified README around the full Loadout lifecycle: discover, curate, activate,
+  handoff, and coordinate — with a single hero image covering all five stages.
+- Added prominent documentation for one-command bounded Claude Code ↔ Codex
+  design discussions (`loadout coord discuss start`).
+- Aligned the GitHub social-preview asset with the unified workflow narrative.
+- Moved npm release authentication fully to trusted publishing (OIDC), removing
+  the legacy publish-token fallback.
+
+## 0.9.2 - 2026-09-06
+
+### Changed
+
+- Coordination discussion output now removes duplicate lifecycle noise, shows a
+  single outcome section, and identifies the provider in every provider error.
+- Maximum Library preparation now skips packages that cannot be safely prepared
+  and clearly reports that the remaining reviewed library can still install.
+
+### Fixed
+
+- Bound overlong provider-synthesized decisions to the coordination event limit
+  instead of failing after all paid discussion turns have completed.
+- Materialize multi-path ownership claims once per normalized path so snapshots
+  and status output do not repeat the full claim for every path.
+- Close the Claude Code subprocess stdin explicitly, avoiding its empty-input
+  wait before a bounded coordination turn begins.
+- Forward cancellation and timeout signals natively to both Claude Code and the
+  Codex SDK so a timed-out paid turn cannot keep running while Loadout starts a
+  replacement turn.
+- Restore files before reapplying read-only directory modes and reject snapshot
+  modes containing special permission bits.
+- Preserve strictly increasing coordination sequence order after checkpoint
+  compaction.
+- Treat all reviewed commits for a shared catalog repository as valid when
+  detecting upstream catalog drift.
+- Apply the default repository timeout to generic HTTPS and SSH Git sources as
+  well as catalog GitHub sources.
+
+### Security
+
+- Expand deterministic instruction-injection signatures and document the
+  repository-grounded threat model in `loadout-threat-model.md`.
+
+## 0.9.1 - 2026-09-05
+
 ### Added
 
 - Snapshot capture and restore preserve Unix file permission modes, with

package/README.md

@@ -1,16 +1,9 @@
-<p align="center">
-  <img src="./docs/assets/loadout-discover-activate.webp" alt="Loadout discovers agent skills, tools, and MCP servers; screens and pins them; activates the right set for a repository; and lets users preview or roll back every change." width="960">
-</p>
-
 <h1 align="center">Loadout</h1>
 
-<p align="center"><strong>Agent extensions, under control.</strong></p>
+<p align="center"><strong>Manage skills for 12 coding agents. Hand off and coordinate work between Claude Code and Codex.</strong></p>
 
 <p align="center">
-  <strong>The package manager for your AI coding setup.</strong><br>
-  Find skills worth having, activate the right ones per project,<br>
-  install them across 12 agents, hand work from Claude Code to Codex,<br>
-  and undo any of it.
+  <img src="./docs/assets/loadout-unified-workflow-v2.webp" alt="Loadout discovers, curates, and activates skills, tools, and MCP servers for coding agents, then helps Claude Code and Codex handoff and coordinate work through durable tasks, bundled context, ownership, contracts, and decisions." width="960">
 </p>
 
 <p align="center">
@@ -23,186 +16,158 @@
 </p>
 
 <p align="center">
-  <a href="#what-it-looks-like">See it</a> ·
-  <a href="#install">Install</a> ·
-  <a href="#use-it-from-inside-your-agent">Use it in your agent</a> ·
-  <a href="#passing-work-between-two-agents">Two agents</a> ·
-  <a href="#why-loadout">Why</a> ·
+  <a href="#try-it-in-30-seconds">Quick start</a> ·
+  <a href="#use-claude-code-and-codex-together">Two agents</a> ·
+  <a href="#try-these-prompts">Agent skills</a> ·
+  <a href="#safety-and-trust">Safety</a> ·
   <a href="#command-reference">Commands</a>
 </p>
 
-## What it looks like
-
-```console
-$ loadout doctor
-loadout doctor — HEALTHY
-
-Platform:   darwin
-State:      ~/.loadout ✓ writable
-Agents:     3 detected, 9 available
-
-DETECTED AGENTS
-  ✓ Claude Code
-    ~/.claude/skills
-    43 skills | supports: skill, command, agent, mcp, plugin, root
-  ✓ Codex
-    ~/.agents/skills
-    30 skills | supports: skill, command, agent, mcp, plugin, root
-
-$ loadout recommend --project .
-Project: checkout-service
-Detected: TypeScript, Zod, Vitest, next.js, react
-
-Rule-based project suggestions:
-  superpowers [high, skill library] — Useful engineering planning, testing, and review workflows.
-  context7 [high, skill library] — Current library documentation helps agents avoid outdated APIs.
-  ui-ux-pro-max [high, skill library] — Frontend framework detected: next.js, react.
-  playwright-mcp [medium, MCP/runtime setup] — Browser verification may help test the detected frontend.
+## Try it in 30 seconds
+
+You need Node.js 20 or newer and Git.
+
+```bash
+npm install --global loadout-ai
+loadout setup --mode stable
+```
+
+The second command detects your coding agents and previews the 30-skill Stable
+loadout. It does not change agent files. Review the plan, then apply it:
+
+```bash
+loadout setup --mode stable --yes
+loadout status
 ```
 
-It reads your repository rather than a config file, knows which agents you
-actually have, and previews and snapshots every write before it touches them.
+Loadout saves a rollback snapshot before applying changes. Run
+`loadout rollback` to restore the previous managed state.
 
-### Demo
+> `Preview complete; nothing was changed. Re-run with --yes to install this exact screened plan.`
 
-<p align="center">
-  <a href="https://www.youtube.com/watch?v=opNqJKX7xMw">
-    <img src="https://img.youtube.com/vi/opNqJKX7xMw/maxresdefault.jpg" alt="Watch the 72-second Loadout demo" width="880">
-  </a>
-</p>
+A later `--yes` invocation recomputes the plan from pinned sources and current agent and filesystem state; it does not persist or prove identity with the earlier preview.
 
-**[Watch the 72-second Loadout demo on YouTube](https://www.youtube.com/watch?v=opNqJKX7xMw).**
+## What Loadout does
 
-## Install
+| Capability     | What you get                                                          |
+| -------------- | --------------------------------------------------------------------- |
+| **Discover**   | Find skills, tools, and MCP servers worth reviewing                   |
+| **Curate**     | Inspect, screen, and pin sources before trusting them                 |
+| **Activate**   | Install a focused set for this repository across your agents          |
+| **Handoff**    | Pass durable tasks with bundled context between Claude Code and Codex |
+| **Coordinate** | Share file ownership, contracts, decisions, and acknowledgements      |
 
-You need Node.js 20 or newer and Git.
+The package manager works across supported agents. Handoff and coordination are
+currently designed for Claude Code and Codex working in the same repository.
+
+## Use Claude Code and Codex together
+
+### Handoff: pass a task that survives sessions
 
 ```bash
-npm install --global loadout-ai
-loadout setup --mode stable
+loadout handoff codex "write unit tests for auth" --bundle src/auth.ts src/types.ts --verify "tests pass" --verify-command npm --verify-args '["test"]'
+```
+
+Codex sees the task when it checks its inbox, works from the attached bounded
+context, and marks it done. Claude Code can then read the result. Handoffs live
+in an append-only project log, so restarting either agent does not erase them.
+Bundles contain secret-redacted text and are capped at 50 KiB total; still
+review them before committing and never attach credential files.
+
+### Coordinate: work at the same time without stepping on files
+
+```bash
+loadout coord start --agents claude-code,codex       # preview ownership
+loadout coord start --agents claude-code,codex --yes # apply ownership
+loadout coord snapshot codex                         # inspect shared state
+loadout coord discuss start "REST or GraphQL?" --agents claude-code,codex --rounds 2 --max-turns 5
 ```
 
-The second command detects your agents and previews the 30-skill Stable loadout.
-Nothing changes until you approve it. If anything goes wrong, start with the
-[user test guide](./docs/USER_TEST_GUIDE.md).
+Coordination is structured shared project state, not shared memory or a merged
+context window. Events reach an agent at safe turn boundaries or when it checks
+its snapshot; Loadout does not interrupt a turn in progress.
 
-For a reproducible install, pin the release: `npm install --global loadout-ai@0.9.1`.
+### Let Claude and Codex debate one decision
 
-## Use it from inside your agent
+You prompt once and Loadout calls both providers in bounded turns—propose,
+critique, synthesize—then records the decision. Neither agent can inject into
+the other's in-progress turn; events arrive at safe turn boundaries. Each
+round consumes paid provider turns from your configured Claude and Codex quota.
+The bounded design discussion reports its turn budget before it starts.
 
-A CLI you have to leave your agent to run is a context switch. Loadout ships two
-skills so you do not have to: one for agent handoffs and one for choosing a
-focused skill set for the current repository.
+See the [live coordination guide](./docs/LIVE_COLLABORATION.md) for ownership,
+contracts, acknowledgements, discussions, the local dashboard, and limitations.
+
+## Try these prompts
+
+Install Loadout's two first-party skills once so your agent knows the workflow:
 
 ```bash
 loadout skills install loadout-handoff --yes
 loadout skills install loadout-curator --yes
 ```
 
-Start a new agent session and just ask, in the conversation you are already in:
+Then ask naturally:
 
 > _"Hand the test writing to Codex."_
+>
 > _"What did Codex leave for me?"_
+>
 > _"Which skills should be active for this repo?"_
 
-The skills teach your agent to call `loadout` and act on the results, so it
-checks its own inbox at the start of a session and can pass work to your other
-agent without you relaying it by hand.
-
-`loadout skills list` shows what ships with Loadout and what is already installed.
+The curator helps choose a focused active set; the handoff skill manages inboxes
+and coordination without making you relay every command.
 
-## Passing work between two agents
-
-<p align="center">
-  <img src="./docs/assets/loadout-handoff-coordinate.webp" alt="Claude Code and Codex use Loadout in two ways: durable task handoffs between sessions, and structured coordination for contracts, file ownership, decisions, acknowledgements, and an audit trail." width="960">
-</p>
+## Install and choose your agent
 
-If you pay for both Claude and a ChatGPT plan, the two agents cannot see each
-other. Loadout gives them a shared, append-only task log:
+For a reproducible install, pin the current release:
 
 ```bash
-loadout handoff codex "write unit tests for auth" --bundle src/auth.ts src/types.ts --verify "tests pass" --verify-command npm --verify-args '["test"]'
+npm install --global loadout-ai@0.9.3
+loadout setup --mode stable
+loadout setup --mode stable --yes
+loadout status
 ```
 
-Bundles snapshot exact, secret-redacted text (50 KiB total). Verification runs
-only with `--done --run-verification`, without a shell; failures stay pending. The first send adds
-managed inbox blocks to `CLAUDE.md` and `AGENTS.md`. Treat bundles as untrusted
-project data, review before committing, and never include credential files.
+Stable is the recommended starting point: 30 selected skill directories from
+four pinned public sources. Loadout auto-detects supported agents; use
+`--agents` when you want to narrow the destination.
 
-```bash
-loadout handoff codex      # what is waiting for codex
-loadout handoff            # everything pending, both directions
-loadout handoff --done 4f2a1c
-```
+If anything fails, follow the [user test guide](./docs/USER_TEST_GUIDE.md).
+For profiles, per-agent paths, MCP configuration, and advanced commands, use the
+[full reference](./docs/REFERENCE.md).
 
-### Make Claude Code and Codex coordinate live (beta)
+## Safety and trust
 
-Live coordination adds file ownership, versioned contracts, decisions, and
-acknowledgements over a shared project event stream — not a merged context
-window. See the [live coordination guide](./docs/LIVE_COLLABORATION.md).
+**Choose -> Inspect -> Preview -> Apply -> Undo**
 
-```bash
-loadout coord start --agents claude-code,codex          # preview ownership
-loadout coord start --agents claude-code,codex --yes    # apply it
-loadout coord detect                                    # shared interfaces
-loadout handoff codex src/auth.ts --template write-tests
-loadout coord discuss start "REST or GraphQL?" --agents claude-code,codex --rounds 2 --max-turns 5
-loadout coord discuss implement <thread-id>             # preview linked tasks
-```
+- Preview is the default for setup, updates, and removal.
+- Every managed apply creates a rollback snapshot first.
+- Catalog sources are pinned and technically inspected, not declared safe or useful by fiat.
+- Static inspection reports scripts, hooks, binaries, domains, credential references, and unsupported components; it is not a security audit.
+- Project recommendations read bounded local metadata. The documented local flow does not upload project source.
+- MCP servers and executable tools stay behind separate preview, permission, and setup steps.
+- Shared manifests store environment-variable or OS-keychain references, not secret values.
 
-Contract publication and bounded design discussion implementation require a second `--yes`
-approval. Exact supported declarations are marked current or stale; ambiguous
-ones require manual review. The optional MCP server and provider bridge deliver
-events at safe turn boundaries, never during an active turn. The
-[coordination guide](./docs/LIVE_COLLABORATION.md) covers templates, Git-author
-mappings, the local dashboard, limitations, and the complete workflow.
+<!-- loadout:current-limits:start -->
 
-## How it works
+- All catalog records have identified SPDX licenses. See the [recorded license decisions](./docs/UPSTREAM_LICENSE_DECISIONS.md) for the source-by-source record.
 
-**Choose -> Inspect -> Preview -> Apply -> Undo**
+<!-- loadout:current-limits:end -->
 
-1. **Choose** Stable, Power, Maximum, or your own package list.
-2. **Inspect** where each extension comes from and what it can do.
-3. **Preview** every planned change without changing agent files.
-4. **Apply** with `--yes`; Loadout saves a rollback snapshot first.
-5. **Undo** with `loadout rollback` if you change your mind.
-
-### Abridged terminal transcript
-
-This is an explicitly abridged transcript from a disposable Stable run. A literal `…` marks omitted fetch output; `<snapshot-id>` is a variable placeholder because snapshot IDs vary. Loadout auto-detects installed agents; `--agents` narrows the selection when needed.
-
-```console
-$ loadout setup --mode stable
-…
-Loadout: Stable
-Detected agents: Claude Code, Cursor, Codex
-Catalog selection: 4 repositories
-Ready to install: 4 skill repositories (30 agent skill directories)
-Preview complete; nothing was changed. Re-run with --yes to install this exact screened plan.
-
-$ loadout setup --mode stable --yes
-…
-Loadout installed 4 repositories for 3 agent(s). Snapshot: <snapshot-id>
-
-$ loadout rollback
-Restored snapshot <snapshot-id>
-
-$ loadout handoff codex "write tests for the auth module" --context "zod schemas exist"
-  created .handoff/
-  told codex to check its inbox
-Sent to codex: write tests for the auth module
-
-$ loadout doctor
-loadout doctor — HEALTHY
-Platform:   darwin
-State:      ~/.loadout ✓ writable
-Agents:     3 detected, 9 available
-```
+Read the [security policy](./SECURITY.md), [catalog policy](./docs/CATALOG_POLICY.md),
+and [credential and update policy](./docs/CREDENTIAL_AND_UPDATE_POLICY.md) before
+trusting third-party content.
+
+## Demo
 
-The final preview sentence above is captured CLI wording. A later `--yes` invocation recomputes the plan from pinned sources and current agent and filesystem state; it does not persist or prove identity with the earlier preview.
+<p align="center">
+  <a href="https://www.youtube.com/watch?v=opNqJKX7xMw">
+    <img src="https://img.youtube.com/vi/opNqJKX7xMw/maxresdefault.jpg" alt="Watch the 72-second Loadout demo" width="880">
+  </a>
+</p>
 
-Preview may fill Loadout's private download cache, but it does not change your agent
-files. Review the summary and warnings before approving an apply command.
+**[Watch the 72-second Loadout demo on YouTube](https://www.youtube.com/watch?v=opNqJKX7xMw).**
 
 ## Why Loadout
 
@@ -225,7 +190,7 @@ structured project facts when Claude Code and Codex work together.
 
 Everything on this page is enforced. `docs/evidence/readme-claims.json` records
 each material claim with the code or command that proves it, and CI fails the
-build when the README and the implementation disagree — including the pinned
+build when the README and the implementation disagree—including the pinned
 version in the install line above.
 
 Loadout watches a much wider catalog than it activates. You can keep thousands of
@@ -243,53 +208,30 @@ everything into every prompt.
 | Manually remember what was changed                             | Scan, reconcile, remove, roll back, or completely uninstall      |
 
 Loadout is local, open source, and preview-first. It does not need an LLM API key
-to manage skills. MCP servers and executable tools stay behind their own explicit
-setup and permission steps.
-
-## Stable workflow
-
-### Stable: install the essentials and start building
-
-Stable is the recommended daily driver: **30 selected skill directories from four
-pinned public sources**, installed into each agent you choose.
-
-```bash
-loadout setup --mode stable
-loadout setup --mode stable --yes
-loadout status
-loadout scan
-loadout rollback
-```
-
-Stable is Loadout's strongest general starting point, not a claim that one setup is
-best for every person or project.
+to manage skills.
 
 ## Profiles
 
-| Mode      | Sources               | Skills | Active by default                |
-| --------- | --------------------- | ------ | -------------------------------- |
-| `stable`  | 4                     | 30     | yes — recommended starting point |
-| `power`   | 8                     | 56     | yes                              |
-| `maximum` | all reviewed          | all    | **no — downloaded but disabled** |
-| `custom`  | your `--package` list | varies | yes                              |
-
-**Maximum** downloads the entire reviewed library and leaves every skill _disabled_.
-Nothing reaches an agent prompt until a project activates what it needs.
+| Mode      | Sources               | Skills | Active by default              |
+| --------- | --------------------- | ------ | ------------------------------ |
+| `stable`  | 4                     | 30     | yes—recommended starting point |
+| `power`   | 8                     | 56     | yes                            |
+| `maximum` | all reviewed          | all    | **no—downloaded but disabled** |
+| `custom`  | your `--package` list | varies | yes                            |
 
-For detailed profile tables, source lists, and custom configuration, see the
-**[full reference](./docs/REFERENCE.md)**.
+Maximum downloads the reviewed library and leaves every skill disabled. Nothing
+reaches an agent prompt until a project activates what it needs. See the
+[full reference](./docs/REFERENCE.md) for source lists and custom configuration.
 
 ## Catalog and discovery
 
-The catalog is not a frozen list. Loadout separates **discovery** from
-**installation** so a viral repo can be noticed quickly without being trusted
-blindly.
+Discovery is separate from trust and installation. A popular new repository can
+enter the review queue without being installed or promoted automatically.
 
 ```bash
 loadout discover --source all --queue
 loadout review-queue
 loadout candidate inspect owner/repository
-loadout update
 ```
 
 <!-- loadout:catalog-coverage:start -->
@@ -306,26 +248,9 @@ Catalog maturity: **53 sourced**, **53 technically inspected**, and **4 selected
 
 <!-- loadout:daily-discovery:start -->
 
-**Discovery snapshot (generated 2026-09-05):** [238 repositories observed](./docs/DISCOVERED.md), including 222 uncataloged review candidates and 16 repositories already in the inspected catalog.
+**Discovery snapshot (generated 2026-09-07):** [237 repositories observed](./docs/DISCOVERED.md), including 221 uncataloged review candidates and 16 repositories already in the inspected catalog.
 <!-- loadout:daily-discovery:end -->
 
-## Trust and limits
-
-- A pinned commit identifies source bytes; it does not prove safety, correct licensing, usefulness, or future compatibility.
-- Static inspection reports scripts, hooks, binaries, domains, credential references, and unsupported components. It is not a security audit.
-- No bundled source is called proven until human review and recorded local outcomes support it.
-- Project recommendations read bounded local metadata. The documented local flow does not upload project source.
-- MCP servers and executable tools have separate preview and approval paths.
-- Shared manifests hold environment-variable or OS-keychain references, not secret values.
-
-<!-- loadout:current-limits:start -->
-
-- All catalog records have identified SPDX licenses. See the [recorded license decisions](./docs/UPSTREAM_LICENSE_DECISIONS.md) for the source-by-source record.
-
-<!-- loadout:current-limits:end -->
-
-Read the [security policy](./SECURITY.md), [catalog policy](./docs/CATALOG_POLICY.md), and [credential and update policy](./docs/CREDENTIAL_AND_UPDATE_POLICY.md) before trusting third-party content.
-
 ## Agent support
 
 <!-- loadout:support-summary:start -->
@@ -344,42 +269,27 @@ Configured CI platforms describe a manually triggered workflow, not evidence tha
 
 ## Command reference
 
-| What it does                            | Command                                                    |
-| --------------------------------------- | ---------------------------------------------------------- |
-| Beginner-friendly guided path           | `loadout guide`                                            |
-| Preview the 30-skill Stable setup       | `loadout setup --mode stable`                              |
-| Apply after reviewing the preview       | `loadout setup --mode stable --yes`                        |
-| Show managed packages and active skills | `loadout status` · `loadout library`                       |
-| What fits this repository               | `loadout recommend --project .`                            |
-| Project-specific active set             | `loadout optimize --project . --limit 30`                  |
-| Scan existing skills across agents      | `loadout scan`                                             |
-| Check for source updates                | `loadout update`                                           |
-| Find newly launched candidates          | `loadout discover --source all --queue`                    |
-| Install Loadout's own skill             | `loadout skills install loadout-handoff --yes`             |
-| Send a task to another agent            | `loadout handoff codex "write tests"`                      |
-| Use a reusable handoff template         | `loadout handoff codex src/auth.ts --template write-tests` |
-| Preview two-agent ownership setup       | `loadout coord start --agents claude-code,codex`           |
-| Detect shared contract candidates       | `loadout coord detect`                                     |
-| Inspect shared agent state              | `loadout coord snapshot codex`                             |
-| Detect live provider runtimes           | `loadout coord agents detect`                              |
-| Debate one design with both providers   | `loadout coord discuss start "<topic>" ...`                |
-| Turn a decision into linked tasks       | `loadout coord discuss implement <thread-id>`              |
-| Start the coordination MCP server       | `loadout serve`                                            |
-| Agent health check                      | `loadout doctor`                                           |
-| Rollback the latest managed change      | `loadout rollback`                                         |
-| Preview complete removal                | `loadout uninstall`                                        |
-| Full CLI reference                      | `loadout --help` · `loadout advanced`                      |
-
-Most mutating commands are dry runs first. Add `--yes` to apply.
-
-## Built with Claude and Codex
-
-Loadout was designed and built by [Viraj Mishra](https://github.com/VirajMishra1) with Claude Code and Codex.
-
-Loadout's core skill management does **not** call an LLM API or require an LLM API
-key. The opt-in provider bridge and design room do invoke your configured
-Claude/Codex sessions and spend their quota; neither is a hidden requirement for
-discovering, installing, or rolling back extensions.
+| Goal                               | Command                                                    |
+| ---------------------------------- | ---------------------------------------------------------- |
+| Guided first run                   | `loadout guide`                                            |
+| Preview or apply Stable            | `loadout setup --mode stable` · add `--yes` to apply       |
+| Inspect managed skills             | `loadout status` · `loadout library`                       |
+| Recommend for this repository      | `loadout recommend --project .`                            |
+| Activate a project-specific set    | `loadout optimize --project . --limit 30`                  |
+| Scan or update                     | `loadout scan` · `loadout update`                          |
+| Send a task                        | `loadout handoff codex "write tests"`                      |
+| Use a handoff template             | `loadout handoff codex src/auth.ts --template write-tests` |
+| Preview two-agent ownership        | `loadout coord start --agents claude-code,codex`           |
+| Inspect coordination state         | `loadout coord snapshot codex`                             |
+| Detect shared contract candidates  | `loadout coord detect`                                     |
+| Turn a decision into tasks         | `loadout coord discuss implement <thread-id>`              |
+| Start the coordination MCP server  | `loadout serve`                                            |
+| Health check                       | `loadout doctor`                                           |
+| Restore the previous managed state | `loadout rollback`                                         |
+| Preview complete removal           | `loadout uninstall`                                        |
+| Full CLI reference                 | `loadout --help` · `loadout advanced`                      |
+
+Most mutating commands are previews first. Add `--yes` only after reviewing the plan.
 
 ## Development
 
@@ -395,25 +305,31 @@ npm run verify:full
 
 <!-- loadout:verification-summary:end -->
 
-The [testing guide](./docs/TESTING.md) documents the exact checks and their boundaries.
+The [testing guide](./docs/TESTING.md) documents each check and its boundary.
 
 ## Documentation
 
-- [Full reference (profiles, MCP, discovery, tools)](./docs/REFERENCE.md)
+- [Full CLI and profile reference](./docs/REFERENCE.md)
+- [User test guide](./docs/USER_TEST_GUIDE.md)
+- [Live Claude Code ↔ Codex coordination](./docs/LIVE_COLLABORATION.md)
 - [Catalog and upstream credits](./docs/CATALOG.md)
 - [Catalog evidence policy](./docs/CATALOG_POLICY.md)
 - [Feature and evidence matrix](./docs/FEATURE_TEST_MATRIX.md)
 - [Testing contract](./docs/TESTING.md)
-- [User test guide](./docs/USER_TEST_GUIDE.md)
-- [Live Codex ↔ Claude collaboration design](./docs/LIVE_COLLABORATION.md)
 - [Changelog](./CHANGELOG.md)
 
 ## Contributing, security, and attribution
 
-See [CONTRIBUTING.md](./CONTRIBUTING.md) · [Code of Conduct](./CODE_OF_CONDUCT.md) · Report vulnerabilities through [SECURITY.md](./SECURITY.md), without credentials, private source, or unredacted state. General bugs and proposals belong in the [issue tracker](https://github.com/VirajMishra1/loadout/issues).
+See [CONTRIBUTING.md](./CONTRIBUTING.md) · [Code of Conduct](./CODE_OF_CONDUCT.md) ·
+Report vulnerabilities through [SECURITY.md](./SECURITY.md), without credentials,
+private source, or unredacted state. General bugs and proposals belong in the
+[issue tracker](https://github.com/VirajMishra1/loadout/issues).
 
-The catalog contains 53 credited public repositories. Inclusion records discovery and attribution; it does not transfer ownership, imply endorsement, or relicense upstream work.
+The catalog contains 53 credited public repositories. Inclusion records discovery
+and attribution; it does not transfer ownership, imply endorsement, or relicense
+upstream work.
 
 ## License
 
-Loadout is licensed under the [MIT License](./LICENSE). Catalog entries retain their upstream licenses and terms.
+Loadout is licensed under the [MIT License](./LICENSE). Catalog entries retain
+their upstream licenses and terms.