docs: record final P1 acceptance evidence

This commit is contained in:
2026-08-09 23:39:07 +02:00
parent 0cfe5c7c9a
commit 87ee55a35f
+19 -9
View File
@@ -5,23 +5,33 @@
## P1 configuration-process automated integration — PASS 2026-08-09
- Retained evidence: `.artifacts/p1-integration/p1-57d5f3b1e420f348f849943f9ee6227c/report.md`
- Retained evidence: `.artifacts/p1-integration/p1-2f5d861d1151121ad7cc3edb69cf3abb/report.md`
- automated integration: PASS
- manual acceptance: PENDING
- The retained run is bound to clean source commit
`0cfe5c7c9a4e6dcd395ec32135b5e4999311432b` and tree
`ad6fcfedb2ca1e8d3c16ec632618aaf2e1bbd78f`. Its hash-bound provenance contains exact
43-file backend source and 39-file compiled `dist` manifests (manifest SHA-256
`2188379320f93f4e24205d418ead9dd25b48ed93da663fcf7e3e6e835931c2bc` and
`9f9e8899f8aca882ff08d49ec6cd00caeea75691c8280095a9b88bc74939a30a`).
- The retained audit has exactly 15 PASS checks and 134 unique declared artifacts whose final
bytes match every SHA-256 declaration. It records 749 PASS command events and 1,664 production
child/network events (831 STARTED, 831 PASS, and the two expected FAIL terminals), with no
rejected surface event. Git runs with fixed safe configuration, an owned empty hooks directory,
exact local config/attribute/hook validation, and a fail-closed invocation grammar.
- The contextual negatives use a separate `invalid-context` branch, remote, checkout, data,
runtime, registry, and second production Fastify listener, all beneath the owned run root.
Persisted before/after semantic-state proofs show primary `main` remains valid, a missing-tree
publish is state-neutral, and an invalid pull advances only its disposable checkout while the
remote and last-valid active/snapshot/data/runtime state remain unchanged.
- The retained audit has 132 unique declared artifacts whose final bytes match every SHA-256
declaration. It records canonical Git, Python lock-holder, and `tht` children under bounded
process/environment policy, both production listeners closed, and no rejected child/network
surface events. The in-capture reachable-object scan covered all four expected repositories
(156 objects, 48 blobs) with zero findings; the frozen final filesystem and virtual-report scan
also found no fixture canaries outside the excluded secret fixture directory.
- The hash-bound final ownership artifact records both production listeners closed with refused
connection checks. Independent final probes found both ports refused and PID 80568 dead. The
reachable-object scan covered all four expected repositories (156 objects, 48 blobs) with zero
fixture-secret findings; the frozen final filesystem scan covered 600 non-fixture regular files,
found no symlinks, and found no fixture-secret values.
- Final report hashes: `report.json`
`dfe4b2f9d7bf0b9cce114ca93239e2b87e0b87f5719504d74ed2c437763c817c`;
`report.md` `4f45aaedfc4f6399ab5ab6ebab5764055a243daae16227a29ce16d32b8ee0fa7`.
`268099f89dc203589eae35172b217e88d5f7603281157d78ae9e67ec5f792eda`;
`report.md` `f771aaed585c3b628768484338efedb133fae856840d72aa5ba41a675e81816f`.
## Internal Qdrant + Ollama semantic infrastructure — LIVE 2026-08-08