fix(plugin): keep always-on rules alive across compaction (0.1.11) #76

2026-06-30T23:01:24-04:00

bvandeusen commented

2026-06-30 23:01:24 -04:00

Ships plugin 0.1.11. A generic, instance-agnostic guardrail so operator rules governing consequential actions (git branch/commit/push, other hard-to-reverse or outward-facing actions) survive a compaction:

Tier-1 static context gains a leading "operator rules govern consequential actions" bullet — directs the model to re-pull list_always_on_rules() / enter_project() before acting when rules may have been summarized away, and to let a loaded rule win over a generic harness/default habit.
Compaction re-grounding banner now explicitly re-pulls list_always_on_rules() (previously only re-ran enter_project()), since a compaction can summarize binding rules out of context and leave only generic harness defaults in their place.
plugin.json version bump 0.1.10 → 0.1.11 (required for autoUpdate marketplace to ship the change).

Root cause: always-on rules are on-demand (tool-fetched) while the competing harness git defaults are always-present in the base prompt, so a compaction drops the rules but not the defaults. Fix is generic (no specific rule hardcoded into the shipped floor).

🤖 Generated with Claude Code

Ships plugin 0.1.11. A generic, instance-agnostic guardrail so operator rules governing consequential actions (git branch/commit/push, other hard-to-reverse or outward-facing actions) survive a compaction: - **Tier-1 static context** gains a leading "operator rules govern consequential actions" bullet — directs the model to re-pull `list_always_on_rules()` / `enter_project()` before acting when rules may have been summarized away, and to let a loaded rule win over a generic harness/default habit. - **Compaction re-grounding banner** now explicitly re-pulls `list_always_on_rules()` (previously only re-ran `enter_project()`), since a compaction can summarize binding rules out of context and leave only generic harness defaults in their place. - `plugin.json` version bump 0.1.10 → 0.1.11 (required for autoUpdate marketplace to ship the change). Root cause: always-on rules are on-demand (tool-fetched) while the competing harness git defaults are always-present in the base prompt, so a compaction drops the rules but not the defaults. Fix is generic (no specific rule hardcoded into the shipped floor). 🤖 Generated with [Claude Code](https://claude.com/claude-code)

bvandeusen added 1 commit 2026-06-30 23:01:25 -04:00

fix(plugin): keep always-on rules alive across compaction (0.1.10 → 0.1.11) f6629d4bcf

Always-on rules were on-demand, not always-present: Tier-1 static context only
tells the agent to call list_always_on_rules(), and Tier-2 dynamic fetch is dark
(token doesn't reach the hook subprocess). On compaction the fetched rules get
summarized away while the harness's own built-in git instruction ("branch first")
survives in the base prompt — so post-compact the generic git instinct wins and
rule #1 ("dev is home") is missed.

- scribe_static_context.md: new "Operator rules govern consequential actions"
  bullet — before any git branch/commit/push or hard-to-reverse action, loaded
  rules beat generic harness/default habits; re-pull rules if not loaded or
  summarized by a compaction. Tier 1 = always fires, keyless, re-fires on compact.
- scribe_session_context.sh: compaction banner now re-pulls list_always_on_rules(),
  not just enter_project().
- plugin.json: 0.1.10 → 0.1.11 so autoUpdate ships the plugin/ change (#1040).

Generic and instance-agnostic per rules #115/#119 — no operator-specific rule
text hardcoded. Refs issue #1197.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E4bNefPFAz7esmMZMZmkzL

bvandeusen merged commit 05f0cc2c4b into main

2026-06-30 23:01:28 -04:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: bvandeusen/FabledScribe#76