# AI session release deployment attempt, 2026-09-09

Owner instruction: `lets deploy`, after committing and pushing the session release feature and
GPT-6 Astra catalogue fix to main at `7f3a3cebabd35cc368014a0a4388088d49f5fb19`.

Prepared release `20260909-133534-7f3a3ce` from that exact clean commit. The candidate fingerprint
matched the clean export: `8da05bcede924c2f1541203c2c060f946a03aab7856034ba37f36bb07d90b776`
over 237 files. Renewal guard accepted today's successful renewal. Evidence is under
`D:\fileStorage\tmp\sibyla-deploy\session-ui-20260909-7f3a3ce`.

The unfiltered application suite with Playwright enabled returned **1,059 passed, three failed,
zero skipped**: Platform 551, Browser 161, Argus 236, API 56, TenantIsolation 55 passed / 3 failed.
The failures are Main/Preview migration, table and AI-reader-grant parity. Preview contains these
migrations from the separate, uncommitted Argus work, absent from Main and this release:

- `20260909022515_IntakeEntryReceipt`
- `20260909091919_Stage19ItemNatureInventoryAndRequirements`
- `20260909092951_MatchEvidencePriority`
- `20260909093650_SourceRuleProvenance`
- `20260909101317_FiscalRepeatRulingIdentity`
- `20260909112326_NativeBankStatementPersistence`

The associated Preview-only tables are `bank_statement_receipt`, `intake_entry_receipt` and
`invmov`; the reader role also has their SELECT grants. The in-progress Argus record explicitly
keeps Main migration and its cutover as separate release gates. No unrelated migration was
applied and no Preview object was removed to hide the mismatch.

The deployment WhatIf also exposed a stale rename guard: `DocsPath` still rejected the segment
`GOTT.Sibyla`, although that is now the current repository. Its oracle even listed the same path
as both valid and invalid. The fix rejects `GOTT.Sibyla.Legacy` case-insensitively and permits
the current repository, preserving the purpose of the legacy-source guard. The entrypoint
regression input and oracle follow the actual renamed legacy location.
The full deployment-module suite passed **1,266/1,266** after this fix.

No Execute step ran. Production remains on `20260908-222415-9cbea5d` for web, API and worker.
The release-runner account/configuration has not been installed. A decision on the separate
Argus work is needed before satisfying the remaining parity gate and activating a release.