chore: simplify public repository tree

[lagrangee]

Problem

The public tree still tracked internal agent/tool state and one-time release process artifacts, which obscured the supported user and contributor surface.

Changes

• Stop tracking and ignore .bearing, .impeccable, AGENTS.md, and docs/agents while preserving local ignored copies.
• Consolidate the domain, product, design, validation, deployment, and MCP guidance under a user-facing docs index.
• Remove completed cutover, history-rehearsal, handoff, review, and release-process artifacts.
• Harden documentation and public-source acceptance checks against reintroducing local-only paths.

Contract impact

None. Runtime behavior, public APIs, schemas, migrations, and deployment behavior are unchanged.

Verification

• npm run public:gate
• npm run docs:lint
• node --test tests/mcp-onboarding.test.js
• node scripts/release-acceptance.mjs
• npm run source:scan
• git diff --cached --check before commit
• Independent review: CLEAR / APPROVE, no findings

UI evidence

Not applicable; no UI behavior changed.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-08-29T13:02:49.888570Z	2d88c44	PR opened

ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 2d88c44da3

ℹ️ 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]

Exclude unstaged deletions from documentation lint

When a contributor deletes or renames a tracked Markdown file and runs npm run docs:lint before staging it, git ls-files --cached still returns the old path, so the subsequent readFile throws ENOENT and aborts instead of linting the current working tree. Filter deleted paths (for example via Git's deletion state) or handle missing files so the documented validation workflow works with ordinary unstaged edits.

Useful? React with 👍 / 👎.