feat: consolidate TraceDecay V2 PR8-PR13 delivery

.cargo/config.toml

@@ -27,12 +27,11 @@ TRACEDECAY_DISABLE_GLOBAL_DB = { value = "1", force = false }
 # in-process. Installed binaries run outside cargo and are unaffected, but the
 # profile does apply to `cargo run` — use the installed binary (or set
 # TRACEDECAY_DATA_DIR yourself) for real `daemon install-service` runs.
-# Enforced by tests/test_profile_isolation_test.rs.
+# Enforced by tests/core_cli_suite/test_profile_isolation_test.rs.
 TRACEDECAY_DATA_DIR = { value = "target/test-profile/.tracedecay", force = false, relative = true }
 
 [alias]
 # Local default for the full Rust test suite. Requires cargo-nextest:
 # https://nexte.st/docs/installation/pre-built-binaries/
-test-all = "nextest run --workspace --no-fail-fast"
-test-ci = "nextest run --workspace --no-fail-fast"
-dogfood = "run --quiet --release --bin tracedecay -- dogfood"
+test-all = "nextest run --workspace --all-features --no-fail-fast"
+test-ci = "nextest run --workspace --all-features --no-fail-fast"

.claude/skills/evaluating-hook-hints/SKILL.md

@@ -9,7 +9,7 @@ Use this skill for TraceDecay repo development only. These are repo-local dev in
 
 ## Workflow
 
-1. Start with TraceDecay context for `src/hooks/tool_hints.rs`, `src/hooks/tool_hints/classifiers.rs`, `src/hooks/tool_hints/evals.rs`, host adapters in `src/hooks/{codex,claude,cursor}.rs`, and recent transcript evidence.
+1. Start with TraceDecay context for `src/hooks/tool_hints.rs`, `src/hooks/tool_hints/classifiers.rs`, the `src/hooks/tool_hints/evals/` module (`mod.rs` plus `host_cases.rs`), host adapters in `src/hooks/{codex,claude,cursor}.rs`, and recent transcript evidence.
 2. Render model-visible hook input when judging verbosity:
    `scripts/render-codex-hook-inputs.py --glob '/home/zack/.codex/sessions/**/*.jsonl' --all --limit 5 --max-chars 800`.
 3. Run deterministic evals before behavior edits:
@@ -22,7 +22,7 @@ Use this skill for TraceDecay repo development only. These are repo-local dev in
 ## Acceptance Rules
 
 - Hints should be contextual and short; avoid generic TraceDecay availability boilerplate.
-- Real-world transcript cases and synthetic cases should both be represented in `src/hooks/tool_hints/evals.rs`.
+- Real-world transcript cases and synthetic cases should both be represented in `src/hooks/tool_hints/evals/` (`host_cases.rs` holds the per-host scenarios). The module is `#[cfg(test)]`, so it only compiles under a test profile.
 - A normal user prompt should not be wrapped into a noisy `UserPromptSubmit hook (completed)` model-visible user message.
 - No hint is a valid outcome when the request does not need TraceDecay guidance.
 - Repeated native behavior should get at most one initial hint plus one later escalation per category, bounded by the session budget.

.claude/skills/inspecting-automation-cycles/SKILL.md

@@ -18,9 +18,9 @@ analytics prove whether generated output was adopted.
 3. For failures or suspicious skips, open the relevant artifact with
    `tracedecay_automation_run_artifact_view` or
    `tracedecay tool automation_run_artifact_view --args ...`.
-4. Inspect model-managed memory outcomes plus configured managed-skill review
-   queues: `tracedecay automation facts list`, dashboard telemetry, and
-   `tracedecay_skill_list --state pending`.
+4. Inspect model-managed memory outcomes plus active managed-skill adoption:
+   `tracedecay automation facts list`, dashboard telemetry, and
+   `tracedecay_skill_list --state active`.
 5. Check adoption evidence: `tracedecay analytics diagnostics --all --no-sync`,
    `tracedecay sessions search "mcp__tracedecay" --provider all`, and managed
    skill usage counts.
@@ -32,15 +32,15 @@ analytics prove whether generated output was adopted.
 | `scheduler_interval_not_elapsed` | Healthy throttling | Count only, do not fix. |
 | `scheduler_lock_active` | Another run owns the loop | Check age before calling stale. |
 | `no_new_session_activity` | Nothing new to process | Verify transcript ingest if surprising. |
-| `validation_gate` artifact | Mutation passed validation | Inspect apply-policy state or dashboard artifact. |
+| `validation_gate` artifact | Mutation passed validation | Inspect automatic application/deployment receipts. |
 | Many fact proposal records | Inspect validation/apply telemetry | Use `tracedecay:project-memory`. |
 | Active managed skills with zero use | Adoption telemetry gap | Use `tracedecay:diagnosing-analytics`. |
 
 ## Guardrails
 
 - Prefer read-only inspection. Do not mutate fact records.
-- Do not approve, reject, delete, or apply managed-skill drafts unless the user
-  explicitly asked for mutation.
+- Validated skill-writer output activates and deploys automatically; inspect
+  receipts rather than waiting for a manual gate.
 - Do not treat skipped runs as failures until grouped by skip reason and age.
 - Avoid parallel `tracedecay_skill_view` calls against one profile while
   automation may write usage ledgers. If a usage read reports a truncated JSON
@@ -50,6 +50,6 @@ analytics prove whether generated output was adopted.
 
 ## Deliverable
 
-Report task/status counts, the exact run or artifact ids inspected, apply-policy
-state, adoption gaps, and the next concrete command for any mutation the user
-should choose.
+Report task/status counts, the exact run or artifact ids inspected, automatic
+application/deployment state, adoption gaps, and the next concrete command for
+any direct operator override the user should choose.