frizz 0.7.8 → 0.8.0

package/runtime/cc-worker/hooks/precompact-instructions.mjs

@@ -1,133 +0,0 @@
-#!/usr/bin/env node
-// @ts-check
-// PreCompact hook (frizz-worker) — steers WHAT SURVIVES a compaction. Run directly with node (zero
-// deps, max Node compat), mirroring cc's hook idiom.
-//
-// WHY THIS EXISTS: compaction is the single largest source of context loss in a long worker session.
-// A ~967k-token session collapses to a ~10-15k summary, and what gets dropped first is the HIGH-LEVEL
-// approach — the plan, the alternatives rejected, the reasoning — leaving a worker that remembers
-// mechanics but has lost the thread. `session-seed.mjs` already re-grounds AFTER the fact on
-// SessionStart(compact); this hook is the other half, steering the summary itself BEFORE it is written.
-//
-// THE CHANNEL — and it is unusual, so do not "fix" it to JSON: unlike every other hook in this
-// plugin, a PreCompact hook's PLAIN STDOUT becomes the compaction instructions. Claude Code collects
-// the trimmed stdout of every succeeding, non-blocking PreCompact hook, joins them with a blank line,
-// and splices the result into the summarization prompt as a literal `Additional Instructions:`
-// section (verified live: cli 2.1.220, `FTe`/`Ysd`). Emitting `hookSpecificOutput` JSON here would
-// send the summarizer a blob of JSON as its instructions. The matcher is the TRIGGER string
-// (`auto` / `manual`), which is why hooks.json registers this twice.
-//
-// LENGTH IS ONLY STEERABLE BY AN EXPLICIT NUMBER — measured, so do not soften WORD_TARGET into prose.
-// Single-variable differential, three `--fork-session` branches off one identical 345,898-token seed:
-//
-//   no hook (control)                    postTokens  4,060
-//   qualitative "prefer a long summary"  postTokens  4,429   (+9% — noise)
-//   explicit ">= 15,000 words"           postTokens 20,339   (5.0x the control)
-//   explicit ">= 35,000 words"           postTokens  5,182   (WORSE, and slower + dearer)
-//
-// The response is NON-MONOTONIC, so do not move WORD_TARGET far in either direction without
-// re-measuring. 35,000 words is past what the model will produce in one response and asking for it
-// degraded compliance badly — a quarter the output of the 15,000 ask (2,174 words vs 9,829), at
-// 11.2 min / $3.73 vs 8.6 min / $2.04. Three single samples; treat the exact figures as indicative.
-//
-// WHY IT IS NO LONGER 15,000 (2026-08-06, maintainer: "let's tone this down a bit"). That row is the
-// one that reads as a win in isolation and is the expensive one in production: a 20,339-token summary
-// is where the next context STARTS, so every compaction handed the thread ~16k tokens of overhead over
-// the control before it did any work. On a long-lived thread that compounds — each cycle begins nearer
-// the ceiling, so the next compaction arrives sooner, and the window between them shrinks. Observed on
-// the maintainer's own 10-day `are-taking-over-an-in-flight-epic` thread: 31 compactions, then a
-// cold resume whose replay overflowed the window outright ("Prompt is too long"), leaving a thread that
-// could not complete the one turn that would have compacted it. The latency was the visible cost; the
-// post-compaction FOOTPRINT was the one that actually mattered.
-//
-// 5,000 is UNMEASURED — an explicit number (adjectives measurably do nothing) at a third of the ask,
-// chosen to keep the mechanism that works while cutting what it leaves behind. There is no data point
-// between the qualitative row and 15,000; if this matters, re-run the differential above and add rows.
-//
-// The remaining COST is latency. That is acceptable because frizz workers run with
-// `precomputeCompactionEnabled`, which arms summary generation in a background sidecar at ~80% of the
-// window and swaps it in at the real threshold — so on an `auto` trigger the wait is largely hidden. A
-// `manual` /compact pays it in front of the human.
-//
-// HARD CEILING: the summary is ONE model response, so it is bounded by max output tokens (64k for
-// Opus 5 / Sonnet 5, ~48k words). A 200k-token summary is unreachable at any prompt.
-//
-// TONE MATTERS: an instruction that reads like injected prompt-hijacking gets REFUSED by the
-// summarizer — measured: an early probe demanding a sentinel token produced a summary that explicitly
-// declined to comply and called the instructions fake. Keep this legible as an ordinary editorial
-// brief about what to retain.
-//
-// GATE: everything is gated on FRIZZ_THREAD, so the plugin stays inert when loaded outside a
-// frizz worker. Sub-agent contexts are skipped, matching session-seed.mjs — the scratch-directory path
-// below is only guaranteed correct for the top-level worker session.
-import { readFileSync } from 'node:fs';
-import { currentSessionId } from '../scripts/frizz/config.mjs';
-
-// See "LENGTH IS ONLY STEERABLE BY AN EXPLICIT NUMBER" and "WHY IT IS NO LONGER 15,000" above before
-// changing this. The number is load-bearing; the prose around it is not.
-const WORD_TARGET = 5000;
-
-/** @type {{ agent_id?: unknown, agentId?: unknown, trigger?: string, session_id?: string }} */
-let input = {};
-try {
-  input = JSON.parse(readFileSync(0, 'utf8'));
-} catch {
-  /* no stdin / not JSON → input stays {} → proceed with the generic brief */
-}
-// Skip inside sub-agent contexts (they carry agent_id) — see GATE above.
-if (input.agent_id ?? input.agentId) process.exit(0);
-
-// WORKER GATE — inert unless this is a frizz worker session.
-const thread = (process.env.FRIZZ_THREAD ?? '').trim();
-if (!thread) process.exit(0);
-
-let sid = null;
-try {
-  sid = currentSessionId(input.session_id);
-} catch {
-  /* best-effort — fall back to the generic path shape below */
-}
-const scratch = sid
-  ? '.frizz/threads/' + sid + '/'
-  : '.frizz/threads/<session-id>/';
-
-// Written as an editorial brief, not as a command block — see TONE MATTERS above.
-const brief = [
-  'This is a frizz worker session driving one engineering effort (`' + thread + '`). Three things to ' +
-    'get right, because they are what actually gets lost in compaction:',
-  '',
-  '1. LENGTH. Target about ' + WORD_TARGET.toLocaleString('en-US') + ' words — long enough that ' +
-    'nothing load-bearing has to be dropped, but this is a working handover and not an archive. ' +
-    'Spend the length on what the next turn cannot recover for itself.',
-  '',
-  '2. THE HIGH-LEVEL APPROACH, AT HIGH FIDELITY. Preserve the shape of the work, not just its ' +
-    'mechanics: what problem is being solved, the approach chosen, the approaches considered and ' +
-    'REJECTED and why, and the reasoning that led there. This is the part worth its space — a summary ' +
-    'that lists edits but loses the plan leaves the next turn unable to judge whether a step is still ' +
-    'the right one. Quote code and output where the exact text matters; summarize where it does not.',
-  '',
-  'Carry forward:',
-  '- The task list and its state — every item, marked done / in progress / not started / blocked.',
-  '- Decisions made and the rationale for each, especially any the human made, approved, or reversed.',
-  '- Constraints, conventions, and explicit human instructions or corrections — in the human\'s own ' +
-    'wording where you can, since paraphrase is where intent gets lost.',
-  '- Paths of every file created, read, or modified, and what changed in each.',
-  '- Commands that matter (build / test / run / verification) and their OBSERVED results.',
-  '- What has been VERIFIED by actually running it versus what is merely believed to work. Keep that ' +
-    'distinction explicit — it is routinely lost in compaction and its loss causes false claims of ' +
-    'completion.',
-  '- Open questions, known failures, dead ends already ruled out, and anything left unfinished.',
-  '',
-  '3. RE-GROUNDING. End the summary with a final section headed exactly "Re-grounding before ' +
-    'continuing:" that tells the next turn what to re-establish BEFORE it asserts anything or resumes ' +
-    'editing. Make it concrete and specific to this session — not generic advice:',
-  '- Read whatever the worker left in `' + scratch + '` first. That is its durable working state and it ' +
-    'outlives this summary.',
-  '- Name the specific files to re-read before describing or changing them, rather than relying on ' +
-    'remembered contents.',
-  '- Name any verification that was in flight and should be re-run rather than assumed.',
-  '- State the single next action to take.',
-].join('\n');
-
-process.stdout.write(brief + '\n');
-process.exit(0);

