Record successful native Vergabe capture preflight
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 2s

Assistant: codex
Assistant-Model: gpt-6.1-sol
Assistant-Session: 01a1abf1-7e95-7141-87c9-ee78332bf790
This commit is contained in:
tegwick 2026-11-06 00:23:15 +01:00
parent 8975e3b106
commit 8fd2c9772d
4 changed files with 74 additions and 17 deletions

View file

@ -0,0 +1,34 @@
{
"schema": "railiance.vergabe-pilot-capture-preflight.v1",
"reported_on": "2026-11-06",
"observed_at": null,
"evidence_kind": "user_reported_terminal_output",
"workplan": "RAPPS-WP-0014",
"task": "RAPPS-WP-0014-T03",
"command": "python3 tools/vergabe_pilot_snapshot_remote.py --check",
"source_revision": "8975e3b106542f99c503cd5e0aa26b88b0c78976",
"status": "ready_for_capture_review",
"runtime_mutations": false,
"helm_revision": 4,
"fixture": {
"active_members": 2,
"oidc_identities": 2,
"fixture_present": true,
"document_sha256": "23a6850fa2391a58280c8515361ca29e9e92fa65fdadc36be7b44b552192e381",
"document_bytes": 803,
"local_state_header_valid": true
},
"anonymous_document_denied": true,
"anonymous_http_status": 302,
"helper_server_dry_run": true,
"migration_check_passed": true,
"review": {
"document_matches_repository_fixture": true,
"capture_executed": false,
"pause_approved_by_this_return": false,
"populated_restart_verified": false,
"off_host_verified": false,
"restore_verified": false,
"next": "Founder-approved short pause, matched PostgreSQL/media/SQLite capture and guarded resume using the prepared --execute command."
}
}

View file

@ -4,7 +4,13 @@ RAPPS-WP-0014-T03. The November 5 native inventory passed at Helm revision 4.
This packet prepares one coherent recovery point for the populated pilot.
[Scope and source pins](plan.json) · [synthetic validation](validation.json).
## Next step: live checks without a pause
## Live checks without a pause — passed November 6
The founder's [native return](../../evidence/2026-11-06-vergabe-capture-preflight-return.json)
reports `ready_for_capture_review`: both members/identities, fixture, matching
803-byte PDF, anonymous-download denial, migration check and reader server
dry-run pass. No pause or capture was performed. The next step is the prepared
capture below, after the founder's go. The check command remains reproducible:
From the founder's workstation checkout, in the founder's own terminal:
@ -25,7 +31,7 @@ Pod through Kubernetes **server dry-run**, without creating it. It checks 1 GiB
free for bounded private artifacts. It prints only counts, hashes and status.
It does not read Secret objects or output personal identifiers/file paths.
Expected result: `status: ready_for_capture_review`. Return that JSON for review.
Expected result: `status: ready_for_capture_review`.
The check does not change replicas, create a Pod, create backup files or restore
data. A failed check stops before any capture mutation.

View file

