session-orchestrator 3.16.0

package/pi/extensions/session-orchestrator.ts

@@ -0,0 +1,25 @@
+import path from "node:path";
+import { fileURLToPath } from "node:url";
+
+import { runPiHookEvent } from "../../scripts/lib/pi-hook-bridge.mjs";
+
+const EXTENSION_DIR = path.dirname(fileURLToPath(import.meta.url));
+const PLUGIN_ROOT = path.resolve(EXTENSION_DIR, "../..");
+
+async function dispatch(piEventName: string, event: Record<string, unknown>, ctx: Record<string, unknown>) {
+  const result = await runPiHookEvent(piEventName, event, ctx, { pluginRoot: PLUGIN_ROOT });
+  if (result.block) {
+    return { block: true, reason: result.reason ?? "Blocked by Session Orchestrator" };
+  }
+  return undefined;
+}
+
+export default function sessionOrchestratorPiExtension(pi: {
+  on: (event: string, handler: (event: Record<string, unknown>, ctx: Record<string, unknown>) => unknown) => void;
+}) {
+  pi.on("session_start", async (event, ctx) => dispatch("session_start", event, ctx));
+  pi.on("session_shutdown", async (event, ctx) => dispatch("session_shutdown", event, ctx));
+  pi.on("tool_call", async (event, ctx) => dispatch("tool_call", event, ctx));
+  pi.on("tool_result", async (event, ctx) => dispatch("tool_result", event, ctx));
+  pi.on("agent_end", async (event, ctx) => dispatch("agent_end", event, ctx));
+}

package/pi/prompts/autopilot-multi.md

@@ -0,0 +1,12 @@
+---
+description: Multi-story autopilot orchestrator — runs N parallel issue pipelines in isolated git worktrees (v3.6 Phase D thin-slice)
+argument-hint: "[--dry-run|--apply] [--max-stories=N] [--max-hours=H] [--inactivity-timeout=S] [--stall-seconds=S] [--draft-mr=off|on-loop-start|on-green] [--json] [--verbose]"
+---
+
+# /autopilot-multi
+
+Use the Session Orchestrator command definition at `commands/autopilot-multi.md`.
+
+Arguments: $@
+
+Read that command file and follow it exactly. When it references `$ARGUMENTS`, substitute the arguments above. Keep all Session Orchestrator platform fallbacks intact.

package/pi/prompts/autopilot.md

@@ -0,0 +1,12 @@
+---
+description: Autonomous session-orchestration loop with kill-switches (Phase C-1.b — all 10 kill-switches shipped)
+argument-hint: "[--headless] [--verbose] [--max-sessions=N] [--max-hours=H] [--confidence-threshold=0.X] [--dry-run]"
+---
+
+# /autopilot
+
+Use the Session Orchestrator command definition at `commands/autopilot.md`.
+
+Arguments: $@
+
+Read that command file and follow it exactly. When it references `$ARGUMENTS`, substitute the arguments above. Keep all Session Orchestrator platform fallbacks intact.

package/pi/prompts/bootstrap.md

@@ -0,0 +1,12 @@
+---
+description: Scaffold the minimum repo structure required by session-orchestrator
+argument-hint: "[--upgrade <tier>]"
+---
+
+# /bootstrap
+
+Use the Session Orchestrator command definition at `commands/bootstrap.md`.
+
+Arguments: $@
+
+Read that command file and follow it exactly. When it references `$ARGUMENTS`, substitute the arguments above. Keep all Session Orchestrator platform fallbacks intact.

package/pi/prompts/brainstorm.md

@@ -0,0 +1,12 @@
+---
+description: Run a lightweight Socratic design dialogue (3-5 AUQ rounds) and write a spec markdown file before any implementation work. Use BEFORE /plan feature when scope/UX is ambiguous.
+argument-hint: "[topic-or-feature-slug]"
+---
+
+# /brainstorm
+
+Use the Session Orchestrator command definition at `commands/brainstorm.md`.
+
+Arguments: $@
+
+Read that command file and follow it exactly. When it references `$ARGUMENTS`, substitute the arguments above. Keep all Session Orchestrator platform fallbacks intact.

package/pi/prompts/close.md

@@ -0,0 +1,11 @@
+---
+description: End session with verification, commits, and documentation
+---
+
+# /close
+
+Use the Session Orchestrator command definition at `commands/close.md`.
+
+Arguments: $@
+
+Read that command file and follow it exactly. When it references `$ARGUMENTS`, substitute the arguments above. Keep all Session Orchestrator platform fallbacks intact.