package/runtime/cc-worker/skills/waits/SKILL.md

@@ -1,84 +0,0 @@
----
-name: waits
-description: How a frizz worker waits on something without going silent or falling out of the board's Active state (invoke as frizz:waits) — choosing between a wait-owning sub-agent, background Bash, native Monitor, and a durable timer fence; frizz's portable monitor scripts; and the CI/PR/release recipes. Load this when your effort needs to wait on CI, a release, a deploy, a merge, or another long-running condition.
----
-
-# Waiting, without going silent
-
-Your system prompt carries the one rule that decides the mechanism. This is the playbook.
-
-## The rule
-
-**Only a live dispatched sub-agent keeps a rested thread out of the human's queue.** A background
-`Bash`/`Monitor` does not: `run_in_background` means "don't block my turn", and frizz cannot tell a CI
-watcher that ends in minutes from a `vite` dev server that runs forever, so neither holds a rested
-thread in Active.
-
-| You will… | Use |
-|---|---|
-| REST until the condition is met (the usual CI / PR / release wait) | a **sub-agent** that owns the wait |
-| KEEP WORKING alongside a process you launched (dev server, log tail) | `Bash` + `run_in_background: true` |
-| stream events into the turn you are actively working in | `Monitor` |
-| re-check at a named wall-clock instant, across a process exit | `mcp__frizz__timer`, named in a `timers:` fence list |
-
-Never fake a wait with `echo waiting`, repeated foreground sleeps, or an `awaiting` fence for CI, bots,
-releases, or merge progression.
-
-Never fake Claude's native background mechanism with shell job control (`cmd &`, `nohup … &`, or
-`disown`). The child may survive after Bash returns, but it has no Claude task id, output-file
-lifecycle, completion notification, or wake. Use `run_in_background: true` with the long command
-itself in the foreground. Shell-level concurrency is only self-contained: explicitly `wait` for its
-children or own cleanup with an EXIT trap before that Bash call returns.
-
-## Choosing a monitor implementation
-
-1. **Look for project-declared tooling first** — `AGENTS.md`, project skills, docs, package scripts.
-   Prefer it only after validating its absolute command and its terminal event/exit semantics. Invalid
-   declared tooling is a visible configuration error to report, not something to silently shadow. Never
-   select a monitor merely by filename.
-2. **Otherwise use frizz's portable Node scripts** in `monitors/` (zero-dep, NDJSON on stdout, they exit
-   at a terminal verdict).
-3. **Native `Monitor`** is the Claude adapter for a changing condition — a quiet
-   `until ...; do sleep ...; done`, emitting one event per meaningful transition. `persistent: true`
-   runs until `TaskStop` or session end.
-
-## The sub-agent-owns-the-wait pattern
-
-This is the prescribed way to wait while you rest. Dispatch with the plain Agent tool +
-`run_in_background: true`, no `name` field. The child runs the watcher in **its own foreground** and
-returns the verdict; you stay Active, and its return re-invokes you so you can act on the result.
-
-Foreground Bash is timeout-capped at ~10 minutes, so for a longer wait the child must loop until its
-terminal condition rather than issuing one long call. A helper must not hand back its final report
-while its own watcher is still live — the wait IS its work.
-
-Give the child, literally, in the prompt:
-
-- the exact command to run and the terminal condition to stop on;
-- the repo path and the thread's scratch-directory path;
-- what to return: the verdict plus enough detail to act on a failure (job name, failing step, log tail);
-- an instruction not to fix anything — it observes and reports; you decide.
-
-## Recipes
-
-**GitHub CI on a PR head.** `gh run watch <run-id> --exit-status` blocks to completion, or loop
-`gh pr checks <n> --json name,state,link`. A partial `gh pr checks` rollup is **not** a green verdict:
-also inspect the workflow runs for the exact PR head, and treat `ACTION_REQUIRED` fork gates as pending,
-not passing.
-
-**PR review activity.** Do not build a watcher — register the PR with `mcp__frizz__watch_pr`, then name
-it in your `awaiting` fence's `prs:` list. Frizz polls it for you, waking on any new review, approval,
-or comment, bot or human. The registration creates the wait; the fence only declares it.
-
-**A release or deploy.** Poll the artifact that proves it, not the pipeline that promises it — the
-published version on the registry, the health endpoint, the deployed asset hash.
-
-**Another long-running local process.** Read its output path with `Read` for diagnostics (`TaskOutput`
-is deprecated). `TaskStop` is only for your own monitor after its terminal handoff — never to cut off a
-sub-agent or a writer.
-
-## Liveness caveats
-
-Live tasks do not survive the Claude process or session ending. A durable `timer:` fence is the only
-wait that survives a restart, so use it when the next meaningful check genuinely belongs at a later
-instant rather than continuously monitored now.

