4 Commits

Author SHA1 Message Date
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
5df77ad761 🔒 Authenticate internal callers without the write lock; retire superseded generations
- Looking up a run-scoped token or a runner token ran in a write
  transaction, which holds the tenant's advisory lock: anyone with a
  long enough token could tie up every change of the tenant, and each
  executor heartbeat, event and meter took that lock just to
  authenticate. The lookups now only read.
- Continuing or answering a run queues a new generation, but until the
  dispatcher started it, the old generation's token still worked and
  could even lease the run again for the new requirement revision. A
  generation now stops acting as soon as a newer one is pending.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-25 19:11:12 +08:00
eust-w
b810423990 feat: show code changes, verification output and lessons in the console
- Runs: a per-file diff of the latest checkpoint, verification evidence with each
  command's exit code, duration and output tail (and failed installs), the last
  failure that the repair round works on, and the integrated commit when a
  project without delivery completes.
- Projects: repository status with a retry for platform repositories, the
  project's lessons (list, add a convention, disable, delete) and runs filtered
  on the server; IDE texts describe the Git hand-off instead of the removed
  save barrier.
- Releases: the approval dialog shows the requirement, project, target
  environment (production flagged), verification commands and approval deadline
  from a new review endpoint; failed releases say why. Environments locked by a
  deployment with an unknown outcome can be unlocked after a confirmation.
- Errors are titled by HTTP status; secondary text and focus rings meet the
  contrast requirements; the mobile drawer leaves the tab order when closed and
  closes on Esc.
- Sessions: the web BFF refreshes access tokens with the refresh token for up to
  12 hours; IDE gateway sessions are renewed while in use (idle timeout 15 min,
  at most 12 h) and rechecked by the granted user, so revocation still applies.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-19 17:01:30 +08:00
eust-w
5aea9b73a9 fix: harden the control plane's storage, identities and recovery paths
- Storage: read-only queries use a read-only transaction without the tenant
  lock, so event streams and dashboards no longer queue behind writers; lists
  filter on indexed project, run and status fields and the run list pages with
  limit/before. Dispatchers claim outbox items with SKIP LOCKED and a claim
  deadline; delivered items and old idempotency records are pruned hourly.
- Migrations are versioned files recorded with checksums in schema_migrations;
  002 adds the claim column and run index and migrates preview-stage runs and
  free-text waiting reasons. Run events and usage are append-only for the app.
- Identities: static service tokens reach only their routes (coordinator: state,
  wait, repair; deployer: lease, transition, releases); the static verifier
  identity is gone; Git credentials go only to the lease holder; internal bodies
  are validated; framework and body-parser errors use the API error envelope.
- Quotas: only queued or running runs (or ones with an unsettled model request)
  hold token reservations; continuing a run reserves its remaining budget again.
- Recovery: owners can list and reconcile model requests with an unknown outcome,
  and requests whose proxy died are marked unknown; definite deployment failures
  free the environment, admins can unlock an environment after checking the
  target, approvals expire with their release, and production approvals need a
  second person. The builder's Docker context is operator configuration.
- MCP: list_projects, absolute console links, request_release resolves the run's
  evidence and default environment, and tool changes are audited as the user.

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