bvandeusenandClaude Opus 5.5
c5eeec471f
CI & Build / Python lint (push) Successful in 3s
CI & Build / Plugin hooks (push) Successful in 14s
CI & Build / TypeScript typecheck (push) Successful in 53s
CI & Build / integration (push) Successful in 1m2s
CI & Build / Python tests (push) Failing after 1m26s
CI & Build / Build & push image (push) Skipped
Step 3 of the Scribe -> Grimoire rename. - Plugin `grimoire` in marketplace `grimoire-plugin`, MCP server key `grimoire`, so tools reach a session as mcp__plugin_grimoire_grimoire__*. - hooks/scribe_* -> hooks/grimoire_*, their shell functions and the TMPDIR ledgers with them; SCRIBE_URL / SCRIBE_TOKEN / SCRIBE_HOOK_DIR / SCRIBE_LEDGER_DIRS -> GRIMOIRE_*; the project marker is `.grimoire`. - skills/using-scribe -> using-grimoire, /grimoire:sync, stored processes arrive as grimoire-proc-<slug>; moment_actions names them the same way. - Migration 0124 rewrites stored skill names (rule_moments, rule_moment_judgments, moment_mappings) from scribe:/scribe-proc- to grimoire:/grimoire-proc-, so a rule mounted on a skill keeps firing. - Settings' install commands and MCP-only defaults, the docs and the tests follow. - scripts/check_plugin.py drops the smoke event for a report-check hook that has no file in plugin/hooks. Kept on purpose: the secret-sealing label, and the names that let backups written as Scribe restore and be counted. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
47 lines
1.9 KiB
Bash
Executable File
47 lines
1.9 KiB
Bash
Executable File
#!/usr/bin/env bash
|
|
# Grimoire — say WHICH session holds a task's claim.
|
|
#
|
|
# The server stamps a claim on the write that is the work — a task reaching
|
|
# `in_progress`, a work log on an open task — so every MCP client gets a claim
|
|
# that dies on its own once its lease runs out. What the server cannot know is
|
|
# which SESSION made the write: an MCP caller is a user and nothing more.
|
|
#
|
|
# The harness knows. This PostToolUse hook watches `update_task` and
|
|
# `add_task_log` and reports the event's `session_id` against the task the
|
|
# call named, so the claim can say "this session" rather than "someone,
|
|
# recently". Same evidence class as grimoire_record_opened.sh: a tool call
|
|
# happened and the harness reported it; nothing here asks the model anything.
|
|
#
|
|
# It cannot CREATE a claim. The server binds the session only to a live claim
|
|
# the caller already holds, so a call that closed the task, or one on a task
|
|
# someone else is working, binds nothing.
|
|
#
|
|
# EXIT 0 AND SILENT, ALWAYS. This decorates a record; a PostToolUse hook that
|
|
# spoke would put a line after every task write, and a failure here must never
|
|
# turn a successful tool call into a hook error.
|
|
set -uo pipefail
|
|
|
|
# shellcheck source=plugin/hooks/grimoire_defs.sh
|
|
. "$(dirname "${BASH_SOURCE[0]}")/grimoire_defs.sh"
|
|
|
|
command -v curl >/dev/null 2>&1 || exit 0
|
|
grimoire_config || exit 0
|
|
|
|
event=$(cat 2>/dev/null || true)
|
|
[ -n "$event" ] || exit 0
|
|
|
|
event_flat=$(printf '%s' "$event" | grimoire_json_flat)
|
|
session_id=$(grimoire_json_pick "$event_flat" '.session_id')
|
|
[ -n "$session_id" ] || exit 0
|
|
|
|
task_id=$(grimoire_json_pick "$event_flat" '.tool_input.task_id')
|
|
task_id=$(printf '%s' "$task_id" | tr -cd '0-9')
|
|
[ -n "$task_id" ] || exit 0
|
|
|
|
sid_enc=$(printf '%s' "$session_id" | grimoire_urlenc) || exit 0
|
|
curl -fsS --max-time 4 \
|
|
-H "Authorization: Bearer ${token}" \
|
|
"${url%/}/api/plugin/claim-session?task_id=${task_id}&session_id=${sid_enc}" \
|
|
>/dev/null 2>&1 || true
|
|
exit 0
|