package/web-dist/assets/architecture-TIHT7OUA-DksosNDW.js

@@ -1 +0,0 @@
-import"./chunk-KEIR6QF5-BfrZ3jm6.js";import{M as e}from"./mermaid-parser.core-BPsFhEi6.js";export{e as createArchitectureServices};

package/web-dist/assets/channel-DqoPvfQz.js

@@ -1 +0,0 @@
-import{at as e,ot as t}from"./chunk-WYO6CB5R-DzVb3-Rj.js";var n=(n,r)=>t.lang.round(e.parse(n)[r]);export{n as t};

package/web-dist/assets/classDiagram-OUVF2IWQ-DwUs74RB.js

@@ -1 +0,0 @@
-import{n as e}from"./chunk-Y2CYZVJY-DsF7k-Jl.js";import"./src-C4XfhTaE.js";import"./chunk-WYO6CB5R-DzVb3-Rj.js";import"./chunk-ICXQ74PX-DWAAqHL7.js";import"./chunk-HOUHSVGY-BCWyMhwJ.js";import"./chunk-Q4XR5HBZ-Bafzu7s-.js";import"./chunk-7BUUIJ7U-Bb538aSH.js";import"./chunk-OGEWGWER-DUxmbiuX.js";import"./chunk-32BRIVSS-CVv1ae7n.js";import"./chunk-XXDRQBXY-DYlTP5J-.js";import"./chunk-VR4S4FIN-DU-1KtuM.js";import"./chunk-C7G6YPKG-Cn4HhNwb.js";import"./chunk-ZGVPDNZ5-BPKQvduj.js";import"./chunk-52WLFC77-BYhPlKCT.js";import"./chunk-FWX5IMBZ-Ba3NpEQa.js";import{i as t,n,r,t as i}from"./chunk-V7JOEXUC-Bj0A8ftW.js";var a={parser:n,get db(){return new i},renderer:r,styles:t,init:e(e=>{e.class||={},e.class.arrowMarkerAbsolute=e.arrowMarkerAbsolute},`init`)};export{a as diagram};

