frizz 0.8.0 → 0.9.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "frizz",
-  "version": "0.8.0",
+  "version": "0.9.0",
   "private": false,
   "description": "A local web UI for running many coding agents at once",
   "keywords": [

package/runtime/board/config.mjs

@@ -254,6 +254,16 @@ export function frizzActive(projectDir, sessionId) {
  * written to disk going forward; legacy spellings (`todo`/`plan`/`enqueued`/`needs-decision`)
  * are accepted on read via {@link STATUS_ALIASES} + {@link normalizeStatus}, never written.
  *
+ * SCOPE — THIS GOVERNS `.frizz/<slug>.md` THREAD FILES, WHICH IS FRIZZ CLASSIC. A thread the Frizz
+ * APP dispatches writes no such file, so none of the machinery narrated below (the nag, the pulse,
+ * the Stop-hook pop, the `⚖ awaiting you` queue) runs for it: the server synthesizes its `status` as
+ * "active" and never reads it back, and its place in the board's queue comes from `deriveNeedsYou`
+ * in packages/server/src/board.ts — runtime telemetry and the worker's own fences, not a status
+ * below. So this enum does NOT answer "what puts a thread in the queue"; it answers that only for a
+ * file-backed row. It stays live because the server still shells out to index.mjs (dispatch) and
+ * thread-update.mjs (mark-as-done) for exactly those rows. Noted 2026-08-26 after an outside review
+ * read this vocabulary as the app's live queue model and reported it as such.
+ *
  * THE WAITING MODEL (2026-07-08, refining the 2026-07-01 unified model): "awaiting a human" is
  * now its OWN first-class status — `needs-human` — no longer an encoding of `blocked`. `blocked`
  * narrows to MACHINE-waits ONLY and REQUIRES a resolution-mechanism field. So the human(yellow)/
@@ -898,7 +908,8 @@ export function revalidateState(revalidateAtRaw, lastCheckedRaw, now = Date.now(
 
 /**
  * Humanize a minutes-until-due into a compact ETA (`45m`, `7h`, `2d`) for the board's
- * "next check in" line. Clamps negatives (an already-due timer) to `0m`.
+ * "next check in" line, in the app's house duration grammar
+ * (`packages/web/src/lib/durationLabels.ts`). Clamps negatives (an already-due timer) to `0m`.
  * @param {number} etaMin
  * @returns {string}
  */

package/runtime/board/index.mjs

@@ -9,6 +9,11 @@
  * `frizz-reminder` hook runs `--validate` every turn so malformed frontmatter surfaces
  * to the orchestrator immediately.
  *
+ * SCOPE: FRIZZ CLASSIC. Every thread here is a `.frizz/<slug>.md` file. A thread the Frizz APP
+ * dispatches writes no such file and therefore never appears in this board at all — its row, its
+ * status and its queue membership are all derived server-side (packages/server/src/board.ts). See
+ * config.mjs § STATUS for what still consumes this tool and why it is not the app's queue model.
+ *
  * Usage (the `frizz` command is the bin/ shim that runs this script against the
  * project's `.frizz/`, regardless of cwd or where the plugin is installed):
  *   frizz               # print the LIVE board (⚖ awaiting-you + active/planning/blocked; planned hidden)

package/runtime/board/thread-update.mjs

@@ -5,6 +5,10 @@
 // (--patch, repeatable) + --append. Writes the project's .frizz/<slug>.md atomically,
 // preserving every byte outside the keys/regions it touches.
 //
+// SCOPE: frizz classic — it edits an EXISTING thread file and never creates one, so the server's
+// mark-as-done call is a no-op for a thread the Frizz app dispatched (those write no file). See
+// config.mjs § STATUS.
+//
 // Exposed as the `frizz-update` command (bin/frizz-update is on the Bash PATH while the
 // plugin is enabled). The project root is resolved from CLAUDE_PROJECT_DIR (exported to
 // bin/hook processes), matching how bin/frizz + index.mjs find the project's .frizz/.

package/runtime/cc-worker/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "frizz",
   "description": "Worker-side frizz plugin for frizz-spawned sessions. Each session is a WORKER driving ONE effort (slug via env FRIZZ_THREAD): it SIGNALS through its final message (done, human/timer awaiting, question), keeps automatable waits active with Claude wait tools, and keeps its own free-form scratch directory (.frizz/threads/<session-id>/). Supplies the effort-only frizz:<effort> sub-agent profiles (frizz:low … frizz:max; the model rides the Agent tool's own parameter), the on-demand frizz:gh skill, and hooks that seed the worker contract, enforce background/name-stripped sub-agent dispatch, and deny the interactive question/plan prompts (deny-ask, deny-plan) that would hang a dashboard worker. Hooks are inert unless FRIZZ_THREAD is set.",
-  "version": "0.1.10",
+  "version": "0.1.11",
   "author": { "name": "Colin McDonnell" },
   "homepage": "https://github.com/colinhacks/frizz",
   "repository": "https://github.com/colinhacks/frizz",

package/runtime/cc-worker/DECISIONS.md

@@ -1140,3 +1140,10 @@ Third pass of the same audit that removed the browser mount and the model×effor
 - **The portable monitors STAYED.** `skills/gh/scripts/{ci-watch,github-watch,review-watch}.mjs` are generated byte-for-byte from `monitors/` and are load-bearing for two other readers: the codex worker prompt names their absolute directory (`monitorScriptsDir()`, `dispatch.ts`, pinned by `dispatch.test.ts`), and `skills/gh` documents them as its declared-tooling fallback. Only the skill went.
 - **`hooks/precompact-instructions.mjs` is DELETED**, with both its `PreCompact` registrations. Maintainer: *"the pre-compaction instructions are probably too opinionated, entirely too opinionated."* It handed the summarizer an editorial brief about WHAT to preserve — plan, alternatives rejected, rationale, at high fidelity — which is a prescription about how someone else's work should be remembered. `scratchpad.mjs --mode=precompact` keeps both matchers: it only says the worker's scratch files exist and names their paths, which is mechanics.
 - **The `toon` bullet is gone from the seed's `⟦gh available⟧` block and from `skills/gh`.** Maintainer: *"It seems pretty opinionated to tell it to pipe through toon, given that toon is probably not installed on most machines. That might be over the line."* The original reasoning (`plans/github-integration.md` §9: worker-side yes, server-side no) was measured against THIS machine's toolchain; a `command -v toon` guard makes the advice safe but not less opinionated, and it spent prompt tokens on every authed session to describe a binary almost no repo has. The one raw-API recipe that piped through it now uses `--jq`, which ships with `gh`.
+
+## 2026-08-28: the worker's tool is `goal`, and the scratch directory is offered rather than pushed
+
+Two corrections from one maintainer thread, both about Frizz telling the worker what to do instead of what it can do.
+
+- **`recurring_prompt` is renamed `goal`.** The board panel, the footer mark and the delivered trailer have all said "Goal" since 2026-08-11; only the MCP tool still carried the mechanism's name. Maintainer: *"I don't think the tool is even called Recurring Prompt anymore, is it?"* — then *"Rename it."* Only the TOOL name and the worker-facing wording changed: the RPC procedures (`setOwnThreadRecurringPrompt`, `getOwnThreadRecurringPrompt`) and the `session.recurring_*` columns keep their names, because renaming the procedure is exactly what stranded every in-flight worker the last time (see the legacy aliases in `@frizz/shared`). No alias tool is listed for the old name — Claude Code rejects a tool name it has not listed, so an alias would have to be a visible second tool forever — and the new tool's description names its former name once, for a resumed worker whose summary still says `recurring_prompt`.
+- **Every surface that mentions the scratch directory stopped prescribing the notes-plus-arming arrangement.** The 2026-08-06 entry above set the rule "every surface that mentions the directory also mentions `post_compaction: true`", and it produced the effect the maintainer noticed: workers armed the post-compaction goal constantly, 49 of the 65 armed prompts in the live db copying the contract's template sentence verbatim. Maintainer: *"this is a very opinionated thing, and I don't think we should be pushing it as the thing to do. We should just be saying that the scratch directory is available to it if it wants it. We can also be saying that it can set these goal hooks."* The contract's scratch sections, the dispatch preamble, `scratchpadOrientation`, the five `scratchpad.mjs` hook texts and the tool's own `post_compaction` wording now say the directory and the goal hooks EXIST and leave the choice to the worker. The literal `post_compaction: true` stays on each surface so the capability is still discoverable; the nudge hook keeps its ~60k-token cadence with the informational wording.

package/runtime/cc-worker/agents/high.md

@@ -1,6 +1,6 @@
 ---
 name: high
-description: Frizz sub-agent at high effort. Set the model with the Agent tool's `model` parameter; omitted, the child inherits the worker's model.
+description: Effort high. The model is the Agent tool's `model` parameter (omitted, it inherits the worker's).
 effort: high
 ---
 

package/runtime/cc-worker/agents/low.md

@@ -1,6 +1,6 @@
 ---
 name: low
-description: Frizz sub-agent at low effort. Set the model with the Agent tool's `model` parameter; omitted, the child inherits the worker's model.
+description: Effort low. The model is the Agent tool's `model` parameter (omitted, it inherits the worker's).
 effort: low
 ---
 

package/runtime/cc-worker/agents/max.md

@@ -1,6 +1,6 @@
 ---
 name: max
-description: Frizz sub-agent at max effort. Set the model with the Agent tool's `model` parameter; omitted, the child inherits the worker's model.
+description: Effort max. The model is the Agent tool's `model` parameter (omitted, it inherits the worker's).
 effort: max
 ---
 

package/runtime/cc-worker/agents/medium.md

@@ -1,6 +1,6 @@
 ---
 name: medium
-description: Frizz sub-agent at medium effort. Set the model with the Agent tool's `model` parameter; omitted, the child inherits the worker's model.
+description: Effort medium. The model is the Agent tool's `model` parameter (omitted, it inherits the worker's).
 effort: medium
 ---
 

package/runtime/cc-worker/agents/xhigh.md

@@ -1,6 +1,6 @@
 ---
 name: xhigh
-description: Frizz sub-agent at xhigh effort. Set the model with the Agent tool's `model` parameter; omitted, the child inherits the worker's model.
+description: Effort xhigh. The model is the Agent tool's `model` parameter (omitted, it inherits the worker's).
 effort: xhigh
 ---