package/pi/prompts/debug.md

@@ -0,0 +1,12 @@
+---
+description: Run a 4-phase systematic debugging investigation before proposing any fix. Iron Law — NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST. Produces a `.orchestrator/debug/` artifact the fixer agent must reference.
+argument-hint: "[bug-description-or-issue-ref]"
+---
+
+# /debug
+
+Use the Session Orchestrator command definition at `commands/debug.md`.
+
+Arguments: $@
+
+Read that command file and follow it exactly. When it references `$ARGUMENTS`, substitute the arguments above. Keep all Session Orchestrator platform fallbacks intact.

package/pi/prompts/discovery.md

@@ -0,0 +1,12 @@
+---
+description: Systematic quality discovery and issue detection
+argument-hint: "[all|code|infra|ui|arch|session|audit|vault|feature] [--since <git-ref>] [--full]"
+---
+
+# /discovery
+
+Use the Session Orchestrator command definition at `commands/discovery.md`.
+
+Arguments: $@
+
+Read that command file and follow it exactly. When it references `$ARGUMENTS`, substitute the arguments above. Keep all Session Orchestrator platform fallbacks intact.

package/pi/prompts/dispatcher.md

@@ -0,0 +1,12 @@
+---
+description: Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command
+argument-hint: "[--dry-run] [--repo <name>]"
+---
+
+# /dispatcher
+
+Use the Session Orchestrator command definition at `commands/dispatcher.md`.
+
+Arguments: $@
+
+Read that command file and follow it exactly. When it references `$ARGUMENTS`, substitute the arguments above. Keep all Session Orchestrator platform fallbacks intact.

package/pi/prompts/eval.md

@@ -0,0 +1,12 @@
+---
+description: Run an honest session-process evaluation (Standard v1, aiat-llm-eval/1.0) — score the last completed session against the pre-registered rubric-v1 dimensions
+argument-hint: "[--session <id>] [--no-write] [--verify <run-id>]"
+---
+
+# /eval
+
+Use the Session Orchestrator command definition at `commands/eval.md`.
+
+Arguments: $@
+
+Read that command file and follow it exactly. When it references `$ARGUMENTS`, substitute the arguments above. Keep all Session Orchestrator platform fallbacks intact.

package/pi/prompts/evolve.md

@@ -0,0 +1,12 @@
+---
+description: Extract session patterns into reusable learnings
+argument-hint: "[analyze|review|list|dialectic [--apply]]"
+---
+
+# /evolve
+
+Use the Session Orchestrator command definition at `commands/evolve.md`.
+
+Arguments: $@
+
+Read that command file and follow it exactly. When it references `$ARGUMENTS`, substitute the arguments above. Keep all Session Orchestrator platform fallbacks intact.

package/pi/prompts/go.md

@@ -0,0 +1,12 @@
+---
+description: Approve session plan and begin wave execution
+argument-hint: "[optional instructions]"
+---
+
+# /go
+
+Use the Session Orchestrator command definition at `commands/go.md`.
+
+Arguments: $@
+
+Read that command file and follow it exactly. When it references `$ARGUMENTS`, substitute the arguments above. Keep all Session Orchestrator platform fallbacks intact.

package/pi/prompts/grill.md

@@ -0,0 +1,12 @@
+---
+description: Stress-test a plan, design, or PRD before any build — relentless one-question-at-a-time interrogation that hunts contradictions against the code and challenges assumptions. Composable; no HARD-GATE.
+argument-hint: "[file-path-or-topic]"
+---
+
+# /grill
+
+Use the Session Orchestrator command definition at `commands/grill.md`.
+
+Arguments: $@
+
+Read that command file and follow it exactly. When it references `$ARGUMENTS`, substitute the arguments above. Keep all Session Orchestrator platform fallbacks intact.

package/pi/prompts/harness-audit.md

@@ -0,0 +1,12 @@
+---
+description: Run the harness audit and report the rubric score for this repository
+argument-hint: ""
+---
+
+# /harness-audit
+
+Use the Session Orchestrator command definition at `commands/harness-audit.md`.
+
+Arguments: $@
+
+Read that command file and follow it exactly. When it references `$ARGUMENTS`, substitute the arguments above. Keep all Session Orchestrator platform fallbacks intact.

package/pi/prompts/memory-cleanup.md

