feat(cli): make case distributable — zero hard-coded paths, CLI subcommands, data directory

.gitignore

@@ -4,16 +4,23 @@
 .case-manual-tested
 .case-reviewed
 
-# Active tasks (ephemeral per-run state, moved to tasks/done/ after merge)
+# Phase 3: state moved to ~/.config/case/. These rules cover both the legacy
+# in-repo paths (during the transition window) and any state accidentally written
+# under the repo root.
 tasks/active/
-
-# Proposed amendments (staged for human review, not committed until approved)
+tasks/done/
+docs/learnings/
 docs/proposed-amendments/*.md
 !docs/proposed-amendments/.gitkeep
-
-# Run log (append-only, machine-generated)
 docs/run-log.jsonl
+docs/agent-versions/
+
+# Ideation artifacts (generated HTML/MD specs)
+docs/ideation/
 
 # Build artifacts
 node_modules/
 dist/
+
+# bun artifacts
+*.bun-build

AGENTS.md

@@ -8,7 +8,7 @@ Humans steer. Agents execute. When agents struggle, fix the harness.
 Run the session-start script to gather context before doing anything else:
 
 ```bash
-SESSION=$(bash /Users/nicknisi/Developer/case/scripts/session-start.sh <target-repo-path> --task <task.json>)
+SESSION=$(case session <target-repo-path> --task <task.json>)
 echo "$SESSION"
 ```
 

CONTEXT.md

@@ -4,23 +4,23 @@ Canonical vocabulary for the case pipeline. Every term used in code, specs, and
 
 ## Terms
 
-| Term           | Definition                                                                                                                                                 | Rejected Alternatives                                                   |
-| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- |
-| **task**       | A unit of agent work dispatched by the pipeline. Has a `taskId`, status, and associated event log.                                                         | `job`, `run` (too generic)                                              |
-| **phase**      | A named pipeline stage that produces one `AgentResult`. One of: implement, verify, review, approve, close, retrospective.                                  | `step` (too generic), `stage` (ambiguous with CI)                       |
-| **node**       | A DAG vertex representing one phase execution at a specific revision cycle. E.g., `implement_0`, `verify_1`. Introduced in Phase 3.                        | `vertex` (too academic)                                                 |
-| **status**     | The lifecycle position of a task, derived from pipeline state. One of: active, implementing, verifying, reviewing, evaluating, closing, pr-opened, merged. | `state` (reserved for `PipelineState`, the full reconstructible object) |
-| **state**      | The full reconstructible pipeline state object (`PipelineState`), produced by `reduceEvents()`.                                                            | `snapshot` (used in mill for a different concept)                       |
-| **event**      | An immutable past-tense fact appended to the event log. Events are the source of truth.                                                                    | `action`, `command` (those are imperative; events are facts)            |
-| **projection** | A derived view computed from `PipelineState`. Examples: `TaskJson`, `RunMetrics`, evidence markers.                                                        | `view`, `derivation`                                                    |
-| **runtime**    | The `CaseAgentRuntime` interface that abstracts agent spawn/cancel/tool-creation.                                                                          | `provider` (that's the backing service, not the interface)              |
-| **adapter**    | A concrete implementation of `CaseAgentRuntime` for a specific provider. E.g., `PiRuntimeAdapter`.                                                         | `driver`, `connector`                                                   |
-| **evaluator**  | Collective term for verifier and reviewer — the two phases that assess implementation quality.                                                             | `assessor`, `checker`                                                   |
-| **marker**     | A file written to `.case/<task-slug>/` as evidence of a completed phase. E.g., `tested`, `reviewed`.                                                       | `flag`, `sentinel`                                                      |
-| **evidence**   | Proof that a phase completed successfully. Includes marker files, SHA-256 hashed test output, screenshots.                                                 | `artifact` (too broad)                                                  |
-| **ast-grep rule** | A YAML file defining a structural code pattern to match or ban. Processed by ast-grep against TypeScript ASTs. Lives in `ast-rules/`.                  | `lint rule` (too generic — we also have oxlint)                         |
-| **target rule** | An ast-grep rule enforcing golden principles in target repos. Run by the implementer before committing. Lives in `ast-rules/target/`.                     | `repo rule`, `external rule`                                            |
-| **self-enforcement rule** | An ast-grep rule enforcing case's own codebase invariants. Run in CI and pre-commit. Lives in `ast-rules/self/`.                                 | `internal rule`, `meta rule`                                            |
+| Term                      | Definition                                                                                                                                                 | Rejected Alternatives                                                   |
+| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- |
+| **task**                  | A unit of agent work dispatched by the pipeline. Has a `taskId`, status, and associated event log.                                                         | `job`, `run` (too generic)                                              |
+| **phase**                 | A named pipeline stage that produces one `AgentResult`. One of: implement, verify, review, approve, close, retrospective.                                  | `step` (too generic), `stage` (ambiguous with CI)                       |
+| **node**                  | A DAG vertex representing one phase execution at a specific revision cycle. E.g., `implement_0`, `verify_1`. Introduced in Phase 3.                        | `vertex` (too academic)                                                 |
+| **status**                | The lifecycle position of a task, derived from pipeline state. One of: active, implementing, verifying, reviewing, evaluating, closing, pr-opened, merged. | `state` (reserved for `PipelineState`, the full reconstructible object) |
+| **state**                 | The full reconstructible pipeline state object (`PipelineState`), produced by `reduceEvents()`.                                                            | `snapshot` (used in mill for a different concept)                       |
+| **event**                 | An immutable past-tense fact appended to the event log. Events are the source of truth.                                                                    | `action`, `command` (those are imperative; events are facts)            |
+| **projection**            | A derived view computed from `PipelineState`. Examples: `TaskJson`, `RunMetrics`, evidence markers.                                                        | `view`, `derivation`                                                    |
+| **runtime**               | The `CaseAgentRuntime` interface that abstracts agent spawn/cancel/tool-creation.                                                                          | `provider` (that's the backing service, not the interface)              |
+| **adapter**               | A concrete implementation of `CaseAgentRuntime` for a specific provider. E.g., `PiRuntimeAdapter`.                                                         | `driver`, `connector`                                                   |
+| **evaluator**             | Collective term for verifier and reviewer — the two phases that assess implementation quality.                                                             | `assessor`, `checker`                                                   |
+| **marker**                | A file written to `.case/<task-slug>/` as evidence of a completed phase. E.g., `tested`, `reviewed`.                                                       | `flag`, `sentinel`                                                      |
+| **evidence**              | Proof that a phase completed successfully. Includes marker files, SHA-256 hashed test output, screenshots.                                                 | `artifact` (too broad)                                                  |
+| **ast-grep rule**         | A YAML file defining a structural code pattern to match or ban. Processed by ast-grep against TypeScript ASTs. Lives in `ast-rules/`.                      | `lint rule` (too generic — we also have oxlint)                         |
+| **target rule**           | An ast-grep rule enforcing golden principles in target repos. Run by the implementer before committing. Lives in `ast-rules/target/`.                      | `repo rule`, `external rule`                                            |
+| **self-enforcement rule** | An ast-grep rule enforcing case's own codebase invariants. Run in CI and pre-commit. Lives in `ast-rules/self/`.                                           | `internal rule`, `meta rule`                                            |
 
 ## Decisions Log