feat(rulings): a command or edit touching an area's files shows its rulings, once per session (milestone 444 step 4, #4757)

A System's rulings (the Rulings section of its description) now reach the work by path, not by similarity. Both PreToolUse arms resolve the files a command or edit names to the Systems whose path_patterns cover them, and the first touch in a session shows each area's rulings in one line; a repeat is a one-line reference. A lookup, so no floor, no budget, no retrieval_logs row. - services/system_rulings: parse_rulings, command_paths (reads and writes, relative to the repo root from any cwd; flags, URLs, globs skipped), rulings_for_paths - /tool-rules takes root, cwd and seen_ruling_systems; /prior-art takes seen_ruling_systems; both return ruling_system_ids - hooks share <sid>.rulings.ids (cleared on compaction by the ledger naming convention); the Bash hook sends the repo root and cwd - system_usage_events (migration 0114): surfacings by source, pulls from get_system; carried by backup (v20) through the system map - writing-records: rulings also arrive when the area's files are touched Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-02 23:08:32 -04:00
parent a113c72b4f
commit 556872c039
17 changed files with 808 additions and 13 deletions
@@ -96,6 +96,8 @@ one line each — the statement, who decided, when, and the record it came from:

 The description arrives with every record filed under that System, so a ruling
 there reaches each session working in the area without having to win a search.
+Once the System names its files (`path_patterns`), its rulings also arrive with
+the first command or edit in a session that touches them.
 A quote inside a work log does not: it surfaces only when a query happens to
 match it, and the passage that matches is usually the prose around it — often a
 session's *reading* of the ruling rather than the ruling.