@@ -0,0 +1,12 @@
+---
+description: Manual memory consolidation — review, consolidate, and prune memory files (Dream-equivalent)
+argument-hint: "[--dry-run | --apply-pending]"
+---
+
+# /memory-cleanup
+
+Use the Session Orchestrator command definition at `commands/memory-cleanup.md`.
+
+Arguments: $@
+
+Read that command file and follow it exactly. When it references `$ARGUMENTS`, substitute the arguments above. Keep all Session Orchestrator platform fallbacks intact.

package/pi/prompts/persona-panel.md

@@ -0,0 +1,12 @@
+---
+description: Run a parallel multi-persona domain-expert review panel against a file, directory, or output range
+argument-hint: "<target> [--personas <names,...>] [--mode <voting|hard-gate|summary>] [--threshold <M-of-N|all|any>] [--grounding <off|re-derive>] [--dry-run]"
+---
+
+# /persona-panel
+
+Use the Session Orchestrator command definition at `commands/persona-panel.md`.
+
+Arguments: $@
+
+Read that command file and follow it exactly. When it references `$ARGUMENTS`, substitute the arguments above. Keep all Session Orchestrator platform fallbacks intact.

package/pi/prompts/plan.md

@@ -0,0 +1,12 @@
+---
+description: Plan a new project, feature, or retrospective with structured requirement gathering
+argument-hint: "[new|feature|retro]"
+---
+
+# /plan
+
+Use the Session Orchestrator command definition at `commands/plan.md`.
+
+Arguments: $@
+
+Read that command file and follow it exactly. When it references `$ARGUMENTS`, substitute the arguments above. Keep all Session Orchestrator platform fallbacks intact.

package/pi/prompts/portfolio.md

@@ -0,0 +1,12 @@
+---
+description: Aggregate cross-repo issue/MR/CI health across vault-registered projects into a single Markdown dashboard
+argument-hint: "[--dry-run] [--repo <name>]"
+---
+
+# /portfolio
+
+Use the Session Orchestrator command definition at `commands/portfolio.md`.
+
+Arguments: $@
+
+Read that command file and follow it exactly. When it references `$ARGUMENTS`, substitute the arguments above. Keep all Session Orchestrator platform fallbacks intact.

package/pi/prompts/reconcile.md

@@ -0,0 +1,12 @@
+---
+description: Reconcile learnings into .claude/rules/ proposals — on-demand version of session-end Phase 3.6.8
+argument-hint: "[--dry-run]"
+---
+
+# /reconcile
+
+Use the Session Orchestrator command definition at `commands/reconcile.md`.
+
+Arguments: $@
+
+Read that command file and follow it exactly. When it references `$ARGUMENTS`, substitute the arguments above. Keep all Session Orchestrator platform fallbacks intact.

package/pi/prompts/repo-audit.md

@@ -0,0 +1,12 @@
+---
+description: Run a 9-category baseline compliance audit on the current repository
+argument-hint: ""
+---
+
+# /repo-audit
+
+Use the Session Orchestrator command definition at `commands/repo-audit.md`.
+
+Arguments: $@
+
+Read that command file and follow it exactly. When it references `$ARGUMENTS`, substitute the arguments above. Keep all Session Orchestrator platform fallbacks intact.

package/pi/prompts/session.md

@@ -0,0 +1,12 @@
+---
+description: Start a development session (housekeeping, feature, deep)
+argument-hint: "[housekeeping|feature|deep]"
+---
+
+# /session
+
+Use the Session Orchestrator command definition at `commands/session.md`.
+
+Arguments: $@
+
+Read that command file and follow it exactly. When it references `$ARGUMENTS`, substitute the arguments above. Keep all Session Orchestrator platform fallbacks intact.

package/pi/prompts/spinout.md

@@ -0,0 +1,12 @@
+---
+description: Guided 5-step venture-spinout / sanitized-fork runbook (copy + fresh-init + SNAPSHOT-FREEZE) — interactive, not scripted
+argument-hint: "[--type venture|snapshot] [--dry-run]"
+---
+
+# /spinout
+
+Use the Session Orchestrator command definition at `commands/spinout.md`.
+
+Arguments: $@
+
+Read that command file and follow it exactly. When it references `$ARGUMENTS`, substitute the arguments above. Keep all Session Orchestrator platform fallbacks intact.

package/pi/prompts/sunset-review.md

