Trevin ChowandClaude Opus 4.7 d1436f4f28 docs(release): add drift recovery playbook and merge-policy rule ...

Captures the learnings from the direct-to-main drift incident so future
investigations don't have to rediscover the file relationships, the
decision tree, or why manifest manual edits are sometimes legitimate.

New solution doc `docs/solutions/workflow/release-please-version-drift-recovery.md`:
- File relationship map showing extra-files, manifest, and linked-versions
- How release-please reads manifest and writes extra-files
- Recovery decision tree (forward-sync vs backward-revert vs release-as pin)
- When manifest manual edits are legitimate (out-of-band recovery)
- The 2026-04-24 incident as worked example

Root AGENTS.md Working Agreement gains a `Merge policy` bullet making
explicit that all changes go through PRs, branch protection enforces
the `test` check, and direct merges have caused real damage. This is
the rule the incident implied but the doc never stated.

Plugin AGENTS.md Versioning Requirements gets a pointer to the recovery
doc so anyone hitting `release:validate` drift finds the playbook on
first stop instead of having to investigate the file relationships
from scratch.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-04-24 14:56:04 -07:00

..

brainstorms

feat(ce-demo-reel): add local save as alternative to catbox upload (#647)

2026-04-22 11:28:44 -07:00

plans

feat(ce-demo-reel): add local save as alternative to catbox upload (#647)

2026-04-22 11:28:44 -07:00

solutions

docs(release): add drift recovery playbook and merge-policy rule

2026-04-24 14:56:04 -07:00

specs

refactor(install): prefer native plugin install across targets (#609)

2026-04-20 18:47:07 -07:00