@overdeck/core 0.45.1 → 0.45.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/docs-index.sqlite
CHANGED
|
Binary file
|
package/package.json
CHANGED
|
@@ -0,0 +1,10 @@
|
|
|
1
|
+
---
|
|
2
|
+
scope: universal
|
|
3
|
+
---
|
|
4
|
+
### NEVER delete the `overdeck-state` branch
|
|
5
|
+
|
|
6
|
+
**Never delete the `overdeck-state` branch — not the local ref, not the remote.** This applies to every project, every harness, every role. Forbidden in all forms: `git branch -d/-D overdeck-state`, `git push origin --delete overdeck-state`, `git push origin :overdeck-state`, deleting it through the GitHub UI/API, and removing the state worktree at `${OVERDECK_HOME}/state/<project>/` to get the branch "unlocked" for deletion.
|
|
7
|
+
|
|
8
|
+
`overdeck-state` is the same-repo orphan branch holding the project's permanent pipeline state (PAN-2541): `records/`, `specs/`, `continues/`, `drafts/`, `.beads/`, and the migration-complete marker. It shares no history with `main` — deleting it destroys the canonical state plane, and no code branch can restore it. The branches also never merge in either direction; guards enforce that mechanically, so never bypass them with `--no-verify` or `--allow-unrelated-histories`.
|
|
9
|
+
|
|
10
|
+
If an operation seems to require deleting or recreating `overdeck-state`, stop and surface to the operator — there is no agent-side exception.
|