docs(specs): 018 set RC-08 met after the tagged-commit ci re-run

specs/018-v0-3-release-readiness/audit/release-criteria.md

@@ -11,10 +11,11 @@ Written before round 0 (FR-015). Columns are fixed by [contracts/audit-records.m
 | RC-05 | Live beta.8 → RC upgrade with zero data loss and zero lost accounts | SC-005, OD-005 | [inventory.md#upg](inventory.md#upg) | not met (accepted risk, T070) |
 | RC-06 | The baseline snapshot matches the post-cleanup snapshot, with zero `audit018-` resources remaining | SC-006 | [rounds.md](rounds.md), [kubelab-baseline.md](kubelab-baseline.md) | not met (accepted risk, T070) |
 | RC-07 | Every `not-a-defect` and `out-of-scope` closure is justified, and each out-of-scope one cites a roadmap line | SC-009 | [findings.md](findings.md) | partially (accepted risk, T070) |
-| RC-08 | CI is green on the tagged commit | FR-017 | [rounds.md#v030](rounds.md#v030) | pending (the `ci` push run on the tagged commit was cancelled by later merges and is being re-run; the PR head it merges, #587 `23c23401`, passed the full `ci` run) |
+| RC-08 | CI is green on the tagged commit | FR-017 | [rounds.md#v030](rounds.md#v030) | met (`ci` run 37411539484 attempt 2 on `040e10e`: success, T073) |
 
 ## Change log
 
 - 2026-09-24: RC-03 now also counts `imported` findings as blocking, matching data-model.md's blocking statuses. Maintainer decision, OD-010 in [../OPEN-DECISIONS.md](../OPEN-DECISIONS.md#od-010-rc-03-leaves-out-the-imported-status--resolved-2026-09-24).
 - 2026-10-05: `Met` filled at the go/no-go decision (T070, maintainer valgulnecron: go, with Not met criteria accepted as known risk; see [report.md#decision](report.md#decision)). Criteria themselves unchanged.
 - 2026-10-05: RC-01 `Met` unchanged (`not met (accepted risk, T070)`) after OD-030: the maintainer attested that all screens and features were tested live on kubelab on 2026-10-04, and the 459 `untested` WEB/API/CRD/AGT/AUX/HELM/MOD rows are recorded as `pass`, but 8 `UPG`/`NODE` rows and the 16 `INV-SEC-*` rows are still `untested`, so not every row has an outcome. The criterion text is unchanged. Maintainer decision, OD-030 in [../OPEN-DECISIONS.md](../OPEN-DECISIONS.md#od-030-screen-and-feature-rows-recorded-as-pass-from-the-live-sweep--resolved-2026-10-05).
+- 2026-10-06: RC-08 set to `met`: the `ci` push run on the tagged commit `040e10e`, cancelled by later master merges, was re-run (attempt 2, finished 2026-10-06T05:34:05Z) and passed (75 jobs success, 1 skipped). See [rounds.md#v030](rounds.md#v030). Criterion text unchanged.

specs/018-v0-3-release-readiness/audit/report.md

@@ -26,7 +26,7 @@ Evidence as of 2026-10-05. `Met` here is filled only from the records; the maint
 | RC-05 | Live beta.8 → RC upgrade with zero data loss and zero lost accounts | SC-005, OD-005 | **Not met** | The upgrade round has not run (T061, T065). The 5 `UPG` rows are `untested`. CI `e2e-upgrade` from beta.8 exists but is not the live upgrade this criterion asks for. |
 | RC-06 | The baseline snapshot matches the post-cleanup snapshot, with zero `audit018-` resources remaining | SC-006 | **Not met** | No post-cleanup snapshot comparison is recorded. The `audit018-admin` test account is still `pending` removal in [rounds.md](rounds.md), the live sweep's test resources are `not recorded`, and T034 (cleanup) is open. |
 | RC-07 | Every `not-a-defect` and `out-of-scope` closure is justified, and each out-of-scope one cites a roadmap line | SC-009 | **Partially** | Both closures that exist are accounted for: F-276 (`not-a-defect`) carries a Justification citing `web/src/lib/servers.ts:15-16`, and F-181 (`closed-already-fixed`) cites #467. No finding is `out-of-scope`, so no roadmap line is needed yet. Not complete: F-289..F-293 are deferred by #549 (F-289 needs a separate `gameplane-module` PR; F-290..F-293 are design-first items awaiting a Pencil design PR) without an `out-of-scope` closure citing a roadmap line, which SC-009 requires for any deferral. |
-| RC-08 | CI is green on the tagged commit | FR-017 | **Not met** | No `v0.3.0` tag exists. `v0.3.0-rc.2` is not tagged (RC-TAG-2 is PENDING), so there is no tagged commit with a green CI run. `v0.3.0-rc.1` was tagged but its release run was cancelled. |
+| RC-08 | CI is green on the tagged commit | FR-017 | **Not met** | No `v0.3.0` tag exists. `v0.3.0-rc.2` is not tagged (RC-TAG-2 is PENDING), so there is no tagged commit with a green CI run. `v0.3.0-rc.1` was tagged but its release run was cancelled. **Update 2026-10-06 (after the decision):** met. `v0.3.0` was tagged on `040e10e` and its `ci` run passed; see [release-criteria.md](release-criteria.md) and [rounds.md#v030](rounds.md#v030). |
 
 ## Totals
 

specs/018-v0-3-release-readiness/audit/rounds.md

@@ -169,7 +169,7 @@ Release record for the public `v0.3.0` tag (T073). The maintainer chose to skip
 | GitHub release not prerelease | [Release v0.3.0](https://github.com/ValgulNecron/Gameplane/releases/tag/v0.3.0), published 2026-10-06T04:10:51Z: `prerelease: false`, `draft: false`, and it is the repository's latest release. |
 | Notes from `## [0.3.0]` | The release body opens with the `## [0.3.0]` section text of `CHANGELOG.md` at the tag ("The first Gameplane release without a pre-release suffix…"). |
 | `0.3` image tag | `ghcr.io/valgulnecron/gameplane/api` tags `0.3.0`, `v0.3.0`, `0.3` and `latest` all resolve to digest `sha256:ccbe29755dd72fe191f97f0a3bc36e13bd672d6578e659272c9cb0be64198ae3`. |
-| CI on the tagged commit (RC-08) | The `ci` push run on `040e10e` ([37411539484](https://github.com/ValgulNecron/Gameplane/actions/runs/37411539484)) was cancelled by `cancel-in-progress` when later PRs merged into master. The PR head it merges ([#587](https://github.com/ValgulNecron/Gameplane/pull/587), `23c23401`) passed the full `ci` run (19 jobs passed, 0 failed); see RC-08 in [release-criteria.md](release-criteria.md) for the re-run. |
+| CI on the tagged commit (RC-08) | **Green.** The `ci` push run on `040e10e` ([37411539484](https://github.com/ValgulNecron/Gameplane/actions/runs/37411539484)) was first cancelled by `cancel-in-progress` when later PRs merged into master; attempt 2, re-run once master's `ci` was idle, finished 2026-10-06T05:34:05Z with conclusion success (75 jobs success, 1 skipped). |
 
 ### Other tag-triggered workflows