bvandeusenandClaude Opus 5.5
e99f1169f7
CI & Build / Python lint (push) Successful in 3s
CI & Build / Plugin hooks (push) Successful in 12s
CI & Build / TypeScript typecheck (push) Successful in 52s
CI & Build / integration (push) Successful in 1m1s
CI & Build / Python tests (push) Successful in 1m55s
CI & Build / Build & push image (push) Successful in 36s
Step 1 of the Scribe -> Grimoire rename: every capitalised "Scribe" in prose
becomes "Grimoire" ("Fabled Scribe" -> "Fabled Grimoire") across the UI,
the PWA manifest and page title, the MCP instructions and tool docstrings,
hook and skill text, docs and README, with the tests that assert on that
prose moving with it. Old migrations keep their wording.
Identifiers are untouched here: the package, plugin name, MCP server key,
hook file names, env vars, the .scribe marker and FabledScribe repo/image
names move in steps 2 and 3, along with prose that quotes them.
The sweep matched "Scribe" only as a whole word, so describe/subscribe and
friends are untouched. The longer name took the MCP instructions one
character over their 1,600 budget; two phrases are shortened to fit.
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
|
|
# Grimoire — 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
|