bvandeusenandClaude Opus 5.5
17777e9bb1
CI & Build / Python lint (push) Successful in 3s
CI & Build / Plugin hooks (push) Successful in 15s
CI & Build / TypeScript typecheck (push) Successful in 53s
CI & Build / integration (push) Successful in 1m10s
CI & Build / Python tests (push) Successful in 1m55s
CI & Build / Build & push image (push) Successful in 39s
MCP tool docstrings and comments, the server's orientation notes, the plugin skills, every hook script and the plugin README/PACKAGING drop record ids, milestone numbers, dates and incident stories, and state each non-obvious why as a present-tense fact. History stays in the task logs. Corrections found on the way: - plugin README/PACKAGING said every hook is a GET; moment, rule-opened and reply-rules POST, so the plugin's key needs write scope. Both now say so, name Settings -> MCP Access, and list every wired hook and endpoint. - the contract-change hint printed "(lesson #4207)", this instance's record, to every install. It no longer cites a record. - tasks.py claimed there is no delete_task; there is. - rulebooks.py cited delete_event and a design spec that no longer exist. - scribe_after_write.sh carried an always-empty etag_q; removed. - test_write_path_trigger pinned "| tac | scribe_defs | head -1", text that existed only in a comment about the old code; it now pins the real tail -1 pipeline. - docs/development.md: CI runs on Gitea Actions. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
56 lines
2.4 KiB
Bash
Executable File
56 lines
2.4 KiB
Bash
Executable File
#!/usr/bin/env bash
|
|
# Scribe — record that this session said what a rule DID, not merely that it
|
|
# read one.
|
|
#
|
|
# THE THIRD LEDGER, AND WHY THE OTHER TWO ARE NOT ENOUGH.
|
|
#
|
|
# `.rules.ids` says a rule was NAMED. `.opened.ids` says it was READ (a
|
|
# PostToolUse hook watches the `get_rule` call, so it is a recorded event
|
|
# rather than a model's claim about its own context). Neither can say what
|
|
# happened next: a rule read and followed and a rule read and forgotten leave
|
|
# identical traces.
|
|
#
|
|
# `rule_outcome` is the call that closes that gap, and the server
|
|
# records it. But the server's row carries no session — `rule_usage_events` is
|
|
# per user over a window — so a SESSION-scoped readout cannot be asked of it.
|
|
# The question "which rules changed something in THIS session" has to be
|
|
# answered where a session is a thing that exists, which is here.
|
|
#
|
|
# SAME EVIDENCE CLASS AS `.opened.ids`, deliberately. A tool call happened or
|
|
# it did not, and the harness reports it either way; nothing here asks the
|
|
# model whether it followed anything, so it is evidence, not self-report.
|
|
#
|
|
# WHAT IT CANNOT SAY: that the rule was followed WELL, or that `applied` was
|
|
# honest. It records that an outcome was declared. The value of that is not the
|
|
# claim itself — it is that the absence of one becomes visible.
|
|
#
|
|
# EXIT 0, ALWAYS. This decorates a ledger; a bookkeeping failure must never
|
|
# turn a successful tool call into a hook error.
|
|
set -uo pipefail
|
|
|
|
# shellcheck source=plugin/hooks/scribe_defs.sh
|
|
. "$(dirname "${BASH_SOURCE[0]}")/scribe_defs.sh"
|
|
|
|
event=$(cat 2>/dev/null || true)
|
|
[ -n "$event" ] || exit 0
|
|
|
|
event_flat=$(printf '%s' "$event" | scribe_json_flat)
|
|
session_id=$(scribe_json_pick "$event_flat" '.session_id')
|
|
[ -n "$session_id" ] || exit 0
|
|
|
|
# The matcher in hooks.json narrows to the rule_outcome tools, but the server
|
|
# segment of an MCP tool name varies with how the plugin was installed, so the
|
|
# id is read from the field rather than from an assumed tool name — the same
|
|
# reasoning scribe_record_opened.sh gives.
|
|
rule_id=$(scribe_json_pick "$event_flat" '.tool_input.rule_id')
|
|
rule_id=$(printf '%s' "$rule_id" | tr -cd '0-9')
|
|
[ -n "$rule_id" ] || exit 0
|
|
|
|
state_dir="${TMPDIR:-/tmp}/scribe-priorart"
|
|
mkdir -p "$state_dir" 2>/dev/null || true
|
|
safe_sid=$(printf '%s' "$session_id" | tr -c 'A-Za-z0-9._-' '_')
|
|
|
|
# Stamped and append-only like its two siblings, so one reader ages them all.
|
|
printf '%s\n' "$rule_id" | scribe_rules_append "$state_dir/${safe_sid}.acted.ids"
|
|
exit 0
|