@bongos/core 1.19.1068 → 1.19.1070

package/docs/copy-registry.json

@@ -192,7 +192,7 @@
         "modules/hall-ui/public/hall-render.js:367",
         "modules/hall-ui/public/hall-render.js:391",
         "modules/hall-ui/public/hall-render.js:461",
-        "modules/hall-ui/public/shell.js:455"
+        "modules/hall-ui/public/shell.js:446"
       ]
     },
     {
@@ -1510,8 +1510,8 @@
       "text": "Sign out",
       "occurrences": 2,
       "at": [
-        "modules/hall-ui/public/shell.js:473",
-        "modules/hall-ui/public/shell.js:785"
+        "modules/hall-ui/public/shell.js:464",
+        "modules/hall-ui/public/shell.js:776"
       ]
     },
     {
@@ -3265,20 +3265,20 @@
       "confidence": "certain"
     },
     {
-      "id": "b3c1c5615971",
+      "id": "ef2fab4901d6",
       "surface": "builders-hall",
-      "text": "Back to ideas",
-      "file": "modules/hall-ui/public/idea.html",
-      "line": 31,
+      "text": "Back to tasks",
+      "file": "modules/hall-ui/public/task.html",
+      "line": 34,
       "origin": "html-text",
       "confidence": "certain"
     },
     {
-      "id": "ef2fab4901d6",
+      "id": "64e2fbc2c072",
       "surface": "builders-hall",
-      "text": "Back to tasks",
-      "file": "modules/hall-ui/public/task.html",
-      "line": 34,
+      "text": "Back to your thinking",
+      "file": "modules/hall-ui/public/idea.html",
+      "line": 31,
       "origin": "html-text",
       "confidence": "certain"
     },
@@ -6824,7 +6824,7 @@
       "surface": "builders-hall",
       "text": "Its details are below.",
       "file": "modules/hall-ui/public/shell.js",
-      "line": 743,
+      "line": 734,
       "origin": "js-markup",
       "confidence": "certain"
     },
@@ -6905,7 +6905,7 @@
       "surface": "builders-hall",
       "text": "Jump to a page or record",
       "file": "modules/hall-ui/public/shell.js",
-      "line": 494,
+      "line": 485,
       "origin": "js-markup",
       "confidence": "certain"
     },
@@ -6914,7 +6914,7 @@
       "surface": "builders-hall",
       "text": "Jump to…",
       "file": "modules/hall-ui/public/shell.js",
-      "line": 496,
+      "line": 487,
       "origin": "js-markup",
       "confidence": "certain"
     },
@@ -8588,7 +8588,7 @@
       "surface": "builders-hall",
       "text": "Open navigation",
       "file": "modules/hall-ui/public/shell.js",
-      "line": 485,
+      "line": 476,
       "origin": "js-markup",
       "confidence": "certain"
     },
@@ -10460,7 +10460,7 @@
       "surface": "builders-hall",
       "text": "Sign in with GitHub",
       "file": "modules/hall-ui/public/shell.js",
-      "line": 455,
+      "line": 446,
       "origin": "js-markup",
       "confidence": "certain"
     },
@@ -10469,7 +10469,7 @@
       "surface": "builders-hall",
       "text": "Sign out",
       "file": "modules/hall-ui/public/shell.js",
-      "line": 473,
+      "line": 464,
       "origin": "js-markup",
       "confidence": "certain"
     },
@@ -10478,7 +10478,7 @@
       "surface": "builders-hall",
       "text": "Sign out",
       "file": "modules/hall-ui/public/shell.js",
-      "line": 785,
+      "line": 776,
       "origin": "js-markup",
       "confidence": "certain"
     },
@@ -10505,7 +10505,7 @@
       "surface": "builders-hall",
       "text": "Skip to content",
       "file": "modules/hall-ui/public/shell.js",
-      "line": 776,
+      "line": 767,
       "origin": "js-text-assign",
       "confidence": "certain"
     },
