kenyang/loong-workflow
1
0
Fork 0
forked from Octopus/octopus-workflow
Code Pull Requests Activity

v0.1.5: standalone-readability pass — delink --strip provenance mode ([TT-NNNN]), Tier-2 dangling refs neutralized, verify/review-code giant skills split into reference/ on-demand files; guards now runtime-neutral (bun|node)

Browse Source
This commit is contained in:
kenyang
2026-09-25 00:09:37 +08:00
parent d6567b1842
commit 88204a90c8
74 changed files with 1417 additions and 1358 deletions
Download Patch File Download Diff File Expand all files Collapse all files
core/rules/stash-discipline.md
+5 -5
View File
@@ -13,8 +13,8 @@ each other's entries and one session's `pop` returns the other session's
content — or `drop`/`clear` wipes uncommitted work belonging to a session in
a different worktree.
This failure mode has already destroyed completed work in production ([org-internal #1655] /
[org-internal #1629] — a finished 25-test implementation overwritten on the shared stack).
This failure mode has already destroyed completed work in production ([TT-1655] /
[TT-1629] — a finished 25-test implementation overwritten on the shared stack).
**Iron Law: NEVER use `git stash` (or `git stash pop` / `push` / `drop` /
`clear` / `apply`) inside an octopus worktree.**
@@ -70,7 +70,7 @@ If you must `git checkout <base>` to reproduce a failure but the worktree is
dirty, do **not** reach for stash. Instead:
- WIP-commit first (option 1), or
- Use the lifecycle-managed scratch-worktree script ([org-internal #2790]) to materialise
- Use the lifecycle-managed scratch-worktree script ([TT-2790]) to materialise
the base commit in a *separate* worktree and run the failing test there:
```bash
@@ -82,7 +82,7 @@ dirty, do **not** reach for stash. Instead:
classification check. The script registers the worktree, symlinks
`node_modules` from the source checkout when `bun.lock` matches, and the
`sweep` backstop reclaims worktrees abandoned by dying sessions — bare
`git worktree add /tmp/octopus/...` has no such recovery ([org-internal #2790]).
`git worktree add /tmp/octopus/...` has no such recovery ([TT-2790]).
### Exceptions
@@ -110,4 +110,4 @@ dirty, do **not** reach for stash. Instead:
If a parallel-session stash collision happens again despite this rule, treat
it as a Sev-2 process incident: stop work, recover via
`git fsck --unreachable` / `git log -g --walk-reflogs stash`, open a follow-up
referencing [org-internal #1655].
referencing [TT-1655].