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>
52 lines
2.2 KiB
Bash
Executable File
52 lines
2.2 KiB
Bash
Executable File
#!/usr/bin/env bash
|
|
# Grimoire — release this session's task claims as it ends.
|
|
#
|
|
# A claim records a session's attention, and a session that ends has none left
|
|
# to give. This is the mechanical half of the hand-off: it needs nothing from
|
|
# the model, only the session id the harness reports. The other half — writing
|
|
# down where the work stands — only the model can do, and it is stated as a
|
|
# practice in the skill and the static context, not here.
|
|
#
|
|
# A TIDY-UP, NOT THE GUARANTEE. SessionEnd does not fire on a crash, a killed
|
|
# terminal or a dropped connection, and those are exactly the cases the claim
|
|
# was designed around. The lease is what makes a dead session's claim read as
|
|
# dead; this only keeps the ordinary exit from leaving a claim to run out.
|
|
#
|
|
# NOT ON /clear. A clear ends one conversation and starts the next in the same
|
|
# terminal, and SessionStart(source=clear) pushes back the work this session
|
|
# had claimed. Releasing here would leave that push with nothing to say. The
|
|
# next write moves the claim wherever the work actually continues.
|
|
#
|
|
# EXIT 0 AND SILENT, ALWAYS. Nobody reads a SessionEnd hook's output, and the
|
|
# session is ending whether this succeeds or not.
|
|
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 moment arm's per-session files (its tool cache and the acts ledger)
|
|
# describe a session that is over, on any exit — a clear
|
|
# included, since the next conversation is a new session id.
|
|
safe_sid=$(printf '%s' "$session_id" | tr -c 'A-Za-z0-9._-' '_')
|
|
rm -f "${TMPDIR:-/tmp}/scribe-moment/${safe_sid}".* 2>/dev/null || true
|
|
|
|
reason=$(scribe_json_pick "$event_flat" '.reason')
|
|
[ "$reason" = "clear" ] && exit 0
|
|
|
|
command -v curl >/dev/null 2>&1 || exit 0
|
|
scribe_config || exit 0
|
|
|
|
sid_enc=$(printf '%s' "$session_id" | scribe_urlenc) || exit 0
|
|
curl -fsS --max-time 4 \
|
|
-H "Authorization: Bearer ${token}" \
|
|
"${url%/}/api/plugin/release-session?session_id=${sid_enc}" \
|
|
>/dev/null 2>&1 || true
|
|
exit 0
|