Parfii-bot 95e2feae0a feat(outcome-hook): PostToolUse:Agent backfills outcome + stubs in ledger

Phase 4 follow-up: the outcome-backfill hook the kei-model-router
needs to learn from. Without an outcome signal the Beta posterior
sees 205 NULL rows and can never converge → router falls back to
top-tier on every spawn. This hook closes that loop.

Spawned by orchestrator as a code-implementer agent (Sonnet 4.6 by
default after the manifest refactor in 50c9e76 — first dogfood proof
that the tier system works end-to-end). Agent returned cleanly with
STATUS-TRUTH MARKER `shipped: functional, stubs: 0`.

Files (3):
- `~/.claude/hooks/agent-outcome-backfill.sh` (73 LOC, /bin/sh) —
  reads PostToolUse:Agent stdin JSON, parses STATUS-TRUTH MARKER from
  `tool_response`, runs `UPDATE agents SET outcome = ?, stubs_count = ?
  WHERE id = ?` via sqlite3 CLI. Defensive on every step (never blocks,
  exits 0 on missing jq / sqlite3 / DB / marker). Bypass:
  `OUTCOME_BACKFILL_BYPASS=1`. Lives outside the kit (system-level).
- `tests/hook-outcome-backfill-test.sh` (79 LOC, /bin/sh) — 8 assertions
  cover: 4 valid outcomes, idempotent re-run, missing marker, bypass
  env, missing sqlite3 (PATH stripped). Run via
  `sh tests/hook-outcome-backfill-test.sh` → "Passed: 8 Failed: 0".
- `_blocks/path-user-hooks.md` — third path-atom following
  user-memory / user-rules convention. Resolves to `~/.claude/hooks/`.
  Lets future manifests reference hook files via
  `path:user-hooks/<file>.sh` opaquely. Registered in registry as
  `atom::md::331b9a34::023e5a08`.

Wiring:
- `~/.claude/settings.json` PostToolUse:Agent matcher chain — appended
  the hook idempotently (jq update preserves existing
  `agent-stub-scan.sh`, `task-timer.sh`, `agent-fork-done.sh`).
- DNA-INDEX regenerated; new path-atom appears in `## Atom (120)`
  section.

Effect: every Agent tool call from now on writes outcome + stubs to
ledger. After ~10-20 invocations the Beta posterior has a usable
prior; after ~50 the router stops defaulting Sonnet to Opus on
unfamiliar tasks. The advisor hook (`model-router-advisor.sh`)
already prints stderr when current model > recommended — orchestrator
needs to actually pass `model:` parameter on next spawn (behavioural,
not a code change).

=== STATUS-TRUTH MARKER ===
shipped: functional
stubs: 0
cargo-check: NOT-RUN
behaviour-verified: yes
follow-up-required:
  - PR feat/substrate-path-atoms-2026-05-01 → main when ready

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-01 23:24:02 +08:00

1.3 KiB

Raw Blame History

type	kind	name	template	expand_at
atom	path	user-hooks	~/.claude/hooks	render

Path atom — user-hooks

Resolves to the user's ~/.claude/hooks/ directory (PreToolUse / PostToolUse / UserPromptSubmit / Stop hook scripts like agent-stub-scan.sh, agent-outcome-backfill.sh, numeric-claims-guard.sh, etc.).

Used by agent manifests (_manifests/*.toml) to reference hook scripts without leaking the absolute path (with the maintainer's home /Users/<user>/...) into public artefacts under _generated/.

Usage in manifests:

[references]
extra = [
  "path:user-hooks/agent-outcome-backfill.sh",
  "path:user-hooks/agent-stub-scan.sh",
]

Resolution: the assembler detects the path:user-hooks/ prefix, looks up this atom in the registry, and emits an opaque DNA reference into the rendered _generated/<agent>.md. Same content-addressing semantics as path-user-memory and path-user-rules — published artefact has DNA hashes, not paths. A reader with a local kit + registry resolves the DNA back to the file; a reader without the kit sees only the opaque hash.

Expand timing: render — substitution happens at _assembler time, before the _generated/ markdown is written.

Constructor Pattern: one cube, one path. No code, no logic. Body bytes + frontmatter ARE the atom. Hash → DNA via standard registry pipeline.

1.3 KiB Raw Blame History

Path atom — user-hooks

1.3 KiB

Raw Blame History