package/web-dist/assets/classDiagram-v2-EOCWNBFH-DwUs74RB.js

@@ -1 +0,0 @@
-import{n as e}from"./chunk-Y2CYZVJY-DsF7k-Jl.js";import"./src-C4XfhTaE.js";import"./chunk-WYO6CB5R-DzVb3-Rj.js";import"./chunk-ICXQ74PX-DWAAqHL7.js";import"./chunk-HOUHSVGY-BCWyMhwJ.js";import"./chunk-Q4XR5HBZ-Bafzu7s-.js";import"./chunk-7BUUIJ7U-Bb538aSH.js";import"./chunk-OGEWGWER-DUxmbiuX.js";import"./chunk-32BRIVSS-CVv1ae7n.js";import"./chunk-XXDRQBXY-DYlTP5J-.js";import"./chunk-VR4S4FIN-DU-1KtuM.js";import"./chunk-C7G6YPKG-Cn4HhNwb.js";import"./chunk-ZGVPDNZ5-BPKQvduj.js";import"./chunk-52WLFC77-BYhPlKCT.js";import"./chunk-FWX5IMBZ-Ba3NpEQa.js";import{i as t,n,r,t as i}from"./chunk-V7JOEXUC-Bj0A8ftW.js";var a={parser:n,get db(){return new i},renderer:r,styles:t,init:e(e=>{e.class||={},e.class.arrowMarkerAbsolute=e.arrowMarkerAbsolute},`init`)};export{a as diagram};

package/web-dist/assets/eventmodeling-45OFAUF4-CUIjQ7kE.js

@@ -1 +0,0 @@
-import"./chunk-KEIR6QF5-BfrZ3jm6.js";import{O as e}from"./mermaid-parser.core-BPsFhEi6.js";export{e as createEventModelingServices};

package/web-dist/assets/flowDiagram-23GEKE2U-Dka-3F3n.js

@@ -1 +0,0 @@
-import"./src-C4XfhTaE.js";import"./chunk-WYO6CB5R-DzVb3-Rj.js";import"./chunk-ICXQ74PX-DWAAqHL7.js";import"./chunk-HOUHSVGY-BCWyMhwJ.js";import"./chunk-Q4XR5HBZ-Bafzu7s-.js";import"./chunk-7BUUIJ7U-Bb538aSH.js";import"./chunk-OGEWGWER-DUxmbiuX.js";import"./chunk-32BRIVSS-CVv1ae7n.js";import"./chunk-XXDRQBXY-DYlTP5J-.js";import"./chunk-VR4S4FIN-DU-1KtuM.js";import"./chunk-C7G6YPKG-Cn4HhNwb.js";import"./chunk-ZGVPDNZ5-BPKQvduj.js";import"./chunk-52WLFC77-BYhPlKCT.js";import"./chunk-FWX5IMBZ-Ba3NpEQa.js";import"./chunk-ZIRB5QZD-C6fEPe3t.js";import{n as e}from"./chunk-PUDLZKDR-DRdZWzxX.js";export{e as diagram};

