Skip to content

Wukong Code v0.0.12

Choose a tag to compare

View all tags
@xxg1413 xxg1413 released this 16 Jul 06:33
v0.0.12
aade6e3

Wukong Code 0.0.12 — Loop until verified

What's Changed

0.0.12 turns Wukong Code from a collection of verification commands into one Loop-first workflow. Give Wukong an objective; it writes, runs the repository's real checks, scans the change, asks a fresh-context read-only reviewer, and continues only when the result is NEEDS_WORK.

One result users can act on

  • PASS — the deterministic gate and reviewer passed; process exit code 0.
  • NEEDS_WORK — the change has actionable blockers or reached its iteration limit; exit code 1.
  • ERROR — Wukong could not produce a trustworthy conclusion; exit code 2.
  • Authentication or quota rejection uses exit code 3; user interruption uses 130.

Each result carries a reason code, compact check results, structured blockers, and a next action. TUI, headless JSON output, SDK snapshots, and persisted Goal records use the same contract.

Stronger delivery gate

  • A single workspace snapshot is shared by verify, scan, and proof.
  • If checks mutate the workspace, Wukong retries once and then returns workspace_changed instead of presenting stale proof.
  • Project-authorized commands in .wukong/checks.json take precedence.
  • Nested npm, pnpm, yarn, and bun packages are discovered and executed in stable order.
  • Source changes without a discovered test/typecheck command return tests_missing; documentation-only changes may continue to review.
  • The reviewer runs with a fresh context and a read-only profile. It cannot override deterministic blockers or edit the workspace.

Free Loop usage

  • Guest: one local Loop trial, up to two iterations.
  • Signed-in Free: 10 Loop sessions per calendar month, up to five iterations per session.
  • A soft Pro-coming-soon message starts with the third monthly session; the hard limit applies after the tenth.
  • Only the top-level Loop counts. Internal verify, scan, and proof checks are never counted separately.
  • Start requests are idempotent, completion records preserve the final three-state result, and temporary quota-service failures fall back to a local five-iteration safety limit.

Role Profiles

Role Profiles are experimental in 0.0.12. Enable experimental.role_profiles, then use wukong roles list, wukong --role <name>, or /transform <name>. A role may narrow tools and change the writer prompt/model; it cannot expand the base permission boundary. Role marketplaces, team synchronization, and a separately selectable reviewer model are not part of this release.

Compatibility

0.0.11 Goal records remain readable. Legacy verify-pass, scan-clean, and judge-pass records and flags are accepted and migrated in memory to proof-pass; original record files are not rewritten. No legacy wire enum is removed in 0.0.12.

Deliberately deferred

  • Hosted Evidence schema v2 and Loop evidence upload
  • --review-model and managed reviewer credits
  • Background/cloud Loop, PR gates, team policies, and billing lifecycle

These remain 0.0.13+ work so 0.0.12 can validate whether users repeatedly use the core Loop before Wukong adds more product surface.

Assets 14
Loading