# Post-rename verification — 2026-09-09 Checked `main` at `c054b7c`. The folder/repository rename checks passed. Regression failures found during the initial check were investigated and fixed in the working tree; verification is below. **Follow-up:** the investigation and fixes below supersede the initial regression status. - GitLab `origin` points to `gottsolutions.dev/sibyla/GOTT.Sibyla.git`; remote HEAD and main match the local commit. Only the primary worktree is registered. The legacy clone points to `gott-sibyla-legacy.git`. - IIS serves current documentation from `GOTT.Sibyla/docs` and legacy documentation from `GOTT.Sibyla.Legacy/docs`. Web and both documentation roots return HTTP 200. API `/health` and `/health/ready` return 200. `/health/live` is not a route in this API. - Web, API and the running document worker use release `20260908-222415-9cbea5d`; their CURRENT pointers agree. No scheduled-task action referencing `GOTT.Apollo` was found. - Active source/script search found only the intentionally retained deployment mutex and its tests/oracles outside migrations and historic evidence. Deployment preparation defaults use the new folder and scratch paths; both default destinations are absent. Offline preparation safety checks pass. - Corrected five stale repository paths in the extraction operator guide. Historic evidence and frozen compatibility identifiers were preserved. ## Validation `local/test.ps1` rebuilt the solution with Playwright enabled. API 56, TenantIsolation 58, Platform 543 and Argus 236 passed (893 total); migration parity passed. The command then exited on the browser test `AdministratorApolloTurnPersistsAndResumesWithTheSameLicenceProfile` reporting failure. PowerShell's native stderr handling interrupted complete failure capture. A separate full Browser run with TRX output completed: **156 passed, 1 failed, 0 skipped**. `UploadsFiltersAndReviewDialogWorkInBothLanguagesAndViewports` failed after an unhandled Blazor circuit exception and a disconnected SignalR send. The Apollo test passed in this run. A focused run of both named tests then passed **2/2**. This is intermittent behavior with an undetermined cause, not a green full-suite result or a proven rename regression. Logs: `%TEMP%/sibyla-rename-validation.log`; `%TEMP%/sibyla-rename-tests/rename-browser.trx` and `rename-focused.trx`. No production configuration, deployment, migration or real document was changed by this check. `git diff --check` passed. ## Next work First capture the server-side exception and diagnose the intermittent browser failures, then obtain a fresh complete passing validation run. The next feature slice is the extraction specification's section 6 persistence hand-off: resolve header/lines/bank movements, repeat the fiscal duplicate guard on corrected values before entry, persist through the governed FDR write path, and provide line/movement correction grids. Establish the tenant's cutover status first: `DocumentCaptureService.RegisterAsync` currently refuses an owner with sync runs; the spec requires cutover or an owner-ruled sync-era exception. Freeze the fresh end-to-end acceptance set and criteria under `persistence-acceptance-decision-260908.md` before using the set. The September 4 project status map is historical and should not override later deployment and data-carry-over rulings. ## Regression investigation and fixes The concurrent full solution run reproduced the Apollo failure as `Subscription missing`. The fake harness completed and the registry removed its live subscription before the test attached. The fake now waits for explicit release after subscription; both turns still assert completion, licence/profile identity, consent and resumed session identity. Runtime registry behavior was not changed. Server-error capture exposed the Uploads circuit failure: `ListFilteredAsync` continued during navigation after its scoped `SibylaDbContext` was disposed. Uploads now cancels reads and queued refreshes on disposal, handles cancellation/disposal only after component teardown, and keeps controls busy through the initial list and company reads. Active-component failures still surface. The test harness now appends server errors to failed Uploads assertions. A subsequent full run exposed an immediate focus assertion after closing the re-extraction dialog. Dialog removal precedes JavaScript focus restoration. View, Review and re-extraction checks now wait for the original required focus target using Playwright's retrying assertion; no focus or browser-error assertion was removed. An additional channel-form save timeout and a Playwright injected hit-target error appeared during diagnosis. Neither justified a speculative channel implementation or browser-package change. Both were absent from the later complete passing run. The complete concurrent solution run `validation-focus` passed **1,050/1,050**, with zero failures/skips (Platform 543, Argus 236, Browser 157, API 56, TenantIsolation 58), Playwright enabled. Final cancellation cleanup, initial-load busy coverage and the View focus assertion were then completed. The final Browser rebuild passed **157/157**, zero failures/skips, recorded in `%TEMP%/sibyla-regression/final-browser.trx`. No assertion was skipped or suite serialized to obtain these results. `git diff --check` and the UI mechanical detector passed. ## Persistence start `argus-persistence-slice-260909.md` defines the implementation sequence, unresolved transactional handoff, duplicate/retry requirements and proposed 24-document sealed acceptance matrix. A read-only Main query confirmed 52 NP Group sync runs. Its existing C6 guard remains intact; development is scoped to an isolated Preview tenant. No new acceptance sources were opened, no production cutover was performed. The subsequent first implementation checkpoint adds an internal atomic fiscal writer and Preview-only receipt migration; see the persistence slice document for its test evidence, remaining resolver work and Main/Preview parity release gate.