docs(skills): record finalization load gate

This commit is contained in:
Jinwoo-H
2026-08-12 06:33:34 -04:00
parent 1a7272aa67
commit dcc8e19069
2 changed files with 43 additions and 11 deletions
@@ -134,12 +134,33 @@ Validated so far:
- Guarded sleep `31580339694` returned staging to low cost. Independent reads verified Cloud SQL
`NEVER`/`STOPPED`, C1/C2/C3 target size zero and stable, and API/Auth min scale zero. Production
was not touched.
- Cloud PRs `#332` through `#335` added the staging-only 12-by-30 finalization load gate, narrowly
authorized its OIDC identity, fixed deterministic fixture ordering, and made retry settlement
cleanup-safe. Their merge commits were `ac85d0690e`, `53559bd644`, `7e1d50a84b`, and
`bb8bf8b9ac`; merged-main verification passed through run `31586525326`.
- Auth deploy `31584318896` promoted `orca-cloud-auth-staging-00021-tuq` with digest
`sha256:e17075d69dca36df427f02fa515481f359c8f67397c5ab16de9759f7f949c6be`; candidate and
canonical smoke passed with one 100%-traffic revision and no remaining candidate tag.
- Load run `31585710645` exercised 12 concurrent bundles with 30 skills and 3,949,317 extracted
bytes each. Two finalized immediately and ten returned explicit saturation; client p95 was
1,514 ms. Aggregate utilization stayed bounded: request p95 1,401.06 ms, API CPU 8.95%, API
memory 26.95%, one API instance, database CPU 10.89%, database memory 25.59%, and seven
connections. A saved, exact one-add Terraform plan restored the declared
`roles/monitoring.viewer` binding for the staging deploy identity before those aggregate metrics
were read; it changed no service, traffic, SQL, storage, Relay, or production resource.
- Cleanup run `31586684354` removed the exact failed-wave package set through normal package DELETE
routes. The two remaining quarantine archives were manifest-proven as 30-skill fixtures for
suffix `013756ec4740` and deleted with exact GCS generation preconditions; no live object from
that run window remained. GCS soft delete keeps the operation recoverable.
- Guarded sleep `31587083752` returned staging to low cost. Independent reads verified Cloud SQL
`NEVER`/`STOPPED`, C1/C2/C3 target size zero and stable with no current actions, and API, Auth,
and Relay active-revision minimums at zero. Production was not touched.
Rollout gate: staging infrastructure, OIDC owner identity exchange, anonymous bearer lifecycle,
owner management, browser-free desktop bundle lifecycle, privacy-safe logging, published-object
recovery, and guarded rollback-capable deployment passed. The shared staging data plane is back in
its low-cost asleep state. Production remains untouched; final remote physical-host staging
journeys, bounded finalization load, and quarantine lifecycle deletion remain.
recovery, bounded finalization load, and guarded rollback-capable deployment passed. Production
remains untouched, and the shared staging data plane is asleep; final remote physical-host staging
journeys and quarantine lifecycle deletion remain.
Source plan: [Agent skill sharing and installation plan](./agent-skill-sharing-installation-plan.md).
@@ -1204,8 +1225,11 @@ still require the listed split metrics, latency panels, and alerts.
Cloud Run platform request logs through Terraform and verify zero are retained.
- [ ] Verify logs, metrics, traces, diagnostics, and support bundles contain no grants or private
package data.
- [ ] Load-test finalization and choose the fixed semaphore from observed memory, CPU, request
latency, and database usage.
- [x] Load-test finalization and choose the fixed semaphore from observed memory, CPU, request
latency, and database usage. Run `31585710645` kept the existing semaphore: its 12 concurrent
30-skill bundles produced two immediate successes and ten explicit saturation responses,
1,514 ms client p95, 8.95% API CPU, 26.95% API memory, one API instance, 10.89% database CPU,
25.59% database memory, and seven database connections.
- [ ] Exercise at least one quarantine lifecycle deletion and published-object soft-delete
recovery. Published-object recovery passed run `31580071168`; the one-day quarantine
lifecycle deletion remains time-gated.
+14 -6
View File
@@ -55,14 +55,16 @@ that larger package-manager surface.
The Orca implementation is on `skills-share` at `38012f06c1`; no Orca pull request exists. Cloud
bundle ingestion and bearer-link work merged through `stablyai/orca-cloud#320` as `0579cc1a71`;
the bundle desktop smoke update merged through `#329` as `eddb144afe`, and generation-aware GCS
recovery merged through `#330` as `8045c85dad`.
the bundle desktop smoke update merged through `#329` as `eddb144afe`, generation-aware GCS
recovery merged through `#330` as `8045c85dad`, and the bounded finalization load gate plus cleanup
hardening merged through `#332`-`#335` as `bb8bf8b9ac`.
The authenticated OIDC smoke landed in `#313`; the narrow Auth release-metadata convergence
follow-up landed in `#314`; the finalization and lifecycle fixes landed in `#317`. The final
anonymous bearer-link candidate and canonical smoke now pass in staging. Production remains
untouched. Local, Windows, WSL, paired-runtime, Docker-backed SSH, browser-free staging desktop,
and published-object recovery validation are substantially complete; the implementation checklist
records the exact evidence and remaining physical-host, load, and lifecycle gates.
published-object recovery, and bounded finalization-load validation are substantially complete;
the implementation checklist records the exact evidence and remaining physical-host and lifecycle
gates.
The local redesign now has an independently implemented Agent Plugins 1.0.0 skills-only bundle
manifest, deterministic one-or-many archive creation, bounded bundle extraction, additive bundle
@@ -127,8 +129,14 @@ Cloud PR `#330` merged as `8045c85dad`; deploy `31579844413` promoted revision
`orca-cloud-api-staging-00057-kat`, and recovery smoke `31580071168` proved generation-aware GCS
soft-delete restoration, transactional reference repointing, bearer download, and cleanup.
Guarded sleep `31580339694` restored SQL to `NEVER`/`STOPPED` and all Relay MIG targets to zero.
Remaining staging gates are remote physical-host journeys, bounded finalization load, and the
time-gated quarantine lifecycle deletion.
Load run `31585710645` then exercised 12 concurrent 30-skill bundles at roughly 3.95 MiB extracted
per bundle. Explicit saturation bounded ten requests while two completed; API, Cloud SQL, instance,
and latency metrics stayed far below their reviewed thresholds. PR `#335` made retry settlement
cleanup-safe, and run `31586684354` removed the exact failed-wave package set before two
manifest-proven quarantine generations were deleted with GCS preconditions. Guarded sleep
`31587083752` then returned SQL to `NEVER`/`STOPPED`, all three stable Relay MIGs to zero, and every
active Cloud Run revision minimum to zero. Remaining staging gates are remote physical-host
journeys and the time-gated quarantine lifecycle deletion.
## Research baseline