Brings the branch up to the current base (executor settings, project
skills, Chinese run messages, cloud IDE removal, wish attachments) and
resolves the ten conflicted files, keeping both sides:
- wish-refiner: the tenant's executor settings pick the models first,
then the Copilot model setting; the tenant credential still goes
before the operator's login
- worker providers: executor settings apply, and a run with its own
credential still gets an empty home
- main.ts: Copilot screenshot uploads and wish attachments each keep
their own body limit
- contracts, http, web types: default budget and skill auto-activation,
Copilot and attachment entity kinds, ./text and ./attachments exports
- globals.css: Copilot styles and attachment styles, one after the other
- tests: the canceled-release reason is Chinese; the refiner's default
models have no [1m] suffix, as this branch names them
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Wishes can now carry screenshots, designs, logs and documents: upload,
drag-and-drop, or paste into the goal/criteria boxes. The files are stored
as attachment records, written into the executor's workspace under a
Git-ignored directory, and pointed out to the agent in its prompt. People
fetch them back one at a time (images inline, everything else downloads)
with nosniff and a sandbox CSP.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Resolved against the IDE removal and the lessons-to-skills merge; the
pitfall skills, their events and repair notes are written in Chinese too.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
The cluster never ran Theia or the IDE gateway, so every workspace stayed
"未配置" forever. The feature is gone instead of half-present:
- API: workspace, launch and lifecycle endpoints, the gateway identity and
its internal routes, the dispatcher's workspace provisioning and the
lifecycle worker. Migration 003 deletes stored workspaces and settles
their pending outbox items.
- Provisioner: workspace provisioning and lifecycle for both backends.
- Web: the 云 IDE panel, the launch route, the start-branch picker that
listed IDE branches, and the workspace count on usage.
- apps/ide, infra/oct, dev:ide and the CI job; IDE parts of local k3s,
network policies, RBAC, docs and the architecture diagram.
A wish can still start from a pushed branch through the API (sourceBranch).
Plan files and stored entitlements may still carry maxWorkspaces; it is
accepted and ignored.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
The run page mixed English stage events and agent summaries into the
Chinese console. Messages are now written in Simplified Chinese at their
source (control plane, dispatcher, worker, POC build), keeping commands,
SHAs, branches and error codes verbatim; raw runtime errors get a Chinese
prefix. The agent prompt asks for the plan, summary and questions in
Chinese. File-change parsing accepts old and new messages, and the event
label table covers every event kind written.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Lessons become skills with a category (workflow / pitfall / convention):
one model, one prompt section, one permission rule. A repaired failure
records or updates a pitfall skill deduplicated by failure signature;
harvest sees every skill and may merge into an existing one; corroborated
skills auto-activate per project (skillAutoActivation, default on).
Runs given a skill are counted (skill_usage); platform-maintained skills
retire after 3 failing runs in a row or 90 days unused. Skills can be
imported from SKILL.md / zip, copied between projects and searched across
projects. Migration 004 converts existing lesson rows to skills.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
- Skills: per-project know-how the platform proposes from each succeeded
run (in the background, or on request from a run), people confirm,
edit, disable, delete or write; active ones enter later prompts
- Export one skill as SKILL.md, or all as a zip with a directory per
skill, as .claude/skills/ expects
- A wish's report: every run, its stage timeline, the agent's plan,
replies, commands, changed files and model usage, the change, the
checks, failures, reviews and releases, and the full event log, as
Markdown, or laid out for printing to PDF
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Projects list the models their wishes may run with, the first by
default; owners and admins set them in the project settings
- A wish may choose one of its project's models; the choice is checked
and pinned to the run, which shows it, and the executor starts the
agent with it (--model), else with the agent configuration's
- Model names may be spelled as the model gateway does
(deepseek-pro@latest[1m]), in projects and agent configurations alike
Co-Authored-By: Claude Opus 5.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>
Every failed installation waited as an infrastructure fault. When the
agent's own change broke it (a misspelled package, say), continuing
installed the same manifests before the agent ran, failed again, and
the agent never got a turn: the run could not move without a new
requirement revision.
- The verifier attributes a failed installation to the checkpoint when
it changed dependency manifests (package.json, go.mod, lockfiles and
the like) and the output is not a network or registry failure. The
evidence lists those manifests, and the control plane records an
`install` failure that the next repair round fixes.
- A repair round for an `install` failure starts the agent even when
the installation fails again, with that output in the prompt.
- Prompts, lessons and the run page name the failed installation.
Any other failed installation still waits for the environment, without
spending a repair round.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The first runs on k3s found these problems; a wish now goes from submission
through the Codex executor, independent verification and integration in
per-run pods.
- Development deployments refused to start because the images set
NODE_ENV=production. The local manifest and the sandbox Jobs now set
NODE_ENV to the deployment mode.
- The model proxy treated x-client-request-id as a per-request idempotency
key. Codex sends its conversation id there, so every second request of a
session failed with 409. Only Idempotency-Key names a single request now.
- Codex's command sandbox (bubblewrap) cannot start in a runc pod. Every
command failed and the agent retried until the budget ran out. The
executor now probes the sandbox before starting Codex. A Kata sandbox that
cannot run it waits as PROVIDER_SANDBOX_UNAVAILABLE. A development (host)
sandbox runs Codex without it, and the timeline records that.
- The prompt asked agents to commit, but Codex keeps .git read-only and the
platform commits the checkpoint itself. Agents now leave their changes
uncommitted, and get the platform's Git identity if they commit anyway. A
resolved merge is recorded even when its tree equals HEAD.
- scripts/k3s-local.mjs:
- excludes the VM and cluster ranges from a host proxy (NO_PROXY);
- uses its own Docker client configuration, so a stale credential
helper does not break builds;
- recovers from an interrupted k3s install;
- reports when Colima switches the current kubectl or Docker context.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A first implementation round may end, without changing any files, with a
QUESTIONS: section of up to five questions. The executor then puts the run in
the clarification wait with the questions in its detail, where the console and
MCP show them; answering already creates a new requirement revision that
starts again from planning. Repair rounds cannot ask: they must fix what the
verifier found.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
People's changes now reach the target branch the same way the agent's do. The
IDE credential carries a ref prefix and the Git service runs a pre-receive hook
on every push that refuses updates outside it, so the IDE can push only
`ide/` branches; the platform's own integration is unaffected.
- A wish may name a source branch. The run starts from that branch's head, the
agent builds on it, and verification, repair rounds, merging onto a moved
target and conflict repair work as before. A missing branch makes the run
wait (git_storage) until it is pushed.
- Release risk is now computed from the target branch before integration, not
from where the run started: a migration committed on the source branch would
otherwise have been missed and could have skipped approval.
- Clones work on `ide/work`; a plain `git push` publishes it.
- The console lists a project's IDE branches with a button to submit a wish
that merges one, and the new-wish form has a starting-point field; MCP
`submit_wish` accepts `sourceBranch`. The Git service lists branches under
a prefix for this (`POST /refs`).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Verification ran git inside the tree under test, kept no command output and
treated every infrastructure fault as a test failure; repairs went through an
executor lease the coordinator should not hold; and a project without delivery
could never succeed. This reworks the worker execution path and the control-plane
contracts it depends on.
- Verification exports the exact commit to a directory without .git, installs
dependencies (network allowed) and runs the protected commands under
bubblewrap in kata mode or directly in host mode; evidence records exit code,
duration, digest, a redacted output tail and the isolation used. Production
rejects host evidence. A failed installation waits as infrastructure.
- Waiting reasons are an enum with a redacted detail; dispatcher, GitHub and
model-proxy states map onto it, and the console explains each one with a way out.
- Repairs are requested by the coordinator through /internal/runs/:id/repair;
the control plane derives the failure summary from the verifier's evidence and
enforces the repair budget. Continuing after the budget is spent grants one more
round; a new requirement revision starts a fresh budget.
- Execution identities may only move a run within their own stages and only to
running or waiting; success comes from integration evidence (no delivery
configured) or deployment acceptance. The unused preview stage is gone.
- Integration fast-forwards when the target has not moved, merges and re-verifies
otherwise, retries when a push finds the target moved, and turns merge conflicts
into a repair round that merges the current target for the agent to resolve.
- Successful runs that needed a repair leave a project lesson; active lessons are
injected into later prompts, and admins can list, add, disable and delete them.
- Executor progress (messages, commands, file changes, plan updates) is stored as
normalized events; previously agent messages were recorded as the literal word
"output". Provider failures keep the work as a checkpoint and wait as
provider_error instead of failing the run.
- Workers declare WF_SANDBOX_MODE=host|kata (host refused in production),
heartbeat with retries until the lease could have expired, and retry safe
control-plane reads with backoff.
- tests/local-loop.test.ts runs the loop end to end with real Git, the in-process
control plane behind its internal routes and a scripted agent.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The API signed Runner tasks with keys sorted by localeCompare, while the
runner verified with code-unit order; environment keys such as
API_URL/API2 or DB_HOST/DBA sort differently, so valid deployment tasks
were rejected with INVALID_SIGNATURE. A third copy lived in the agent
package.
canonicalJson now lives in @wishforge/contracts (code-unit key order,
undefined properties omitted, non-JSON values rejected) and is used by
the API digest, Runner task signing/verification, the runner's state
digest and agent bundle digests. Binding digests computed by the old
locale-dependent order may differ, so releases requested before this
change must be requested again.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The meta-evolution machinery (failure clustering meta-tasks, signed
offline evaluation, shadow/canary stages, external release receipts,
evaluator identity and its UI) could never take effect: promotions were
written to the system tenant only, the benchmark/runner/observer it
depended on did not exist, and its statistical gates were effectively
unreachable. It is removed as agreed in docs/requirements.md section 3.
What remains is the part every run actually uses, now explicit:
- packages/evolution becomes packages/agent and keeps only the bundle
schema, content digest and prompt assembly; consumers import it as the
@wishforge/agent workspace package instead of by relative path.
- apps/api/src/domain/agent-bundles.ts: immutable, content-addressed
agent configurations per tenant, with create, activate and rollback
restricted to human owners/admins. A run pins the active version at
submission; later activations never change it.
- /v1/agent-bundles routes replace /v1/evolution*; all /internal
evolution routes, the evaluator service token and the rsi:rollout
script are gone.
- Web: the experiment page becomes an "Agent 配置" page.
- Tests for the deleted modules are removed; control-plane tests cover
version pinning, rollback and authorization.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>