chore: track the teardown-gate, anchor-default and bundle-ignore findingsHEADmain

Four findings arrived from other projects. Each is graded and filed.

Teardown kills the project's tmux session without checking whether another agent is living in it (P2). Shutdown mode has had that gate all along and calls it load-bearing.

The agent-scoped session anchor should probably be the default rather than the opt-in. TMUX_PANE is a fourth option the proposal didn't consider: it's stable across calls and keeps the resolver a pure function of its environment.

Every language bundle appends the same unconditional tooling block, which asserts the opposite of the truth in a project that tracks those files (P3).

The wrap hook's block message names a workflow step instead of the command that clears it, so a project running an older workflow gets no route to the fix (P3).

0 files changed, 0 insertions, 0 deletions