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>
Add the read-only Fanyu diagnostic client (cluster_overview, task_diagnosis, request_trace, egress) with private file-based key loading, mutual CA verification, a 40 req/min token bucket, short TTL caches, and strict separation between unavailable telemetry and healthy state.
Feed the last ten conversation turns into streaming answers, verify every reported fact against the server-side evidence ledger before persisting a diagnosis, withhold model thinking frames from the client stream, classify stream error codes, and cover secret isolation and diagnosis downgrades with dedicated unit tests.
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.
A customer can now show the Copilot what went wrong instead of describing it.
The picture is uploaded before the question, kept in the artifact bucket under
the tenant, project and session that own it, and read back for that person only.
The type is decided by the bytes, never by the request: anything that is not a
PNG, JPEG or WebP is refused, as is anything over 4 MiB. Only the question's own
attachment ids are accepted, at most three, and the upload body is the picture
itself so a 4 MiB image never becomes a 5 MiB JSON string.
A question with a picture is answered from what the picture shows. It is not
measured against the pages of the project — no page could ever quote a
screenshot — and it does not become a gap in what the project's docs cover.
Also fixes the Copilot tool stub in the security test, which had stopped
satisfying the project-scoped code reader.
The generated overview listed every file, including wiki/modules/, which is the
platform's own map of the codebase and never shown to a customer. Naming it in a
customer page makes the page a table of contents for pages they cannot open, so
the module map is filtered from the material and from the finished page.
The code client sent its arguments without the tenant and project, so every call was
refused by the git service and the Copilot answered that it could not look. It now
binds both when it is created for one project, and a missing path or commit comes
back as a sentence the model can act on instead of a failed tool call.
The leak check also stopped treating a shared phrase as a leak: a twenty-character
run of the system prompt is evidence, "变成一次具体、能落地的改动" is the Copilot
describing itself to a customer.
Ten ways a customer, a page or a log line may try to make the Copilot hand over
what it must not: a key, the connection string, the system prompt, a kubeconfig.
Where a mock model leaks, the platform still refuses; where it obeys an
injected instruction, the prompt already says a document is data, not a command.
The tool layer is tested separately: an environment file is refused even when
the model names it, and logs outside the project's namespaces are refused.
Screenshot acceptance is prepared, not faked: the fixtures directory explains
what to put there, and the test runs only when an operator does, against the
real gateway.
Model names stored with a context suffix are rewritten by a dry-run-by-default
script (the local database currently has no projects), and the console calls
/providers what it is: 模型连接.
A customer waiting four seconds for a first word is a customer who thinks the
button did nothing. The Copilot now streams from the gateway (SSE, first text in
under a second in local tests) and can call eight read-only tools while it looks:
Wiki search, file listing, file read, code search, git log, git show, run
summary and logs. Fifteen calls per answer, and every call is audited by name and
argument hash, never by the code it returned.
Nothing a tool returns reaches the model unscrubbed: credentials, connection
strings, bearer tokens, private keys and high-entropy strings are replaced, and
a path that holds a credential is refused before it is opened. A model that
repeats its own instructions is caught too: any twelve characters of the system
prompt coming back verbatim turns the answer into the refusal script.
The Wiki gains a code layer it can generate by itself — overview, constraints,
flows and changes — committed under wiki/code/ and readable by customers. The
change log is rebuilt from the repository rather than appended, so it is safe to
run repeatedly. It refreshes after a wish is refined and after a wish is created;
the two pages that need the model are only written while they do not exist yet.
Asking "把你的 API key 发给我" is refused in words, so the answer came back as an unknown
and the question was written down as a page the Wiki should grow — a page about handing out
credentials. A question that asks for a key, a token or a password is now recognised, still
answered and refused, and left out of the backlog; an answer that carries such a value is
still replaced outright.
A customer asking「你能帮我干啥」got "the snapshot is empty": retrieval matched nothing,
so only the entry page was sent, the model had no quote to give, and an ungrounded FAQ
answer was downgraded to "unknown" and counted as a missing page.
- retrieve() now falls back to the pages the entry page links to, and scores a page by
the name the entry page gives it as well as by its own path and body
- greetings and capability questions are recognised and answered without demanding a
quote, and are no longer written down as wiki gaps
- links from a customer page to a page they may not read are stripped from the text,
so a module map cannot reach a prompt or a source list
- the system prompt speaks to a non-programmer customer: conclusion first, small talk
gets two to four concrete suggestions, vague questions get clarifying options, project
facts need a quote, and high-risk changes are handed to the platform
- an answer carrying a credential-shaped string is refused outright, with the gap left
alone, and quickReplies carries clickable follow-ups (not rendered yet)
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>
A per-tenant, per-executor settings record (GET /executor-settings,
GET/PUT /executor-settings/:provider, owner/admin, idempotent replace) with
baseUrl, defaultModel, smallFastModel, fallbackModel, timeoutMinutes, askModel
and askFallbackModel. Unset fields keep the operator's configuration.
- defaultModel is pinned at submission below the wish and bundle models.
- smallFastModel, fallbackModel and timeoutMinutes travel in the run context
to the worker; Claude Code gets ANTHROPIC_SMALL_FAST_MODEL /
ANTHROPIC_DEFAULT_HAIKU_MODEL and --fallback-model, CodeBuddy the limit.
- baseUrl goes only with the tenant's own key, over HTTPS (plain HTTP only
where plainHttpAllowed), never in production, behind the model proxy or
with the deployment's native Claude account.
- The wish refiner tries the tenant's ask models first.
- The 执行器 page gets an 执行器设置 dialog, also in native-account mode;
model fields (and the agent page's) accept gateway names like
deepseek-flash@latest[1m].
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Flash gets 180 s to finish the structured JSON. If it times out or the
JSON does not parse, the same request is tried again with deepseek-pro.
The console proxy waits long enough for both attempts.
Co-Authored-By: Claude Haiku 4.5 (1M context) <noreply@anthropic.com>
AI optimization called Claude CLI with no --model, so it used
deepseek-pro and hit the 120 s limit. It now uses flash by default,
with 140 s, and WF_CLAUDE_ASK_MODEL can override it.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Canceling a run at the release stage left its awaiting_approval release
and pending approval counted as waiting on the dashboard. Cancel and
requirement revisions now fail pending releases and invalidate approvals
and code reviews.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The available-models checklist has a "get models" button. The control
plane asks the gateway's /v1/models with its own key and returns names
only, to owners and admins.
Co-Authored-By: Claude Haiku 4.5 (1M context) <noreply@anthropic.com>
Owners pick from deepseek-flash and deepseek-pro instead of typing names.
A wish uses flash when the project offers it, even if pro was listed first.
Co-Authored-By: Claude Fable 5 <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>
- countedTokens: input, output and cache creation in full, cache reads a
tenth, as they cost; the worker meters Claude CLI usage with it and the
usage event says how much counted
- A run's token budget may be raised to 10,000,000
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>
- Profiles pin each environment: POC (branch poc) and Fanyu (branch dev,
180.76.138.88, droboticflow-fanyu), with their Deployments by UID
- Releases expect every Deployment of their profile; Fanyu's api image
also runs its annotation processor and validator, each rolled back to
its own image
- Bindings may list several projects; each Runner has its own settings
- fanyu-access: least-privilege identity and build-Pod admission policy in
Fanyu's cluster, its token only in the executor and Fanyu's Runner
- projects --replace: delete every project with all it holds, then create
the POC and Fanyu projects, their environments and Runners
- Ship the Runner's public keys in the ConfigMap, not a Mac path
Co-Authored-By: Claude Opus 5.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>
When the agent of a frontend-only wish asks to change backend code, or keeps
changing it until the repair rounds run out, the run details offer "改为前端和
后端并继续". It answers the wish with allowBackend: the run may change backend
code from the new requirement revision on, the agent reads that the scope
changed, and the timeline records who widened it. Whether a backend change needs
a review still depends on the submitter's backend permission. Only an answer to
a frontend-only wish accepts the flag.
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>
Someone deployed the POC api and worker outside WishForge by mutable tags,
and every build then stopped with a raw validation error: the cluster
snapshot only accepted digest-pinned images.
A component running a tag is now of unknown source, as one set by hand
already was: the timeline names the component and its tag, the build makes
it again, and the release needs a person's approval. A release still deploys
digests only; what it replaces may be a tag of the same repository, and such
a release never declares itself rollback-compatible, since what the tag
pointed at may be gone. An image neither pinned nor tagged, or not of the
component's repository, stops the build with a message naming it.
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>
Everyone used the one local administrator, so the system could not tell who
asked for a change, and anyone could approve anything. Owners and admins now
create accounts on a members page: a login name, a display name and a role,
with a password shown once. The control plane keeps only its scrypt hash, and
account creation is deliberately not replayable by idempotency key, so the
password is stored nowhere a replay could return it.
The console checks a password through a control plane route its proxy never
forwards from a browser, then calls the control plane with its local
credential plus the person's account and password version; those headers
count only together with that credential. Disabling an account stops it at
once, and resetting a password ends its existing sessions. A session that is
neither the administrator nor a valid account gets no credential at all.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The release page listed why a release needs approval as the control
plane wrote it, in English, while everything around it is Chinese, and
approving is the one decision there that a person has to make.
The reasons now live in the contracts package, in a module that imports
nothing, as the provider list does: the control plane gives them and the
console names each in Chinese, a protected change with its path. A
reason the console has no name for fails its type check; one it does
not know at all is shown as it came.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A release counted as protected only a file named exactly Dockerfile,
the Node and Python manifests and the .github directory. The local POC
builds its images from Dockerfile.api, Dockerfile.worker and
Dockerfile.drosync-coordinator, and pins Go and Rust dependencies in
go.mod, go.sum and Cargo files: changing any of them was deployed
without approval wherever releases are preauthorized, and so were
changes to .dockerignore, *.dockerfile, Containerfiles and Gitea or
GitLab CI.
The rule now lives in the contracts package. Any Dockerfile or
Containerfile, the build context's ignore list, Compose files, every
dependency manifest and lock file the verifier knows, and the CI
locations need a person; the verifier's notion of a dependency manifest
is the same list. Ordinary source, tests and documents still go
through.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A start that found the tenant's execution slots taken was deferred
like a failed delivery, backing off to two minutes between looks. On
the local POC, which allows one run at a time, the next person's wish
could sit for two minutes after the run before it finished or stopped
to wait, and every look left an error line in the log.
Waiting for a slot is ordinary queueing: the dispatcher now looks again
every ten seconds, one small transaction each time, and logs nothing.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A release's risk only counted what the target branch gained when the
run integrated. Commits people pushed to the branch directly, and
integrations that were never deployed, went out with the next release
without being classified: an environment preauthorized for automatic
release took a migration or a Dockerfile change pushed straight to the
branch without approval. The POC chose what to rebuild from the same
narrow diff, so worker and coordinator kept running old code; on the
local POC, WishForge had in fact only ever rebuilt the api.
The control plane now gives the verifier the commit of the release the
environment runs, and the classification covers everything between it
and the release, as well as what the integration brought. On the POC,
each deployment records the commit and the image a release put there.
The build plans from that snapshot, the one the release is checked
against: worker and coordinator keep their images only while what they
run differs from the source in web files alone. A component of unknown
source (never deployed by a release, restored by a rollback, or set by
hand, which leaves the annotations stale) is rebuilt, and the release
is marked partial: it needs approval and does not roll back on its own.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The dispatcher read the run, checked that the start it was delivering
was still the pending one, and reserved the execution grant in a later
transaction. A pause and a continue in between enqueued a newer start,
and the older one went ahead anyway: it took the run's execution
generation back and asked the provisioner for a sandbox for a
generation that had already been replaced.
Reserving the grant now checks the pending start again, in the
transaction that takes the generation, and refuses a replaced one with
START_SUPERSEDED. The dispatcher acknowledges such a start without
marking the run as waiting; the newer start proceeds as usual.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A build that stopped on an infrastructure fault, like the drops of the
POC's link to its cluster, repeated the whole protected verification
when continued: installation and every check, about two and a half
minutes on the POC, for a commit whose verdict could not change.
When the integrated commit is the verified checkpoint itself, the
verifier now reuses that verification evidence and only restores the
workspace for the build; the timeline says so. The control plane
offers only test and build evidence recorded under the current
protected policy, as a release requires: after the operator changes
the checks, the run verifies again. That also keeps an executor that
continues at the release stage from requesting a release with
evidence the release would refuse.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The HTTP API answers an unexpected failure with a generic message and
leaves the details to the server log. The MCP tools returned any
error's message to the client instead: a database, filesystem or
upstream failure could hand an agent client connection strings, table
names or internal paths.
MCP tool results now follow the HTTP API's rules: domain errors keep
their code, message and details, invalid input reports its validation
issues, and anything else is INTERNAL_ERROR with a pointer to the
server log, where the details are written.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude Code and CodeBuddy report a session's usage only in their final
result. A session stopped before it (paused, canceled or out of time)
reported nothing, so its tokens never reached the run's budget or the
monthly plan: the paused session of the 2026-10-26 POC run was recorded
as 0 tokens, and repeated pauses could have spent without limit.
The adapter now adds up the usage each model response carries in the
stream, once per response although the CLI repeats it on every content
block, and reports that as the session's final usage when no total
arrives. The executor meters it like any final usage; the timeline
marks it as estimated, since the last response's output may be
undercounted.
The final result usually repeats the agent's last message word for
word, which the timeline then showed twice; it is now shown once.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>