Additive API registration slice

Source: main coordination and authoritative minimal-spec6766f99. Delivery base is the live API source26d95f46ada7cc03e2b7906858878b6fe2b7be81 (selfhost-20261110T022821Z), not later main. Owned branch codex/solve-pair-api-registration in t2-dev:/home/eric/wt-solve-pair-api-registration. Original divergent main untouched.

Runtime delta: packages/shared/src/agent-browser.ts only. Strict new visible-only browser_create_solve_pair schema takes UUIDv4 client operation and enum production/staging; exact URL mapping feeds existing origin admission. No new API route, migration, dependency, environment variable, secret, native OS grant or server entitlement. Existing API catalogue derives input/control/risky=false registration from shared browser schema. Existing createCommand and assertBundleCommand still require agent-browser flag, surface, current linked consent, requester/lease, origin and generation checks. They are not loosened. The slice test imports actual catalogue/service validators; it does not claim a database-backed consent/routing test.

Old native desktop does not support newkind and must refuse without a Solve pair allocation. Registration is only relay compatibility, never UI completion. Native signed app and separately reviewed Solve cookie endpoints/assets remain release dependencies. Final native action release guard lives in desktop, not this slice.

Failure first: baseline source-only actual validator suite8tests ran2missing-command/origin assertion failures and6unknown-kind rejection passes; after additive schema8pass. New UUIDv4 case must pass before commit. No global database setup needed for this narrow source-only suite.

Validation: pnpm --filter @bugtracker/api exec vitest run --config vitest.solve-registration.config.ts; git diff --check. Before deployment require independent exactHEAD review plus existing release preflight and staged real API checks of denied actor/no consent/expired generation/foreign origin and route to an old desktop yielding safe unsupported refusal. No migration or endpoint write added. Main owns the actual staging deployment command and canary.

Release order: reviewed Solve staging schema+endpoints; additive API staging registration and negative routing checks; signed native candidate integration; native staging clicks. Production API slice can canary separately only after main approval, preserving source identity and prior image pointer26d95f46 for rollback. Verify deployed /version and real validator behavior. Roll back on auth/consent regression, queue/result errors or unsupported refusal with side effects by restoring previous API image; queued newkind commands remain safe unsupported refusals under old native and should not be replayed as new operations. Do not promote unrelated main changes or report full feature ready from registration alone.

Observed real-service validation: root executed one passwordless socket-only PostgreSQL cluster/DB and actual127.0.0.1 API HTTP listener. Migration exited0 and4/4 cases passed: missing/expired consent; wrong actor/mapped origin; malformed/hidden/caller phrase input; valid queue/native-consumer exclusion/desktop next/stale generation. Existing bootstrap initially failed before assertions because temporary postgres and entrypoint psql used different socket defaults; root reconciled the SAME verified container and cluster, then completed the run. This infrastructure NO_RESULT is not counted as a code failure or a passing test. Exact container ID+purpose cleanup stopped/removed only solve-api-http-01a1c3fd; private data and logs retained. No provider/browser/device action occurred. Evidence: /home/eric/.agent-harness/work/solve-api-http-01a1c3fd/{manifest.json,socket-proof.txt,migrate.log,service-test.log}.

Observed service source SHA256s, unchanged through execution and commit: machines-solve-service.test.ts7dc1caf53a42f836af8415b10bff3b48b9fd4094297d842096a09321b984be9e; solve-service-db-target.tsc39e6e605479722e1337a095895de4db1f01806c793bf53a9b9d971b1fc1e608; solve-service-db-target.unit.test.ts252e0cfcfa5a3ff510162d8e083ce3addb2c1ac9dba5b6d72ff73211277f72c8; vitest.solve-service.config.ts733b4e7da1329b8922e0656b341593b05b710113ce06b9e04999719f50b14efd; vitest.solve-registration.config.ts28c145560b996a127d142b2feb317b210dd7396b409361d715e33f48c852ebf6. Source-only validator+DB-target guard suite18passed. Final independent exactHEAD PR review and staged/live relay deployment checks remain pending. Installed old desktop delivery is a postdeploy check; static refusal analysis and real service queue proof do not replace it.

We use essential cookies to keep you signed in. See our Privacy Policy for details.