jobtrackingapp/docs/redesign/phase-7/p7-09/OWNER_AUTHORIZED_RELEASE.md

# Owner-authorized main promotion — 2026-10-17

**The owner authorized one main promotion despite the recorded NO-GO qualifications. Deployment has been triggered; live deployment is not yet verified.** This authorization does not convert technical release readiness into GO.

The owner first requested a push to main, then explicitly accepted the outstanding NO-GOs/pending items and asked for the completed work to go live. This later decision supersedes the earlier instruction to keep main unchanged for this one promotion. The authorization and exact command are retained in the [portable receipt](evidence/owner-authorized-release.json), with hashed original observations.

## Promoted revision and boundaries

The root agent pushed only the latest completed, already published development commit, **`e7dba9a2f776c55e3c4f4df7ef59076f93fa92df`** (`feat(settings): preserve drafts and connection recovery`), to `refs/heads/main`. The normal push ran **2026-10-17 13:54:33.243078–13:54:35.214338 UTC** and exited 0.

Direct verification at **13:54:35.567674 UTC** recorded local/origin/live main and development HEAD/live development at that revision. Main previously referenced `27657f31131cd95d42f0e1290853ec9c9b3959a4`. Historical statements that main remained at that earlier revision are valid for their recorded observation times; the standing main revision after this promotion is e7dba9a.

The pending import compatibility repair, General lifetime foundation, backend company-create prerequisite, associated tests and unfinished documentation were **excluded**. The recorded working-tree path lists match before and after the push; remote revision equality does not mean the worktree was clean. No unfinished change was committed or included merely to deploy it.

## Deployment observation

Read-only Gitea API observations identify [run 820, number 401](https://git.cesnimda.uk/cesnimda/jobtrackingapp/actions/runs/820), triggered by a main push for the exact e7dba9a revision.

| Observation UTC | Recorded state |
|---|---|
| `13:55:16.507277` | Run 820 `in_progress`, conclusion absent. |
| `13:56:07.968311` | Run still `in_progress`; test job 1699 `in_progress`; deploy job 1700 `waiting`; neither has a conclusion. |

These observations prove the trigger and workflow identity. They do not prove successful deployment, deployed runtime identity, authenticated smoke behavior or production health. The root agent will append the eventual CI/deployment outcome when supported by evidence. This report performs no additional push or deployment action.

## Qualifications remain

The [debt register](../DEBT.md) and [preservation matrix](../PRESERVATION.md) remain authoritative. Production ingress/topology, complete backup/restore, effective schema/configuration, tested rollback, deployed revision/smoke/monitoring and applicable human/device/provider/output qualifications remain open. P5-13 stays withheld; Phase 8 has not started. P7-09's remaining data/privacy/plan/backup work is still pending.

**Technical production readiness: NO-GO qualifications retained. Owner-authorized promotion: pushed. Deployment/live verification: pending.** This was a one-time override for e7dba9a, not authorization to promote later development commits automatically or to mark outstanding requirements complete. Further main promotion needs separate owner authorization and an explicit evidence-based release decision.

## Authorized repair continuation — 20 October 2026

The owner subsequently reported the failed deployment, supplied runner SSH access and explicitly instructed continued investigation and pushes to main. This authorizes coherent release repairs; it does not automatically promote unfinished Phase 7 work or close release qualifications. The specific dev-only braces advisory exception through 31 October 2026 was separately owner-approved. It does not cover other advisories or production dependencies.

Main now references **`cc7977131a4f991578f29d83eec17a242a858fca`**, directly verified against the remote. The chronological repair chain is dependency/audit policy `2278473`, visible browser diagnostics `32bc65c`, approved-route census `f9bf31c`, portable Python fixtures `e5aba4c`, confirmation keyboard scroll `985c719`, shared login-fixture capacity `9234d0a`, and exact notification-caption locator `cc79771`. Each repair has its own infrastructure record, focused verification and normal push. No force push or production database operation was used.

Diagnostic [run 828](https://git.cesnimda.uk/cesnimda/jobtrackingapp/actions/runs/828) passed backend 1054, frontend 824/95 and sidecar 49, then failed its browser lane with **274 passed / 57 failed**. All 57 cases are accounted for: 35 shared-fixture login 429, 15 missing local wrapper in Linux seed fixtures, four nonexact caption queries matching a live announcement, two stale route assertions and one actual scrollable confirmation keyboard barrier. The corresponding targeted fixes preserve assertions, ownership, rate-limit contracts and accessibility checks. Its complete 2,143-entry browser artifact was downloaded and ZIP CRC-checked, SHA256 `e9059617eb3a784de94695b0497227fd1f5f5f1ad10c1e40c9b6019c288c0847`.

The corrected [run 831](https://git.cesnimda.uk/cesnimda/jobtrackingapp/actions/runs/831) is queued behind older runs as of 07:47 UTC. Existing Git-token authentication cannot cancel web-only queued runs through a supported API; no sessions or server records were forged or altered. Deployment, deployed source identity and live smoke remain **unverified**. The last verified healthy live source remains the older `7d641ed` revision. The separately downloaded Qwen 3.5 candidate has not been activated; P5-13 remains withheld.

Development independently published company repair `5addcde` and import prerequisite `3028d81`; neither was silently included in the release. The normal development merge **`36fc5d54e781dcad077c2064edc5c5adef1d4e24`**, pushed and directly verified **07:50:40 UTC**, incorporates the release repairs while preserving every intervening working-file hash. Privacy/usage/backup changes remain a separate unfinished boundary at this observation. Technical production readiness remains NO-GO under the existing operator/manual gates despite explicit owner authorization to deploy the release.