package/web-dist/assets/railroad-abnf-AHOZXSZD-CCnWa6K9.js

@@ -1 +0,0 @@
-import"./chunk-KEIR6QF5-BfrZ3jm6.js";import{m as e}from"./mermaid-parser.core-BPsFhEi6.js";export{e as createRailroadAbnfServices};

package/web-dist/assets/railroad-ebnf-EBAXGLYW-jtVdzv7e.js

@@ -1 +0,0 @@
-import"./chunk-KEIR6QF5-BfrZ3jm6.js";import{f as e}from"./mermaid-parser.core-BPsFhEi6.js";export{e as createRailroadEbnfServices};

package/web-dist/assets/railroad-peg-LSFZ7HO6-B8D6TyEe.js

@@ -1 +0,0 @@
-import"./chunk-KEIR6QF5-BfrZ3jm6.js";import{u as e}from"./mermaid-parser.core-BPsFhEi6.js";export{e as createRailroadPegServices};

package/web-dist/assets/stateDiagram-v2-6OUMAXLB-DWKW-4qu.js

@@ -1 +0,0 @@
-import{n as e}from"./chunk-Y2CYZVJY-DsF7k-Jl.js";import"./src-C4XfhTaE.js";import"./chunk-WYO6CB5R-DzVb3-Rj.js";import"./chunk-ICXQ74PX-DWAAqHL7.js";import"./chunk-HOUHSVGY-BCWyMhwJ.js";import"./chunk-Q4XR5HBZ-Bafzu7s-.js";import"./chunk-7BUUIJ7U-Bb538aSH.js";import"./chunk-OGEWGWER-DUxmbiuX.js";import"./chunk-32BRIVSS-CVv1ae7n.js";import"./chunk-XXDRQBXY-DYlTP5J-.js";import"./chunk-VR4S4FIN-DU-1KtuM.js";import"./chunk-C7G6YPKG-Cn4HhNwb.js";import"./chunk-ZGVPDNZ5-BPKQvduj.js";import"./chunk-52WLFC77-BYhPlKCT.js";import"./chunk-FWX5IMBZ-Ba3NpEQa.js";import{i as t,n,r,t as i}from"./chunk-EX3LRPZG-P3ZYFC1W.js";var a={parser:n,get db(){return new i(2)},renderer:r,styles:t,init:e(e=>{e.state||={},e.state.arrowMarkerAbsolute=e.arrowMarkerAbsolute},`init`)};export{a as diagram};

package/web-dist/assets/swimlanesDiagram-G3AALYLV-DZKoB7ae.js

@@ -1,8 +0,0 @@
-import{n as e}from"./chunk-Y2CYZVJY-DsF7k-Jl.js";import"./src-C4XfhTaE.js";import"./chunk-WYO6CB5R-DzVb3-Rj.js";import"./chunk-ICXQ74PX-DWAAqHL7.js";import"./chunk-HOUHSVGY-BCWyMhwJ.js";import"./chunk-Q4XR5HBZ-Bafzu7s-.js";import"./chunk-7BUUIJ7U-Bb538aSH.js";import"./chunk-OGEWGWER-DUxmbiuX.js";import"./chunk-32BRIVSS-CVv1ae7n.js";import"./chunk-XXDRQBXY-DYlTP5J-.js";import"./chunk-VR4S4FIN-DU-1KtuM.js";import"./chunk-C7G6YPKG-Cn4HhNwb.js";import"./chunk-ZGVPDNZ5-BPKQvduj.js";import"./chunk-52WLFC77-BYhPlKCT.js";import"./chunk-FWX5IMBZ-Ba3NpEQa.js";import"./chunk-ZIRB5QZD-C6fEPe3t.js";import{r as t,t as n}from"./chunk-PUDLZKDR-DRdZWzxX.js";var r=n({defaultLayout:`swimlane`,styles:e(e=>`${t(e)}
-  .swimlane.cluster rect {
-    stroke: ${e.clusterBorder} !important;
-  }
-  [data-look="neo"].cluster rect {
-    filter: none;
-  }
-`,`getStyles`)});export{r as diagram};