@@ -0,0 +1,12 @@
+---
+description: Identify unused / near-zero-use / stale skills, agents, and commands as Demote or Retire candidates (read-only; never deletes)
+argument-hint: "[--kind skill|agent|command] [--window-days N]"
+---
+
+# /sunset-review
+
+Use the Session Orchestrator command definition at `commands/sunset-review.md`.
+
+Arguments: $@
+
+Read that command file and follow it exactly. When it references `$ARGUMENTS`, substitute the arguments above. Keep all Session Orchestrator platform fallbacks intact.

package/pi/prompts/templates-ack.md

@@ -0,0 +1,12 @@
+---
+description: Acknowledge templates-first policy for the current session — bypasses the pre-bash-templates-first hook for the remainder of the session
+argument-hint: "[optional-reason]"
+---
+
+# /templates-ack
+
+Use the Session Orchestrator command definition at `commands/templates-ack.md`.
+
+Arguments: $@
+
+Read that command file and follow it exactly. When it references `$ARGUMENTS`, substitute the arguments above. Keep all Session Orchestrator platform fallbacks intact.

package/pi/prompts/test.md

@@ -0,0 +1,12 @@
+---
+description: Agentic end-to-end test orchestrator — drive web/macOS flows, evaluate UX rubric, reconcile issues
+argument-hint: "[scope|profile-name] [--since <git-ref>] [--full]"
+---
+
+# /test
+
+Use the Session Orchestrator command definition at `commands/test.md`.
+
+Arguments: $@
+
+Read that command file and follow it exactly. When it references `$ARGUMENTS`, substitute the arguments above. Keep all Session Orchestrator platform fallbacks intact.

package/rules/_index.md

@@ -0,0 +1,51 @@
+# Rules Library — Canonical Index
+
+Source of truth for `.claude/rules/` vendored into consumer repos via `/bootstrap --sync-rules`.
+
+## Entry syntax (issue #722 Epic A Wave 3)
+
+Each bullet is:
+
+```
+- `<category>/<file>.md` — description
+- `<category>/<file>.md` — description [archetypes: archetype-a, archetype-b]
+```
+
+The optional trailing `[archetypes: ...]` tag is an allowlist, matched
+case-insensitively against the consumer repo's resolved archetype (see
+`scripts/lib/rules-sync.mjs` § archetype resolution). Known values include
+`static-html`, `node-minimal`, `nextjs-minimal`, `python-uv`, plus any
+baseline project type (`nextjs-saas`, `express-service`, `docker-service`,
+`monorepo-oss`, `swift-app`, `cli-tool`, `swift-menubar-app`,
+`tauri-desktop`, `astro-content-site`, `go-service`).
+
+- **Absent tag** — universal. Vendored to every consumer repo regardless of
+  archetype. This is the default and is fully backward compatible with every
+  entry written before Wave 3.
+- **Present tag** — scoped. Vendored ONLY when the consumer repo's resolved
+  archetype matches one of the listed values (case-insensitive). Skipped
+  otherwise, with a `skipped[]` reason of `archetype-mismatch` (known,
+  non-matching archetype) or `archetype-unknown` (no resolvable archetype on
+  the target).
+
+## always-on (vendored to every consumer repo)
+
+- `always-on/parallel-sessions.md` — PSA-001/002/003/004 multi-session discipline
+- `always-on/commit-discipline.md` — atomic commits, stage-by-name, no `git add .`
+- `always-on/npm-quality-gates.md` — the typecheck + test + lint triad before commit
+
+## opt-in-stack (vendored on match)
+
+- `opt-in-stack/backend.md` — server actions, API routes, Express services, AI provider abstraction, observability [archetypes: nextjs-saas, express-service, docker-service]
+- `opt-in-stack/backend-data.md` — Supabase/Postgres, RLS performance, migrations, caching, N+1 prevention [archetypes: nextjs-saas]
+- `opt-in-stack/frontend.md` — React/Next.js, component design, styling, accessibility, forms [archetypes: nextjs-saas, nextjs-minimal]
+- `opt-in-stack/swift.md` — Swift 5.9+/SwiftUI, Swift Testing, networking, error handling, SPM [archetypes: swift-app, swift-menubar-app]
+- `opt-in-stack/security-web.md` — CSRF, CSP/security headers, rate limiting, output encoding [archetypes: nextjs-saas, nextjs-minimal, express-service]
+
+## opt-in-domain (vendored on match)
+
+- `opt-in-domain/prompt-caching.md` — Anthropic prompt caching (breakpoint placement, TTL selection, pre-warming, verification) [archetypes: nextjs-saas, express-service, docker-service, monorepo-oss, cli-tool]
+
+## Sync mechanism
+
+Consumer repos receive these files via `/bootstrap --sync-rules`. Re-running the command syncs every manifest category that has entries: universal entries always vendor, and archetype-tagged entries vendor only when the consumer repo's resolved archetype matches. Plugin-sourced files are overwritten while local rules are preserved (copy-on-write via the `<!-- source: session-orchestrator plugin ... -->` header on plugin files). Category entries must not share a basename, because all synced files flatten into `.claude/rules/`.

