← Design · c143
PICKUP.md
c143 Pickup Note
Contents
Parked: 2026-11-12, at the end of the merge sweep; updated the same evening after everything outstanding was pushed (see CYCLE.md Key Changes for what landed). Pick this up to tie off the longer-running loose ends, or before the next sweep: start by re-running the survey in "Suggested first hour", because other sessions keep moving.
Where every thread stands
Owed, from work merged this week
| Item | State |
|---|---|
c133-sketch-record.png. The c133 story's record-sketch outcome points at it. | ✅ captured 2026-11-12 (1d353daad0), only its manifest entry committed (the tool re-sorts the whole manifest) |
| c7 Web Rail captures (qnative) | ⏳ owed. The rail merged without them, on Mark's word. |
| c7 call: with no fill, the lit Dev page is the same cyan as its siblings (c6's tint holds through hover and the lit row) | ✅ superseded 2026-11-12: Mark made developer mode's group grape (the brand's primary) on its title and pages; the cyan is the tour's alone (qnative fbd9e5a) |
Layer release: q-nuxt-layer main e7e1454 (PolicyTag "Off") is pushed, not released | ✅ v0.9.38 published 2026-11-12 (1647e2f); lockfiles bumped and pushed in design 5ecc1b4365, bob-wire e958f99, qflow f7de370 and qdash 43c29ea5f |
| Design deploy: #18, #20, the c4/c6 captures, c140, c142 and c133 Phases 6–7 | ✅ deployed 2026-11-12, 17:08 UTC. Mark had the c133 and c142 commits pushed first. deploy 5e4ad09939, 6,937 routes; _deploy.json: design a6694996e8, layer 0.9.38, 1 uncommitted path (the c130 PNG). The new pages return 200 on design-f39.pages.dev. |
| Design deploys, evening 2026-11-12 | ✅ two more: 23fed8856e (design 169e0b867a, after the pushes) and af19753d92 (design e74e06fbe3, 6,945 routes, nothing uncommitted, layer 0.9.38) with the trainings page's prototype links, the quiz wording and qnative c9's record; checked on design-f39.pages.dev. The prerender's link errors are the same class as below. |
30 prerender errors in the deploy log: links in records that the crawler can't resolve (/cycles/design/c138.developer-mode and mcp-guide-u4 as cycle ids, todos-2026-09-* as weeks, /api/evolution/native/app-status, qnative c4's captures/messaging.json.md) | ⏳ content fixes per record (c129 lists the same class); they don't fail the build |
cycles/c130.native-app/agent-sessions-design-since-tuesday.png (11-12 07:21) | ✅ committed to c130 2026-11-12 (b0979ad28d): Mark's screenshot of the program's agent sessions since Tuesday |
qnative c8 (the native port specs, design c140 D13): five commits through 40be83f, local only | ✅ pushed 2026-11-12 on Mark's word ("push this and anything else outstanding"), with the scorecard commit 360fbd4 and c143's three (9ae1424, c45646f, 9628a2a); qnative main at 9628a2a. Review stop 1's three calls stay open. |
| Another session's uncommitted qnative work (the New to Qpoint tour, the grape Dev group, Source's change line, the scorecard's wrapping) | ✅ committed and pushed 2026-11-12 on Mark's word (fbd9e5a), with the README's quick start and flags (b477a0e, 880451a) |
| The Monitor contract (qnative c3 Guide 4) asked for richer copies of D17's shapes | ✅ reconciled 2026-11-12: one ask per route (design 2fae338529, qnative 9ae1424) |
The bridge's config fixtures were invented TOML (config.toml) | ✅ 2026-11-12: qcontrol's config.yaml, loaded by qconfig from qcontrol main (design 930f090ade, qnative c45646f) |
| c139 review stop 1: eleven calls | ❓ Mark, in cycles/c139.updates/review-1.md |
Design CI red on every run since 2026-11-04 (found 2026-11-13 at design#22): npm ci gets 403 permission_denied: read_package on @qpoint-io/qmap 0.1.0 from GitHub Packages, which entered the lockfile with c123 (2759e45); the workflow's GH_NPM_READ_JON_PAT can read the layer but not qmap. Nothing in the code; the site deploys from Mark's laptop, so nothing is blocked | ❓ an org admin: give qpoint-io/design read access to the qmap package (Packages › qmap › Manage Actions access), or a token whose owner can read it; then one green run. Queued as a task card from the shape.md thread. Follow-up once green: the workflow pins Node 20 and rollup-plugin-visualizer@7 wants 22 (EBADENGINE, a warning today) |
Worktrees that were in use: ✅ removed 2026-11-12
qnative-c2 (12 GB), qnative-c3 (56 GB) and the c6 worktree (48 GB) are removed, with their branches c2/rulings, c3/phases and claude/c6-lean-marker; every commit on them was already on main. On Mark's word: the two old app copies running from c2 and c3 were quit, and the c6 session was archived.
Kept on purpose
| Item | Why |
|---|---|
design .claude/worktrees/c117-* (two) | c117's Alexander and overview work is held there |
qcontrol-c113 | untracked check-baked.json (c113's E1–E3 check of demo.qpoint.io, 2026-10-07); c113's pending items (delete the containers, the deleted_classes migration, the bake schedule) |
branches c112/demo-container, c113/baked-demo | ✅ pushed to origin 2026-11-12 for safekeeping; delete them when c112 and c113 close |
qmap/.claude/worktrees/determined-meninsky-2ea1d6 | untracked dev/experiments/c28.haiku/HAIKU.md (2026-05-13) is not in qmap main. Main's c28 is c28.live-qcontrol-stream, so the number clashes. |
qcontrol/.claude/worktrees/hopeful-margulis-2be528 | detached at 8aaf1c9f4 (qdash scale fixes, 2026-10-05; also on local qdash/scale-fixes); clean; not reviewed |
qcontrol-main (added 2026-11-13) | detached at origin/main 8677b44ed, a read-only reference for c138's Live parity work. Its crates/qdash/ui/node_modules is an APFS clone of the Fable checkout's (the dependencies are identical), plus untracked public/_corpus.jsonl and _sentinel.jsonl. Run it with design's launch config qdash-main (:3031, NUXT_LOCAL_LAYER=1, against the seed on :7882). Remove it with git -C qcontrol worktree remove --force ../qcontrol-main once c138's Phase 3 and the wipe are done. |
qcontrol feat/new-pages d274b9306 (2026-11-13) | ✅ pushed 2026-11-13 on Mark's word: main's Audit log in the Fable /live (c138), now in PR qpoint-io/qcontrol#713. |
design c145.setup-tour (2026-11-13) | stage 1 only: initial-prompt.md and plan.md, with four rulings for Mark before any build. Not in CYCLES.md until kick-off. |
Live when parked: leave to their sessions
- design:
cycles/c140.surface-evaluation/,c141.surface-docs/,c142.cycle-tours/,brand/glossary.md, and their edits tocycles/CYCLES.md,c133,c135. - qnative main: about 92 paths in flight, a crate move into
crates/qguikit, partly staged.
Older uncommitted work: needs its owner's call
| Repo | What | Dates |
|---|---|---|
q-nuxt-layer main | dev/ControlColor.vue (an HSB picker in place of the native one), dev/Configurator.vue (collapsed), nav/JumpPills.vue, ux/PageTitle.vue, composables/useStickyBand.ts | 10-18 → 11-03 |
qcontrol feat/new-pages | crates/qdash/README.md (a rewrite, −335 lines), crates/qdash/ui/README.md, ui/app/pages/compliance.vue, devenv.nix, new crates/qdash/docs/how-it-works.md | 10-05 → 11-03 |
market-analyst main | ✅ ruled 2026-11-12: the 19 calls are internal (team syncs, all-hands, 1:1s, an investor monthly), so they are kept local and never committed, hidden through .git/info/exclude (remove a line there to bring one back) | 09-22 |
qmap main | ✅ the 15 commits pushed 2026-11-12 (29b3de2, on Mark's word); ~50 changed paths still uncommitted, and c28.haiku in a worktree | 02 → 11-04 |
bob-wire c16-agent-control-plane | c17, c20 and c21 pages and data | 06-16 → 09-03 |
qflow ai-ecosystem-visualizations | dev/experiments/c12.qcontrol-live-view/ and edits | 03-25 → 07-29 |
design main | ✅ the nested c3 move reverted 2026-11-12 (identical copy; c3 back at cycles/c3.app-migration/); the c130 PNG committed | 02-26; 11-12 |
| www.qpoint.io | ✅ 2026-11-12: the checkout is on main; disable-dark-mode deleted locally and on origin (#65 merged long ago, and since then the branch only collected layer bumps); www dropped from update-consumers.sh (layer f581e09), so bump it by hand when Rob wants the layer (main is on 0.9.0) | — |
Older open PRs
| PR | Recommendation |
|---|---|
| qcontrol#713 Initial Nuxt Frontend Buildout | keep open; the qdash branch, waiting on Tyler's review |
qcontrol#692 index on tool_calls(run_id) | ✅ closed 2026-11-12: feat/new-pages already carries the index (4f6b16ce8), so it lands with #713 |
| qmap#4 Cycle 14+ | ✅ closed 2026-11-12 after qmap main was pushed: main supersedes it (its own publish workflow, #6 and #7) |
| www.qpoint.io#56, #51, #47 | all conflict and are 6–11 months old. Ask Rob (active on the site, #86) which are still wanted; close the rest. |
| app.qpoint.io#247, #238, #166 | ✅ closed 2026-11-12 as superseded; app.qpoint.io dropped from update-consumers.sh (layer db128d4) |
| 24 bot PRs (dependabot, captainqpoint; lockfile bumps from March to May) in design, layer, qflow, market-analysis, bob-wire, qmap, www, app | close; run one npm audit fix pass per repo. qcontrol's three (#707, #673, #592) are the product team's. |
The decision queue
- qmap:
push main's 15 commits and close #4(done 2026-11-12); still to decide: the ~50 uncommitted paths andc28.haiku. c112 and c113 branches.Pushed 2026-11-12.- The layer's five uncommitted files: finish and release them, or roll them back (c103 noted layer props "under evaluation").
- qdash's README rewrite and
how-it-works.md: commit tofeat/new-pages, or drop. market-analyst's 19 raw calls.Kept local, 2026-11-12.- The older PRs above that are still open: the www PRs (Rob), the bot PRs.
- Design CI (added 2026-11-13): the qmap package permission, so PR checks mean something again (the "Owed" table).
Suggested first hour at pickup
- Re-run the survey (other sessions move fast):
cd ~/web/qpoint && for d in design q-nuxt-layer qnative intents market-analyst qcontrol bob-wire qflow www.qpoint.io qmap; do git -C $d fetch -q origin; printf "%-15s %-28s %s uncommitted:%s\n" $d "$(git -C $d branch --show-current)" "$(git -C $d status -sb | head -1 | sed 's/^## [^ ]*//')" "$(git -C $d status --porcelain | wc -l | tr -d ' ')"; done
And the open PRs:GITHUB_TOKEN= gh search prs --owner qpoint-io --author @me --state open. - Clear the "Owed" table: the layer release, then the deploy, then the c7 captures.
- Walk the decision queue with Mark.
Restore points: deleted 2026-11-12
Restorable with git branch <name> <sha> until git prunes unreachable objects (about two weeks):
| Repo | Branch | SHA |
|---|---|---|
| qcontrol | backup/feat-new-pages-pre-rebase | cf065ab0832ae3cf0466b8c95239c808237758fd |
| qcontrol | backup/feat-new-pages-pre-rebase-1005 | c9da3b5526fa21a43c29ec4cb61c027c5fe94097 |
| design | claude/jovial-dubinsky-36e37e | bedcca7bb7f50a46269da4f9ca4cd48cb6793c57 (also the HEAD of the c117 Alexander worktree) |
| design | c81/phase1-pages | 014dc95a98d160f9bd1a43f4e9b07bfe96ae3959 (merged as #13) |
The other deleted branches were merged PRs or contained in main.
How the conflicts were untangled (for the next sweep)
- Shared indexes (
CYCLES.md,page-registry.ts, story modules, a CYCLE.md's Documents line): keep both. Main's newer version of a rewritten line wins, and the branch's addition goes beside it. - Capture manifests (
public/cycles/<project>/manifest.json): merge by entry, keyed byfileplusvariant. Main's entries, plus the branch's new ones. Check that nothing was dropped or changed. - Code (qnative
shell.rs): keep the branch's new structure and carry main's behaviour into it, then build, test, run the lean check and let CI pass before merging. - Never stash or reset in a tree a live session uses. Rebase in a scratch worktree, push, and merge through the PR. When moving a branch ref under a live tree, do it only when the trees are identical, with
git update-ref <ref> <new> <old>.