Repository navigation
fix: correct assistant lock order and release validation inputs - #10
Draft
LIghtJUNction wants to merge 12 commits into
Draft
LIghtJUNction wants to merge 12 commits into
LIghtJUNction wants to merge 12 commits into
Conversation
The Alpine smoke probe reaches a healthy installed service, then fails when the container-root observer reads the other UID's procfs executable link. Run that exact read as the existing service UID and GID with no supplementary groups. Keep the executable-path assertion, timeout, error propagation and subsequent native catalogue checks.
The Identity workflow invokes all Core targets without the private evidence roots, acquisition fixtures, pinned historical objects or preserved executors required by those tests. Reuse the established Core protocol setup and retain every test assertion. Execute the payment-live case through its mandatory owning runner, which validates the real parent PID and the exact passing test result. Preserve the job timeout, resource configuration, failure propagation and original failed-run evidence.
The original full Identity run observed a global usage-count change from32 to33 in the store-tristate refusal test. Each earlier successful response can finish before its detached performance write completes. Wait for the existing bounded, request-specific performance sample after each successful stored request and before taking later refusal baselines. Keep every original snapshot, balance, provider-call, and refusal assertion unchanged. The historical extra event's identity remains unknown; its original failure evidence is retained. [skip ci]
LIghtJUNction
force-pushed
the
review/release-fixture-contracts-20261120
branch
from
November 20, 2026 17:57
bbf72df to
fe7f291
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Current status
Draft: the original
bbf72df7Identity gate failed; this PR is not fully qualified. All three original attempt 1 runs are terminal. Their actual checkout is95feb5dd5c7775070de0b11d2b8ae0c4289294f7, binding headbbf72df77a6c144462fc17976a586b4ea4d5b51band base65c7c5c644646535054f82bde2ec291526a53d0b.UPGRADE_DB_OTHER_CLIENT_OR_PREPARED_TRANSACTION. The original A5 kill/restart and store-tristate cases both passed.The Identity log records lib 1,829 passed / 1 failed / 33 ignored, completion upgrade 1 passed / 1 failed, and navigation upgrade 1 passed / 1 failed. It does not identify the conflicting backend/prepared transaction or each exact historical rejection stage. Unrelated autovacuum messages do not establish causation. All original logs and failures remain preserved; no original run was rerun or cancelled manually.
The later three-case diagnostic, control
af783312and product37649a1a, executed each original APP07/completion/navigation case once with 1 PASS / 0 FAIL / 0 ignored. It retained the business assertions and production guard, and checked source stability and disposable PostgreSQL cleanup. This is targeted evidence on that separate source, not a replacement for this failed full Identity gate. The first diagnostic's missing private evidence environment failure remains preserved.The ongoing feature/8e candidate and plugin release work has a separate source lineage and qualification. See the current iteration record. Its component78 and four-case results do not authorize merging or deploying this main/cf candidate.
The release owner's production migration and activation remain blocked by the required real source approvals and financial declarations. This PR has not switched a production service, database or entry point. Terminal evidence was collected by 13:09 UTC; this status correction records those already verified outcomes without starting new jobs.
Why this is needed
The assistant cancellation recovery path had a real lock-order defect. The worker acquired a charging row before the conversation lock, while status polling took the opposite order. PostgreSQL detected a deadlock, and the worker ignored the failed classification transaction, leaving the request in
streaming.The original release checks also exposed missing fixture inputs, evidence ownership errors and snapshot baselines taken before asynchronous performance observations completed. Each correction keeps the existing business assertions and resource budgets.
Changes
78cb1555).508e66ed). Hand back only the three private Native evidence files to the runner before upload, preserving permissions and rejecting symlinks or non-regular files (1c1582cf).73c01b4d).7b0832d3,c3a38f17).e0befd48).d92c9af7). Update the exact required-submodule expectation while preserving strict equality and anti-recursion checks (6a0a0f4f).fe6b6ff1). Keep the real SIGKILL, same-database restart, same-nonce HTTP 409, full snapshot, provider count and balance assertions.bbf72df7). Reuse the read-onlyperformance_samplehelper and its original 3-second bound. Keep every rejection, full snapshot, usage count, funding and provider assertion, and the existing stateless completion barrier.The last two changes affect tests only. The production response completes independently of its spawned performance-recording transaction; reading the body or observing settled request state does not join that transaction. This establishes a missing baseline prerequisite in the test source. It does not identify the extra historical usage-event row.
Latest completed candidate: fe6
All three original runs for head
fe6b6ff1, base65c7c5c6and actual merge checkoutd4c70abe6a9f576f4b46448018315f456751529eare terminal. Their original logs and failures are preserved..dockerignoreinput is absent from the archive and its declared digest remains recorded. The exact fixture script matched the immutabled4c70abesource. No claim is made that all 1,811 input bytes were archived.d4c70abeand successful original build, install/upgrade, real Alpine catalog, evidence handoff and upload steps. Large package ZIPs have API metadata only; their contents were not downloaded for this observation.responses_continuity_independent_store_tristate_and_exact_refusal, at source line 1349. Its full-snapshot comparison observed usage count 32 → 33; the other recorded snapshot fields matched. Lib: 1,829 passed, 1 failed, 33 ignored. Assistant 13/13 and navigation upgrade 2/2 passed. The complete raw log is retained. The additional event's identity is unknown; neither the passing Core job nor the new prerequisite retroactively explains that row.The fe6 Identity failure blocks qualification of that candidate. The new bbf results above must stand on their own.
Earlier evidence retained
37258249; product22c5a510, unchanged source inputs, Rust 1.100 and PostgreSQL 18.6 were verified. This is targeted evidence, not a substitute for the failed fe6 Identity run or the new complete gates.UPGRADE_DB_OTHER_CLIENT_OR_PREPARED_TRANSACTION; the specific client/prepared transaction remains unestablished.be7e13aa. Identity failed the A5 kill/restart snapshot with usage 4 → 5, while the other recorded fields matched. The full log and actual artifact remain preserved; the fifth event is still unidentified. That is distinct from d92's navigation rejection and fe6's store-tristate failure.Source and release boundary
This PR stays on the release owner's 65/cf lineage, with Extore pinned to
cf3469dbe827afcfb2e3f054a63f7b9b7c40bc2b. It does not import the separate shared-state host ABI.The separate 8e feature evidence remains bound to its own sources:
6102f997has verified official packages and an actual 14-check short browser pass; the22c5a510package comparison preserves that browser source distinction. Its original complete feature CI subsequently passed on 22c. The earlier c430 formatting failure is retained. Those results do not qualify this PR's different Go/native ABI.Diagnostic control commits remain on their own branch. Production migration, activation and any release-owner approval remain separate blocked work; no deployment success is claimed here.