@ -7,8 +7,10 @@ The user also confirmed Ausschreibung/Anforderung creation and visibility from
the other account after reload; see the [workflow return](evidence/2026-11-05-vergabe-shared-workflow.json).
The user confirmed the uploaded file is available from the other account; see
the [document return](evidence/2026-11-05-vergabe-document-return.json). The
document UI still needs user review. File hash equality and signed-out download
refusal are unverified. The user also confirms the **LOKAL** issue badge is
document UI still needs user review. The November 6 native check verifies the
stored file matches the original PDF checksum and its anonymous binary URL
redirects to login. A second-account downloaded-file hash comparison remains
unreported. The user also confirms the **LOKAL** issue badge is
visible in both accounts; the [issue return](evidence/2026-11-05-vergabe-local-issue-return.json)
binds Ausschreibung 1, task 1 and document 1 from their supplied URLs. The user
now confirms cross-account task editing and the flow through documented
@ -19,9 +21,12 @@ below remain the reproduction sequence for the populated restart/restore drill.
The founder's [November 5 native inventory](evidence/2026-11-05-vergabe-native-inventory-return.json)
passes at Helm revision 4 with the expected healthy deployment/database and both
Bound claims. The next step is the read-only native capture check in the
[three-store recovery packet](proposals/2026-11-06-vergabe-three-store-capture/README.md).
Its synthetic restore validation does not satisfy the pilot recovery gate.
Bound claims. The [November 6 capture check](evidence/2026-11-06-vergabe-capture-preflight-return.json)
also passes: two active members and OIDC identities, fixture 1/1/1, matching file,
valid local-state header, anonymous download denial, no pending migrations and
the reader Pod server dry-run. Next is the founder-approved pause/capture/resume
in the [three-store recovery packet](proposals/2026-11-06-vergabe-three-store-capture/README.md).
Neither preflight nor synthetic validation satisfies the pilot recovery gate.
The other session does not update automatically, and a fresh login was needed
after a short interval. The user wants a full working day without renewed login
@ -82,14 +87,13 @@ the collaborative workflow are distinct verdicts.
## Recovery follow-through
The [read-only preflight](evidence/2026-11-05-vergabe-pilot-preflight.json)
confirms the recorded cluster UID, public health and the NetKingdom welcome
gate. Node, Deployment and PVC reads are forbidden to the current agent identity;
fresh image/release/claim status remains unverified. The binding's expected image
and claims are historical reference values until a permitted native readback.
The [native inventory packet](proposals/2026-11-05-vergabe-recovery-preflight/README.md)
now provides the exact metadata-only action; its current-caller receipt remains
incomplete. It prepares the baseline read, rather than a snapshot or restart.
The earlier [agent preflight](evidence/2026-11-05-vergabe-pilot-preflight.json)
could not read native node, Deployment and PVC status. The founder's subsequent
[native inventory](evidence/2026-11-05-vergabe-native-inventory-return.json) and
[capture preflight](evidence/2026-11-06-vergabe-capture-preflight-return.json)
clear that blocker at Helm revision 4. They use the founder's own terminal and
existing SSH/sudo lane; the agent receives only sanitized receipts. Native
capture and restart have not run.
After the populated workflow, prepare the exact attended recovery action from
the existing [pilot recovery contract](vergabe-teilnahme-pilot.md#persistence-and-recovery)
@ -118,7 +122,8 @@ and [deployment binding](vergabe-demo-company-binding.md). Its receipt must cove
Existing database-only backup/restore targets default to historical `vergabe_db`
and omit both file stores. They cannot establish this three-store recovery claim.
The two-account functional walkthrough is user-confirmed with UI follow-up.
The attended restart,
off-host capture, isolated restore and rollback action has not been prepared or executed.
The attended capture/restart action is prepared and its live preflight passes;
execution awaits the founder's go. Off-host publication, isolated native restore
and rollback remain outstanding.
Logged-in account deactivation remains a separate owner-run access-control check
from the pilot contract. No account is disabled as part of these walkthrough steps.

View file

@ -390,6 +390,18 @@ founder's go for the exact pause/capture/resume. No native pause/capture has run
Off-host readback, native isolated restore/rollback, access and operating-owner
acceptance remain open. T03 remains waiting.
2026-11-06 native capture preflight return: `ready_for_capture_review` at Helm
revision 4. Two active members and two OIDC identities, fixture 1/1/1, local-state
header, migration check and reader Pod server dry-run pass. The stored document
is the repository's 803-byte PDF (SHA256 `23a6850f…192e381`), and its actual
anonymous binary URL returns a login redirect (302). Receipt:
`docs/evidence/2026-11-06-vergabe-capture-preflight-return.json`. This clears the
live preflight gate. The return is not approval to pause; the concrete reviewed
`--execute` action awaits the founder's go for the short pause, matched capture
and guarded resume. No capture or populated restart has executed. T03 remains
waiting for that action and subsequent off-host/restore/rollback, access and
operating-owner acceptance.
## Validate synthetic sizing against the exact release and shared contention