An answer travels in a submit_answer tool call, and the model writes its
line breaks there as the two characters \n. The console draws exactly what
it is given, so a customer read \n\n where a paragraph break belonged.
The layout escapes are now unfolded once, where model text enters: the
answer, the Wish draft, the quick replies and the excerpts all pass one
door. Answers stored before this change are unfolded as they are drawn, so
the history reads correctly without touching the database.
The settings checklist pulled values from the contracts barrel, which
Turbopack cannot follow. The catalog now lives in its own entry.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- Provide six account types and custom combinations of wish, code review,
release and management permissions, applied on each authenticated request.
- Enforce frontend-only accounts when submitting, answering, widening and
reverting wishes; require every contributor to have full access before
skipping backend code review.
- Gate code review and release decisions by their specific permissions.
- Rework member management to create and edit account types, permissions and
project access, and reflect those permissions throughout the console.
- Update the manual and architecture docs with permission tests and
end-to-end coverage.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- Each wish says whether it may change backend code. A frontend-only wish is told
which paths it must leave alone; a change to them goes back before any check runs,
the platform puts those files back before the repair round, and the control plane
never integrates them. A wish that may change backend code integrates directly for
people with backend permission and waits for a code review otherwise.
- Owners and admins grant backend permission per person on the members page as well
as per project in the project settings.
- AI optimization has its own button for the wish and for the criteria. It writes a
wish of at most three lines (goal, scope, limits), keeps the details in checkable
criteria, and asks only what the person must decide, as choices whose answers join
the wish; suggested criteria are taken one by one.
- Lists, run titles, Feishu cards and pull request titles show a wish's first line;
the run details show the rest.
- Changed paths no longer follow renames, so moving backend code into a frontend
directory counts at both places for code review and for the frontend-only scope.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
What the pilot asked for, from its meeting:
- Code review: a project names the paths changes to which a person reviews
before they reach the target branch (globs, with exceptions). After the
checks pass, the verifier asks the control plane, and the run waits at
integration until an owner or admin approves the exact commit; approving
integrates it without repeating the checks, rejecting hands the comment to
the agent as a new requirement. Continuing cannot get around it: the
verifier asks again before every integration.
- Undo: "take back this change" starts a run that reverses what a run
integrated on the current target branch, three-way, keeping later commits;
only lines later commits changed too go to the agent. It then verifies,
integrates and delivers like any run. Releases get a rollback button for the
version live in their environment.
- Wish optimization: the local Claude account rewrites a draft wish and its
acceptance criteria by built-in and project rules, with no tools at all;
the person compares and decides, nothing is submitted for them.
- Release confirmation: an environment can make every release wait for a
person, not only those the risk rules flag.
- Feishu notifications: a group bot is told of releases awaiting approval and
changes awaiting review (mentioning the decision makers), runs that need a
person, finished runs and failed releases; each once, signed when a secret
is set, with text from runs never acting as card markup.
- Reviewers see the agent's change summary and who submitted the wish, and
whether the checks ran in the macOS sandbox; the wish form offers only the
executors this deployment can run.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The run timeline showed raw event kinds such as provider.file_change. Each
kind now has a Chinese label, with the raw kind kept in its tooltip; a kind
the console does not know is shown as it came.
The executor event kinds move to the import-free providers entry, so the
console's test can check that every kind has a label without pulling the
contracts entry into the browser bundle.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Building the web image showed that `next build` failed.
- The console imported runtime values from the contracts entry point.
- Turbopack cannot follow the NodeNext `.js` imports inside that entry,
which also carries zod and every schema into the browser.
- Only `next dev` had ever run before, and the console used to import
types only.
The fix:
- The executor catalog moves to an entry without imports, exported as
@wishforge/contracts/providers. The console takes its values from
there.
- providerBaseUrl moves to its own module.
- A test keeps value imports of the entry point out of the console.
With the console's default budget of 50,000 tokens, every Codex run
stopped after one model request:
- The proxy reserves one token per request byte, and a Codex request is
already about 50 KB.
- The executor then reported a bare 429 as a provider failure.
The fix:
- A request the remaining budget cannot cover now puts the run into the
`budget` wait, with what it needs and what remains.
- The console defaults to 300,000 tokens and explains the reservation.
The run page also marked the stage a successful run ended in as not yet
done; it now shows it as complete.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>