diff --git a/docs/agents/records/2026-09-15-minio-compose-ci-image.json b/docs/agents/records/2026-09-15-minio-compose-ci-image.json index 5465671..9646d4c 100644 --- a/docs/agents/records/2026-09-15-minio-compose-ci-image.json +++ b/docs/agents/records/2026-09-15-minio-compose-ci-image.json @@ -16,5 +16,13 @@ ], "base_sha": "c6e1145f4fd7f2d4227b790826963e9e6511c750", "status": "synchronized", - "updated_at": "2026-09-15T17:48:39Z" + "implementation_sha": "4b690715d73d2b328df8534253380af08f4e0e59", + "verification": { + "pr_number": 94, + "pr_head_sha": "322441414c9e2792c56e7d88ef1b0463873b73fb", + "run_id": 35004339067, + "run_conclusion": "success", + "merge_sha": "defec080f925e97ce3bd9b785579817c572d5807" + }, + "updated_at": "2026-09-15T18:02:00Z" } diff --git a/docs/architecture/infrastructure-and-dev.md b/docs/architecture/infrastructure-and-dev.md index 1ae9acb..18e3e90 100644 --- a/docs/architecture/infrastructure-and-dev.md +++ b/docs/architecture/infrastructure-and-dev.md @@ -59,7 +59,9 @@ no longer pull that namespace. `AUTODATA_MINIO_IMAGE` remains an explicit override for a private or provider-managed registry; deployments should use a reviewed immutable release tag or digest rather than `latest`. This registry choice does not change the S3-compatible API, bucket contract, health check, -or secret-management boundary. +or secret-management boundary. The correction was delivered to protected +`master` by PR #94 at `defec080f925e97ce3bd9b785579817c572d5807`; required +verification run `35004339067` passed on the PR head. The Go API uses the same PostgreSQL connection pool for purchaser-facing projection reads and dataset-request status when `AUTODATA_PROJECTION_STORE` diff --git a/docs/public-facing/README-and-wiki.md b/docs/public-facing/README-and-wiki.md index b80597d..644e5b3 100644 --- a/docs/public-facing/README-and-wiki.md +++ b/docs/public-facing/README-and-wiki.md @@ -15,14 +15,14 @@ repository `docs/` tree at the exact verified commit. - **GitHub Project:** [Project #8 — AutoData Portfolio](https://github.com/users/lucronn/projects/8) - **Plan:** [`docs/superpowers/plans/2026-09-11-public-facing-readme-and-wiki.md`](../superpowers/plans/2026-09-11-public-facing-readme-and-wiki.md) - **Machine record:** [`docs/agents/records/2026-09-11-public-facing-readme-and-wiki.json`](../agents/records/2026-09-11-public-facing-readme-and-wiki.json) -- **Status:** `pending merge`: the refreshed README and canonical documentation are pushed on [`automation/knowledge-fallback-runtime`](https://github.com/lucronn/autodata/tree/automation/knowledge-fallback-runtime) and are under review in [PR #94](https://github.com/lucronn/autodata/pull/94). The visual explains the customer problem and solution; all four Wiki pages are published and read back. The default `master` branch will receive the repository-facing changes when PR #94 merges. +- **Status:** `complete`: the refreshed README and canonical documentation are merged into protected `master` by [PR #94](https://github.com/lucronn/autodata/pull/94). The visual explains the customer problem and solution; all four Wiki pages are published and read back. ## Implementation evidence - **README and asset commit:** `3dcef0511ea4bd15ecc30923131c6981f575d44d` -- **Repository-facing verification:** the README/Wiki source work and subsequent release-hardening commits are pushed through merge head `74d5a6c9af9208f47a6a5e96731882e937308a2a`. The required verification passed on the identical implementation tree at `4b690715d73d2b328df8534253380af08f4e0e59`; the merge-head check is rerun by PR #94. +- **Repository-facing verification:** PR #94 merged the synchronized implementation tree into `master` at `defec080f925e97ce3bd9b785579817c572d5807`. Required verification run [35004339067](https://github.com/lucronn/autodata/actions/runs/35004339067) passed on PR head `322441414c9e2792c56e7d88ef1b0463873b73fb`; `master` was read back with the refreshed README and Quay-pinned Compose image. - **Local repository checks:** repository governance `6 passed`; pre-implementation validator `7 passed`; Markdown fence, local-link, secret, and redundant-image checks passed; replacement image inspected at `1942 x 809` PNG. -- **GitHub repository branch:** `automation/knowledge-fallback-runtime` contains the refreshed README, canonical documentation, consumer readiness fixes, and Compose CI image correction. PR #94 is the delivery path into protected `master`. +- **GitHub repository branch:** `automation/knowledge-fallback-runtime` delivered the refreshed README, canonical documentation, consumer readiness fixes, and Compose CI image correction through merged PR #94. Protected `master` is the current delivery branch. - **Wiki status:** GitHub Wiki is initialized and the four requested pages are published and read back: [Home](https://github.com/lucronn/autodata/wiki), [Architecture](https://github.com/lucronn/autodata/wiki/Architecture), [Getting Started](https://github.com/lucronn/autodata/wiki/Getting-Started), and [Contributing](https://github.com/lucronn/autodata/wiki/Contributing). - **Visual message:** scattered repair data becomes one vehicle-specific workspace that produces a procedure, labor-and-parts quote, source evidence, and review status. @@ -47,5 +47,5 @@ The Wiki is published from `docs/wiki/` and must not receive private source payloads, credentials, or claims that exceed the verified local runtime. A generated procedure or source-derived result remains explicitly unreviewed until an authorized human review changes its status. The README and canonical -repository changes remain on the delivery branch until PR #94 is merged into -protected `master`. +repository changes are now on protected `master`; the Wiki remains its +public-facing projection.