Repository navigation
Show the plan each CLI reports and save a turn's task record to Notes (CF-7, first part) - #289
Merged
Merged
Conversation
Codex's turn/plan/updated (pending, inProgress, completed, and an
optional explanation) and Claude Code's TodoWrite todos (pending,
in_progress, completed) become plan.update observations; a status Modex
does not know is unknown. Each update is a revision of one plan item
per turn, which never folds away and takes the turn's outcome when the
turn ends. "completed" stays what the CLI reported; nothing is marked
verified. The phone receives a plan as steps plus a text summary
("Plan · 1 of 2 reported done") that older builds show as is.
Refs #280
Coven-Harness: Claude Code / claude-opus-5-5
taskRecord/taskMarkdown summarise one turn: request, latest plan, changed files relative to the project (files outside it are counted, not named), commands with outcome and exit code, the answer and what is not settled, with a backlink to the thread. No reasoning, output or outside paths. task:save-note (ThreadRunner.saveTaskNote) writes it into the thread's project notes as a human change; saving again updates the same note, unless it was edited since, when the edit stays and this version becomes a new note. The thread remembers each turn's note. Refs #280 Coven-Harness: Claude Code / claude-opus-5-5
… turn TaskPlanCard lists each step as Not started, In progress, Reported done or Status unknown, with where the plan came from and its revision. Under each finished turn, Save to Notes (then Update note) saves the turn's record and offers Open. e2e/task-to-notes.spec.ts failed on both tests before this and passes now. Refs #280 Coven-Harness: Claude Code / claude-opus-5-5
Refs #280 Coven-Harness: Claude Code / claude-opus-5-5
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
13 tasks
The offline store demo has no Notes, so task:save-note is unavailable there like the other knowledge commands. CI's full build caught the missing handler. Coven-Harness: Claude Code / claude-opus-5-5
Code coverage overviewLanguages: TypeScript TypeScript / code-coverage-agent
View coverage of the 10 most impacted files.
ℹ️ Calculations represent line coverage. Results may change as calculations are updated. |
14 tasks
BunsDev
added a commit
that referenced
this pull request
Oct 18, 2026
Coven-Harness: Claude Code / claude-opus-5-5
BunsDev
added a commit
that referenced
this pull request
Oct 18, 2026
Brings in #289 (CF-7, first part) before the next steward commit. Coven-Harness: Claude Code / claude-opus-5-5
BunsDev
added a commit
that referenced
this pull request
Oct 18, 2026
Val decided on #290: Known rough edges keeps only open problems. Six fixed incidents move, word for word, to docs/reviews/2026-10-18-resolved-rough-edges.md, each under the PR that fixed it (#153, #189, #190, #197, #204, #265 and #271). The section now links to them. Entries with an open part stay: the layout e2e note, the demo-thread and sizing test corrections whose causes are unproven, and the poisoned ChatGPT threads. Also: node-pty's line says Modex still ships the beta, the demo-thread note no longer waits on a merge that happened (#189), and the tracker pointers list the open CF PRs after #289 landed. Coven-Harness: Claude Code / claude-opus-5-5
BunsDev
added a commit
that referenced
this pull request
Oct 18, 2026
Coven-Harness: Claude Code / claude-opus-5-5
BunsDev
added a commit
that referenced
this pull request
Oct 18, 2026
The only conflict was claude.ts's import of conversation-event types. It keeps CF-2's ApprovalAnswer and adds CF-7's PlanStepStatus. CF-7's TodoWrite plan observation sits in handle(), apart from CF-2's lifecycle code. Refs #275 Coven-Harness: Claude Code / claude-opus-5-5
BunsDev
added a commit
that referenced
this pull request
Oct 18, 2026
…ycle 1) (#292) * Record what shipped in plans, specs, README and status Docs and plans steward, cycle 1 (#290). - Plans: a status line on each ledger under docs/superpowers/plans/ and on docs/mac-store-preview-plan.md, naming the PRs and release that delivered it. Unticked boxes stay as history rather than being ticked after the fact. - Specs: routines (Phases 0 and 1 on main), sticky Auto routing (shipped in v0.0.11) and approval rules (parts 1 and 2 shipped, gate off). - README: app-owned sign-in, self-updating Macs from v0.0.12, Windows and Linux installers from v0.1.0, Images and Plugins no longer marked unreleased. - status.md: the site's static fallback follows apps/site/release.json; the delivered release-candidates entry leaves In flight for a pointer to tracker #273; Next 3 points to #286. Coven-Harness: Claude Code / claude-opus-5-5 * Bring reference docs in line with main and the releases Docs and plans steward, cycle 1 (#290). Each change was checked against the code on main, a release section of status.md or a review. - Shipped work no longer reads as pending: the approval rules editor (v0.0.7), Modex sign-in (v0.0.9), 1Password filling (v0.0.11), the notes folder (v0.1.0), the hosted native updater scenarios and the first published-to-published upgrade, and Windows/Linux publication. - Behaviour matches the code: Windows and Linux show no update banner; Auto's judge sees a placeholder for assistant replies and runs `jev` with one attempt; Claude's model list is Modex's fixed aliases; the Settings sections and transport labels; Space options → Agent notes; the companion's policy route and current version; the knowledge fence for overlapping folders; CI's e2e runs the unpackaged build. - The Store record and processed 0.0.8 package are recorded under gate 5. Coven-Harness: Claude Code / claude-opus-5-5 * Close the two finished In flight entries and add the GitHub App to Next Val decided on #290: the local work recovery and retired worktrees entries are done, so they leave In flight. The recovery audit and the archive READMEs keep their record. Their one open item, repository authorization through a GitHub App, becomes Next 4, ahead of the out-of-scope Cloud tasks. Coven-Harness: Claude Code / claude-opus-5-5 * Move fixed rough edges into a dated review Val decided on #290: Known rough edges keeps only open problems. Six fixed incidents move, word for word, to docs/reviews/2026-10-18-resolved-rough-edges.md, each under the PR that fixed it (#153, #189, #190, #197, #204, #265 and #271). The section now links to them. Entries with an open part stay: the layout e2e note, the demo-thread and sizing test corrections whose causes are unproven, and the poisoned ChatGPT threads. Also: node-pty's line says Modex still ships the beta, the demo-thread note no longer waits on a merge that happened (#189), and the tracker pointers list the open CF PRs after #289 landed. Coven-Harness: Claude Code / claude-opus-5-5 * Move status.md's release sections into their release reviews Val decided on #290: status.md keeps the Shipped table as the index, and each release's details live in its review. The v0.0.6 to v0.1.0 sections (651 lines) move unchanged to a "Status summary" section at the end of each review. Only link targets change, so they resolve from docs/reviews/. status.md drops from 1,060 to 388 lines. The Shipped rows now link their reviews. Four links that pointed at the old release anchors now point at the reviews. A new convention and step 1 of the release procedure say where a release's details go from now on. Coven-Harness: Claude Code / claude-opus-5-5 * Trim the Mac App Store entry to its current state Val decided on #290. The 52-line In flight entry becomes 15 lines: what Apple shows, what signed acceptance covered, and what is open, each linked to its receipt. The old entry moves unchanged to a "Status summary" section of the October 11 signed-acceptance review, with links re-based to docs/reviews/. The short entry drops two statements that no longer hold. The iPhone CI failures have been diagnosed (resolved rough edges), and the Store recovery changes are on main (edf52fc, #173). Coven-Harness: Claude Code / claude-opus-5-5
This was referenced Oct 18, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of #280 (CF-7): the part that does not need #276 (CF-3). It builds on #282, #284 and #287. Clarification through question cards waits for CF-3, so #280 stays open.
What changes
Native plans as typed plan updates.
turn/plan/updated(codex-cli 0.163.0:pending,inProgress,completed, plus an optionalexplanation) and Claude Code'sTodoWritetodos (pending,in_progress,completed) becomeplan.updateobservations.unknown.planitem per turn. The item never folds away, and takes the turn's outcome when the turn ends.Honest statuses. "completed" stays what the CLI reported ("Reported done"). Nothing is marked verified.
The plan card lists steps as Not started, In progress, Reported done or Status unknown, with where the plan came from and its revision.
The task record (
shared/task-context.ts) contains:It leaves out reasoning, command output and outside paths.
Save to Notes (
task:save-note,ThreadRunner.saveTaskNote): explicit, per finished turn. It writes into the thread's project notes as a human change.taskNotesfield.The phone gets a plan as steps plus "Plan · 1 of 2 reported done", which older builds show as text.
Docs:
docs/task-context.md, and status.Evidence
Base
d3711c6, head3b66524(four signed commits). The rebase over the CF-5 merge left the tree byte-identical; the checks below ran on that tree, at39b7c7d.test/task-context.test.ts: the module and observation didn't exist; thesaveTaskNotetest failed for its missing method.e2e/task-to-notes.spec.ts: both tests failed before the UI.pnpm test: the first stage ran 1,539 tests, with 1,522 passed, 16 skipped and 1 failed. The failure was "knowledge does not adopt failed, unready, unidentified, or UI-less servers"; it passed 2 of 2 alone. The run had stopped there, so the second stage wasn't reached.task-to-notes,conversation-evidence,typed-turns,sources,app,agents,event-journal,space-fitandcompanion. The failure was theapp.specaccessibility test's sidebar step, where two "Chat details" dialogs were open at once; it passed 2 of 2 alone.Not covered here (#280 stays open)