cesnimda
3.4 KiB
Patched-source integrated run — 21 October
This is investigation evidence, not final acceptance. The ordinary351-case run started05:32:57UTC against patched entry, with zero configured retries. It was explicitly stopped05:55:08UTC after144passing and3failing logged cases; passing partial output does not establish a passing suite. Raw hashes and the subsequent bounded repair preserve the distinction between this failed attempt and successor verification.
Reproduced SQLite failures
The ordinary Audit persistence case77 again receives500 from GET /api/jobapplications/328 after successful owned Restore. Captured API output now identifies Microsoft.Data.Sqlite.SqliteException, SQLite error5 (database is locked), propagated through AiUsageMeter.ReserveAsync line65, MeteredSummarizerService.MeterAsync line75 and JobApplicationsController.GetById line656. The request failed in12ms. This supersedes the earlier absence of a server stack; it does not establish the competing lock holder or justify an untested retry.
The ordinary application-form locale case93 also fails its unchanged expected204 assertion: PUT /api/auth/preferences/language returns500 in5ms with the same SQLite error5. The affected behavior is therefore broader than AI metering. Further diagnosis must preserve quota accounting, persistence, tenant filters and the original browser assertions. A passing isolated rerun cannot close this intermittent issue.
Raw evidence remains in .artifacts/phase7/current/ui/main.log and each failed case's retained trace under main-results. The completed report must record their final archived locations and hashes. A cancelled earlier workspace request also logged500; that is distinct from the two client-observed assertion failures above.
Users fixture pagination
Case85 reaches the two mobile samples, then cannot find its created long identity at the768px desktop sample. The retained accessibility snapshot shows a populated, alphabetically ordered desktop grid, not a failed user load. The desktop component intentionally pages10rows; earlier suites have created enough users to place the target outside the first page. The isolated3-case vector did not exercise that population.
The correction must navigate the existing grid to the actual target before asserting its visible identity and keyboard/reflow behavior. It must not remove pagination, reduce fixture populations, weaken the visibility assertion, delete accounts or change administrative authorization.
Release remains separate
Main 5f835e54a9b74e6b71418422e28431b2af06453f was normally pushed. Its CI838 test job1727 failed before deployment: Node20.20.1/Jest exited139 on both the initial command and its pre-existing retry. Matching host core metadata identifies Node processes1057260 at05:38:21UTC and1066375 at05:42:23UTC. The job finished failed05:42:38UTC; deployment job1728 was skipped.
This follows separately captured Python and .NET native crashes. The shared runner's cause remains unproven; readable core metadata does not establish a hardware diagnosis. Raw CI/host observations are retained under .artifacts/phase7/p7-09/instrumented-release-ci/20261021T054421Z/. No additional retry or failed-check bypass is introduced. Live release identity and the requested Ollama activation remain unverified/pending. Production readiness stays NO-GO.