10 Commits

Author SHA1 Message Date
eust-w
3217982f32 🔀 Merge project knowledge
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

# Conflicts:
#	apps/web/src/features/projects.tsx
#	apps/web/src/lib/types.ts
#	docs/architecture.md
#	docs/reference/ui.md
#	docs/requirements.md
#	docs/user-manual.md
#	tests/local-loop.test.ts
2026-11-04 12:45:22 +08:00
eust-w
302635254a 🔀 Merge executor settings
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

# Conflicts:
#	docs/architecture.md
2026-11-04 12:43:44 +08:00
eust-w
da1cfcea13 🔥 Remove the cloud IDE
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>
2026-11-04 12:43:02 +08:00
eust-w
c6d37e3cc3 ✨ Add the 知识库 page for managing project skills across projects
Top-level console entry listing skills of every visible project with
project, status and category filters and search; confirm, edit, enable,
disable, delete, import SKILL.md / zip, copy to another project and
export. The project page shows a summary linking there; project settings
gain the auto-activation switch; docs describe the unified skills.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-11-04 12:37:36 +08:00
eust-w
4e9e5fb874 ✨ Let tenant admins configure each executor: gateway, models and time limit
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>
2026-11-04 12:19:02 +08:00
eust-w
addf330b10 ✨ Add account types and enforce per-user wish permissions
- 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>
2026-10-28 12:07:08 +08:00
eust-w
17553e2f8f ✨ Let a person widen a frontend-only wish to backend code
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>
2026-10-27 23:19:08 +08:00
eust-w
bf3313620e ✨ Let each wish stay frontend-only, and optimize wishes into short goals with choices
- 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>
2026-10-27 20:37:30 +08:00
eust-w
44b1bee723 🐛 Treat POC images deployed by tag as of unknown source
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>
2026-10-27 17:58:42 +08:00
eust-w
9006de384e 📝 Write a manual for the console's users and the local service's maintainers
One document that walks through the console page by page: core concepts,
how to write a wish, what a run does, what to do when it stops, approvals,
rollback and undo, members and roles, code review, wish optimization,
notifications, and the operator's guide to the local service.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-27 17:08:27 +08:00