@@ -10757,7 +10757,7 @@
       "surface": "builders-hall",
       "text": "Switch theme",
       "file": "modules/hall-ui/public/shell.js",
-      "line": 500,
+      "line": 491,
       "origin": "js-markup",
       "confidence": "certain"
     },
@@ -10955,7 +10955,7 @@
       "surface": "builders-hall",
       "text": "Text size",
       "file": "modules/hall-ui/public/shell.js",
-      "line": 499,
+      "line": 490,
       "origin": "js-markup",
       "confidence": "certain"
     },
@@ -12359,7 +12359,7 @@
       "surface": "builders-hall",
       "text": "Use the control below to take it.",
       "file": "modules/hall-ui/public/shell.js",
-      "line": 740,
+      "line": 731,
       "origin": "js-markup",
       "confidence": "certain"
     },

package/docs/module-api-changelog.md

@@ -2623,5 +2623,9 @@ is load-bearing: the script throws rather than guess if it is missing, and
         landed since 1.19.1066 with no explicit bump. run 36458843914. (task 1002620)
   1.19.1068 — CI auto-patch (publish-on-merge, ADR 0161): carrier for merges
         landed since 1.19.1067 with no explicit bump. run 36467481353. (task 1002620)
+  1.19.1069 — CI auto-patch (publish-on-merge, ADR 0161): carrier for merges
+        landed since 1.19.1068 with no explicit bump. run 36470192310. (task 1002620)
+  1.19.1070 — CI auto-patch (publish-on-merge, ADR 0161): carrier for merges
+        landed since 1.19.1069 with no explicit bump. run 36472133987. (task 1002620)
 ---------------------------------------------------------------------------
 ```

package/docs/packs/artist.md

@@ -6,71 +6,95 @@ An art session is not the engineer's text-heavy build loop. The artist's subject
 
 ---
 
+## Where the artist works: the studio
+
+The artist's whole loop is one page in the hall, **`/builders/studio`**: Tweak Mode ([ADR 0341](../adr/0341-the-page-is-the-unit-of-tweak-mode.md)). The unit is a **page** (an id such as `landing:index` or `builders:studio`, from [`docs/page-inventory.json`](../page-inventory.json)): the artist takes one whole page, rewrites its words as one document, submits it, and approves the applied result before it ships. No terminal, no claim command, no diff. Your first move is to open the studio in their browser and let them look.
+
+**The studio.** A calm night room. Top right, the **tally**: credits, pages tweaked, this week. Under the greeting, Resume and three quick actions, each opening a glass panel in place:
+
+- **Resume** — shown only while they hold a page; back into the editor on it, with "N of M lines" rewritten so far.
+- **Tweak/CopyWrite Flow** — the page to do next, with its reason ("2 people asked for it", "4 lines changed since your last pass", "untweaked"). **take it** claims that page and opens the editor; **pick another** shows four more as chips. The order is: asked for, then changed since the last tweak, then untweaked.
+- **Approval queue** — the pages a session has applied, waiting for them (below).
+- **Artist Review Status** — three lines, landing, builders hall and status, each "N of M tweaked".
+
+The studio's own words (the greeting and its sub-line) are the studio page itself: clicking them offers to take `builders:studio`, and then they type over them where they stand.
+
+**The editor: `/builders/tweak-editor?page=<id>`.** Every line of the page, in page order, on one sheet of paper, typed over in place and **autosaved**. A changed line keeps a faint "was:". A line marked "changes this on every page" is shared shell text; one marked "goes to an engineer" cannot be placed in the code, so submitting files it as an engineer task and the page does not wait for it. The top bar holds:
+
+- **open the page ↗** — the live page in a new tab, to read it in place;
+- **download .docx / upload .docx** — work offline in Word, then upload; it merges into the draft, never straight to the site. Keep the paragraphs as they are: added, dropped or reordered lines are refused by name, and a page that changed since the download asks for a fresh one;
+- **submit page** — freezes the words and puts the page in the queue. Then "The page is in." with **take next**, **pick another**, or back to the studio.
+
+Only the holder writes. A page someone else holds is read-only and names them. A draft left unsubmitted keeps its words and can be taken up again.
+
+**Between submit and approval, a session applies it.** Submitted pages wait for a builder session running `/tweak` ([the skill](../../.claude/skills/tweak/SKILL.md), Metic+). It transcribes every line, renders the page before and after, and parks it. **It never lands the page.**
+
+**The Approval queue.** Pictures of the applied page, desktop or phone, light or dark, flipped **before / after**. Beside them, the changed lines ("was:" / "becomes:"); a line the applier could not apply says why. Then:
+
+- **approve and ship** — it lands, the page's count goes up, and the artist is paid **30 credits** for the page, shown in the tally;
+- **send it back** — with a note of at least ten characters; it returns to the `/tweak` queue and comes back once it is re-applied.
+
+**Gone from the artist's loop:** the per-ship "Artist review" task (a ship that changes a page's words now marks it "changed since last tweak", and the Flow raises it) and flagging single strings on the copy desk (archived; a page is the unit now). Reviews filed before Tweak Mode are still answered behind the studio's quiet door under the actions ("1 review from before Tweak Mode still waits"), shown only while one does.
+
+**When the artist is at the terminal instead.** You are their hands. The same routes the pages use are on `node scripts/gds/api.js` under `/api/bongos/copy-desk/`: `GET next`, `POST pages/<id>/claim`, `GET pages/<id>/draft`, `PUT pages/<id>/draft` (the whole draft, `{ reading_hash, lines: [{ key, after }] }`), `POST pages/<id>/submit`, `GET approvals`, `POST pages/<id>/approve`, `POST pages/<id>/send-back` (`{ note }`). Put *their* words in, then open the editor or the queue so they see the result. Never approve on their behalf.
+
+---
+
 ## The first rule: show, don't narrate
 
 In every other craft Claude narrates — diffs, logs, paragraphs about what it is doing. **Here that is the failure mode.** An artist judges with their eyes.
 
 > **Show, then briefly caption. Never narrate the pipeline at length.** Every step ends in something the artist can *look at*, with at most a one-line caption. The plumbing still runs; it runs quietly.
 
-- **End every step with something visual.** After a generation, display the image. After a copy change, show the rendered text in place, not a diff. After a check, show the scorecard, not a prose summary. They should see the result before they read a word.
-- **Collapse the plumbing to one-liners.** Budget checks, config edits, retry tiers, atlas rebuilds — do them, report them as a single line or a number. "Generated, scored 0.91, on-palette, staged ✓" beats three paragraphs.
-- **Verification is looking, not reading.** Surface the rendered surface and the sandbox preview, not console logs. Logs are for when something breaks, not for routine success.
-- **Nothing that changes a page ships until they have seen it** (the project default, owner 2026-09-23). Show the before and after in both modes at desktop and phone width, opened in their browser with `node scripts/gds/review-sheet.js` (a terminal shows no images), and ship on their OK.
+- **End every step with something visual.** After a generation, display the image. After a copy change, show the rendered text in place (the studio, the editor, the Approval queue), not a diff. After a check, show the scorecard, not a prose summary.
+- **Collapse the plumbing to one-liners.** "Saved, 12 of 38 lines rewritten" beats three paragraphs.
+- **Verification is looking, not reading.** Surface the rendered page, not console logs. Logs are for when something breaks.
+- **Nothing that changes a page ships until they have seen it** (owner, 2026-09-23). In Tweak Mode the Approval queue is that look. For other work, show the before and after in both modes at desktop and phone width with `node scripts/gds/review-sheet.js` (a terminal shows no images), and ship on their OK.
 
 ## The second rule: as little interpretation as possible
 
 The artist owns the look; you own the rendering. **You are their hands, not their art director.**
 
-- **Take the brief literally.** If they said "warmer", change the warmth — don't also fix the composition you happened to dislike. An unrequested improvement is an interpretation, and interpretation is what this rule is against.
-- **Don't explain your reasoning about taste.** They did not ask why; they asked to see it. If a request is genuinely impossible, say what stopped you in one line and show the nearest thing you could make.
-- **Don't offer a critique they didn't ask for.** When they want a second opinion they will ask, and there are graded review loops for it.
-- **Ask at most one question, and only when you truly cannot proceed.** Everything else you resolve by making something and showing it — a wrong first attempt they can react to is worth more than a right question they have to answer.
+- **Take the brief literally.** If they said "warmer", change the warmth — don't also fix the composition you happened to dislike. Put their words on the page exactly; an unrequested improvement is an interpretation.
+- **Don't explain your reasoning about taste.** They did not ask why; they asked to see it. If a request is impossible, say what stopped you in one line and show the nearest thing you could make.
+- **Don't offer a critique they didn't ask for.** When they want a second opinion they will ask.
+- **Ask at most one question, and only when you truly cannot proceed.** A wrong first attempt they can react to is worth more than a right question they have to answer.
 
 ## The third rule: arrive precalculated
 
 Setup is your job, and it should already be done when they get here. **A session that opens with questions is a form.**
 
-- **Load the look before you make anything.** The instance's palette, tokens, voice and style rules live in [`config/branding.neutral.json`](../../config/branding.neutral.json) ([contract](../branding-contract.md)), `DESIGN.md`, and the instance's own identity scaffold [`docs/project-context.template.md`](../project-context.template.md). Read them first, silently.
-- **Have the options ready.** Where a choice is coming, generate the candidates before you ask, so the question is "which of these" over pictures — never "what would you like" over a blank.
-- **Never present a checklist.** No numbered intake questions, no "please confirm the following", no form. One line of orientation, then the work.
-- **Locked things stay locked.** A palette, a rubric, or a token contract is not edited to make one asset pass — that is whole-project drift. Changing one needs an ADR.
+- **Load the look before you make anything.** The palette, tokens, voice and style rules live in [`config/branding.neutral.json`](../../config/branding.neutral.json) ([contract](../branding-contract.md)), `DESIGN.md`, and the identity scaffold [`docs/project-context.template.md`](../project-context.template.md). Read them first, silently.
+- **Have the options ready.** Where a choice is coming, make the candidates before you ask, so the question is "which of these" over pictures — never "what would you like" over a blank.
+- **Never present a checklist.** One line of orientation, then the work.
+- **Locked things stay locked.** A palette, a rubric, or a token contract is not edited to make one asset pass. Changing one needs an ADR.
 
 ---
 
 ## Step 0 — is an artist here?
 
-- Someone is present to look and react → **interactive mode**: show, react, iterate. Loop until they are happy; each pass ends in a picture.
-- Autonomous, bypass-permissions, or scheduled → **autonomous mode**: nobody is watching the images, so do not narrate into the void and do not lower the bar. Make it, gate it hard against whatever standard the surface has, stage the passes for review, and park them. In the session log give the preview URL and one line per asset — so the first thing the returning artist does is *look*, not read.
+- Someone is present to look and react → **interactive mode**: show, react, iterate, each pass ending in a picture.
+- Autonomous, bypass-permissions, or scheduled → **autonomous mode**: nobody is watching, so do not narrate into the void and do not lower the bar. Make it, gate it hard, stage it for review, and park it. **Never approve a page in the Approval queue for an absent artist.** In the session log give the preview URL and one line per item, so the returning artist's first act is to *look*.
 
 If unsure, ask once; if no answer, treat it as autonomous.
 
 ---
 
-## What the artist's work actually is here
-
-The subject varies by instance; the stance above does not. In this core the standing surfaces are:
-
-- **The project's user-facing text** — the copy desk (`modules/copy-desk/`) is the artist's review loop over live copy. It is deliberately **not a CMS**: nothing on that page edits a string. A bad line becomes a claimed, graded task like any other change.
-- **The project's interface** — visual and layout work is the `ui` discipline and has its own playbook (`/design`), contributed by `modules/ui-design/`. Adjacent craft, separate lane.
-- **A pixel-art or asset pipeline**, when the instance ships one. It is a host module and is **not** part of the portable core, so its commands, palette, and rubric live with that module rather than here; on a core-only checkout those files are simply absent. Drive whatever pipeline the instance has via its own skills — never freelance around it, and never hand-edit its locked palette or rubric without an ADR.
+## The other surfaces
 
-The artist role also carries a deploy-time gate of its own in some instances (ADR 0241) — the artist's authority over what the project looks like when it goes out.
-
----
+- **The interface's form** — visual and layout work is the `ui` discipline with its own playbook (`/design`, from `modules/ui-design/`). Adjacent craft, separate lane.
+- **A pixel-art or asset pipeline**, when the instance ships one. It is a host module, not the portable core, so its commands, palette and rubric live with it; on a core-only checkout they are absent. Drive it via its own skills, and never hand-edit its locked palette or rubric without an ADR.
+- The artist role can carry a deploy-time gate in some instances (ADR 0241).
 
 ## Scoping art work
 
-When you scope or present an art task, factor in that the reader judges by eye:
-
-- **Lead with the visual target**, not paragraphs — the subject, the reference it should sit beside, an example if one exists. "Make this," shown.
-- **Express done-when in visual terms** — "reads as weathered marble in-world, every pixel on the locked palette" — not a procedural step list.
+- **Lead with the visual target**, not paragraphs — the subject, the reference it should sit beside, an example. "Make this," shown.
+- **Express done-when in visual terms**, not a procedural step list.
 - **Keep procedure out of the task.** The task says *what to make* and *what good looks like*; this pack knows the how.
 
----
-
 ## Feedback becomes a durable rule
 
-When the artist reacts — "too saturated", "that reads as modern", "weather the marble" — don't just tweak once. Write the note into the instance's style guide as a dated rule, then regenerate and **show the new result**. The loop is see → react → see again, and the guide gets smarter every pass. A tweak that lives only in one asset is a tweak you will be asked for again.
+When the artist reacts — "too saturated", "that reads as modern" — don't just tweak once. Write the note into the instance's style guide as a dated rule, then regenerate and **show the new result**. A tweak that lives only in one asset is a tweak you will be asked for again.
 
 ---
 

package/docs/packs/engineer.md

@@ -88,6 +88,8 @@ Three manual slash-commands keep the methodology surfaces from accumulating drif
 - **`/blocker-review`** — walk the open blockers: resolved (which auto-promotes linked tasks via a DB trigger), still blocked with a note, or escalate.
 - **`/backlog-review`** — walk `status='backlog'`, the pre-workable state a human must say go on. Rows waiting on a **person** get walked (promote / kill / water); rows waiting on a **trigger** are counted, never walked (a satisfied dep auto-promotes). It also surfaces rows stranded behind an abandoned dep, which the trigger can never fire for. `/demote` is invalid on a backlog row (409 `cannot_demote` — it requires `ready`).
 
+**`/tweak`** (Metic+) works a fourth queue: pages an artist submitted from the studio wait there until a session applies them. It never lands one; the artist approves first (ADR 0341).
+
 If a day passes without them, the queues quietly grow. Running them is the structural cure for the markdown-graveyard pattern.
 
 > **`/merge-mode` is not a daily chore** — don't run it on a schedule or tell builders to. The server lands merges itself: green PRs auto-merge, a 5-min reconciler flips `confirmed → shipped`, and the ADR 0082 resolver self-heals generated-file conflicts. It is the rare manual fallback for a strand still stuck after that sweep.