package/rules/always-on/commit-discipline.md

@@ -0,0 +1,26 @@
+<!-- source: session-orchestrator plugin (canonical: rules/always-on/commit-discipline.md) -->
+# Commit Discipline (Always-on)
+
+Every commit in a shared repository is a permanent, public record. Sloppy staging or ambiguous commit messages erode git history quality and make bisect, revert, and code review harder for everyone — including future-you. These rules apply to all contributors regardless of role or urgency.
+
+## Rules
+
+- **Stage by filename, never by glob.** Use `git add <specific-file>` rather than `git add .` or `git add -A`. Blanket staging silently includes unrelated in-progress work from parallel sessions, leftover debug files, and accidental editor artifacts.
+- **Review `git diff --cached` before every commit.** Verify each staged line is intentional. If you see changes you did not author, unstage them and ask the user before proceeding.
+- **Use Conventional Commits format.** Prefix every commit message with a type: `feat`, `fix`, `chore`, `docs`, `refactor`, `test`, `perf`, or `ci`. Example: `feat(auth): add JWT refresh endpoint`. This feeds automated changelogs and makes intent unambiguous.
+- **Describe WHY, not WHAT.** The diff already shows what changed. The commit message should explain the motivation: what problem this solves, what constraint it respects, or what decision it encodes.
+- **Never amend a commit you did not create.** `git commit --amend` rewrites history. Amending someone else's commit — even to fix a typo — destroys their authorship record and can corrupt parallel-session work in shared branches.
+- **One logical change per commit.** If your work touches unrelated concerns, split it into separate commits. Atomic commits are easier to review, cherry-pick, and revert without side-effects.
+- **Never use `--no-verify`.** Pre-commit hooks exist for a reason. If a hook fails, fix the underlying issue rather than bypassing the gate.
+
+## Anti-Patterns
+
+- Running `git add .` in a worktree where another agent is active — you will commit their partial work.
+- Writing commit messages like `fix stuff` or `wip` — these carry no information and pollute the log.
+- Amending pushed commits — this forces all collaborators to reset, breaking parallel sessions.
+- Squashing without reading — blindly squash-merging can discard important intermediate state or commit attribution.
+- Committing with `--no-verify` to "just get it in" — the hook is protecting an invariant; skipping it ships a broken state.
+
+## See Also
+
+- `parallel-sessions.md` PSA-004 — the sister rule covering parallel-session staging discipline.

package/rules/always-on/npm-quality-gates.md

@@ -0,0 +1,26 @@
+<!-- source: session-orchestrator plugin (canonical: rules/always-on/npm-quality-gates.md) -->
+# Quality Gates (Always-on)
+
+Shipping code with known type errors, failing tests, or lint violations is a false economy: it offloads cost from the author onto every reviewer and future maintainer. The triad — typecheck, test, lint — is the minimum bar before any commit enters the branch.
+
+## Rules
+
+- **Run the full triad before every commit.** The three gates are typecheck, test, and lint. All three must pass. Skipping any one is not acceptable even under time pressure.
+- **Commands come from Session Config.** Read `test-command`, `typecheck-command`, and `lint-command` from the project's `## Session Config` block in `CLAUDE.md`. These override any globally assumed defaults. This plugin's own gate runner assumes `npm` (`npm test`, `npm run typecheck`, `npm run lint`) — other projects may use `pnpm`, `yarn`, `uv run pytest`, or `cargo test`. Always use the project-configured commands.
+- **CI must run the same gate.** Whatever commands are in Session Config, the CI pipeline must invoke the same commands in the same order. Divergence between local gates and CI is a configuration smell that will produce "passes locally, fails in CI" incidents.
+- **Never commit with known TypeScript errors.** If `npm run typecheck` (or equivalent) fails, stop and fix the errors. Do not mark them as `@ts-ignore` or `@ts-expect-error` without an explicit comment explaining the suppression and a linked issue to resolve it properly.
+- **Never commit with failing tests.** If tests are red, either fix the code or explicitly skip the test with a comment explaining why and a linked issue for follow-up. Never delete a test to make the suite green.
+- **Never use `--no-verify`.** Pre-commit hooks enforce these gates at the git layer. Bypassing them with `--no-verify` ships a broken state to collaborators.
+- **Fix root causes, not symptoms.** Suppression flags, `any` casts, and disabled lint rules are last resorts. When you reach for them, leave a `// TODO(#<issue>)` comment with a concrete follow-up.
+
+## Anti-Patterns
+
+- Running only one of the three gates before committing — each gate catches a different class of defect.
+- Using `npm run typecheck || true` in CI to "ignore" type errors — this silently regresses the codebase.
+- Wrapping a failing test in `describe.skip` without a linked issue — the failure disappears from view but the bug persists.
+- Differing commands between local and CI (e.g., `pnpm test` locally vs `npm test` in CI) — produces unreliable feedback loops.
+- Committing generated files with type errors and marking them `@ts-nocheck` — the generator needs fixing, not the output.
+
+## See Also
+
+- Session Config keys: `test-command`, `typecheck-command`, `lint-command` — set in `CLAUDE.md` under `## Session Config`.

