docs(auth): correct Task 14 release status
This commit is contained in:
+8
-4
@@ -7,7 +7,8 @@
|
||||
> ThothII per il repository (app + CLI `thothctl`), (3) come usare l'applicazione ThothII di base
|
||||
> (sessioni, domande, gate). Il documento userà parole semplici ed esempi; i dettagli tecnici
|
||||
> resteranno nei contratti esistenti. Esempio pratico completo: Policlinico San Donato.
|
||||
Last updated: 2026-08-13 (P2–P6 accepted; P7 live preprocessing PASS on PSD).
|
||||
> Last updated: 2026-08-18 (Task 14 documentation implemented; strict documentation and
|
||||
> authentication release gates remain blocking or pending as listed below).
|
||||
> Point a fresh session here ("read PROJECT_STATE.md") before substantial work.
|
||||
|
||||
### Task 14 authentication documentation — implementation status (2026-08-18)
|
||||
@@ -16,9 +17,12 @@
|
||||
revision invalidation, generic OIDC direct groups claims, exact group-role mapping, Authentik
|
||||
group-view-only catalog checks, tht auth/tht doctor ordering, diagnostics, CSRF, and restore
|
||||
reauthentication.
|
||||
- Task 14 documentation smoke and strict documentation build are release evidence for the docs
|
||||
scope only. Browser OIDC callback E2E, native Windows behavioral execution, PSD/manual test
|
||||
identities, and external L2 remain pending Task 15/release gates.
|
||||
- The Task 14 authentication-documentation smoke passes. The MkDocs `--strict` baseline remains a
|
||||
blocking release gate: it exits 1 with 69 warnings, the same warning count before and after Task
|
||||
14. It is not a PASS or release evidence.
|
||||
- Browser OIDC callback E2E, native Windows behavioral execution, PSD/manual test identities, and
|
||||
external L2 remain pending Task 15/release gates. Task 14 documentation is implemented, not
|
||||
release-accepted.
|
||||
- Task 13 has two parked restore-lock preconditions that remain mandatory before certification:
|
||||
lock before target-dependent preflight with archive bytes/hashes staged and revalidated inside the
|
||||
lock immediately before extraction; and an opaque installation-bound transaction capability or
|
||||
|
||||
Reference in New Issue
Block a user