package/rules/always-on/parallel-sessions.md

@@ -0,0 +1,43 @@
+<!-- source: session-orchestrator plugin (canonical: rules/always-on/parallel-sessions.md) -->
+# Parallel Session Awareness (Always-on)
+
+Multiple Claude Code sessions may be active in the same working directory simultaneously. Another agent may be editing files, creating commits, or running builds right now. Treat the repo as a shared workspace, not a private sandbox.
+
+## Recognizing Parallel Work (PSA-001: Detect Before Acting)
+- **Unexpected git status changes:** Files modified or staged that are not part of your current task likely belong to another session.
+- **Unfamiliar commits:** New entries in `git log` that you did not create mean another agent (or the user manually) committed work.
+- **Spontaneous errors:** Build failures, type errors, or test failures in code you did not touch may be in-progress work from another session — not pre-existing bugs.
+- **Files changed between reads:** If a file's content differs from what you read moments ago, another session likely edited it.
+- **New untracked files:** Files appearing in `git status` that you did not create belong to someone else's work.
+
+## Behavioral Guidance (PSA-002: Ask, Don't Assume)
+- **When you detect signs of parallel work, stop and ask the user:** "I notice changes I didn't make (e.g., modified files in git status, new commits). Is another session active?"
+- **Never "fix" code outside your task scope.** Errors in files you are not working on may be intentional intermediate states from another session.
+- **Stay in your lane.** Only read, create, modify, and delete files directly relevant to your assigned task.
+- **If blocked by external changes, ask the user** rather than reverting, resetting, or working around them.
+- **Track your own footprint.** Be aware of which files you have created or modified. Your commits should contain only your changes.
+
+## Destructive Action Safeguards (PSA-003: Never Destroy What You Didn't Create)
+These commands require explicit user confirmation even in normal operation. When parallel work is suspected, they are **forbidden** without user approval:
+- **`git reset` (any form)** — destroys staged or committed work that may belong to another session.
+- **`git checkout -- <file>`** — discards uncommitted changes another session is actively building.
+- **`git clean -f`** — deletes untracked files another session created.
+- **`git stash`** — captures another session's changes into a stash they cannot find.
+- **`rm` / delete of files you did not create** — may remove work-in-progress from another session.
+- **`git revert` of commits you did not make** — undoes another session's completed work.
+- **`git push --force`** — rewrites shared history (dangerous even without parallel sessions).
+
+Before running any of the above, ask: "Did I create this file/commit/change? If not, it is not mine to touch."
+
+## Commit Discipline (PSA-004: Isolate Your Changes)
+- **Stage files individually** (`git add <file>`) rather than `git add .` or `git add -A`, which may sweep in another session's work.
+- **Review `git diff --cached` before committing** to verify every staged change is yours.
+- **If you see unfamiliar changes in the diff, unstage them** and ask the user.
+- **Never amend a commit you did not create.**
+
+## Anti-Patterns
+- Seeing unfamiliar changes and assuming they are "leftover mess" to clean up — they are likely active work.
+- Running `git reset --hard` to "start fresh" — this destroys all uncommitted work across all sessions.
+- Fixing type errors or lint issues in files outside your scope — the other session will handle their own files.
+- Using `git add .` in a shared workspace — you will commit another session's partial work.
+- Reverting "broken" commits without asking — another session may have intentionally pushed incremental progress.