Skip to content

Commit 637678e

Browse files
committed
docs: record first release readiness inventory
1 parent 6caeeca commit 637678e

1 file changed

Lines changed: 30 additions & 0 deletions

File tree

‎docs/RELEASE_QUALIFICATION_PLAN.md‎

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,36 @@
22

33
Status: **ACTIVE — supersedes migration-era remaining-work sequencing**
44

5+
## Readiness inventory — 2026-10-01
6+
7+
The assigned readiness worker confirmed through the public GitHub API that
8+
`ngallodev/codebase-memory-cli` is public, `main` points to
9+
`38153854c46f237b700d68b60a65c1a1078c78c5`, the releases collection is empty,
10+
and open PR #12 (`release-tooling`, head
11+
`fd9fbe9c46c214c41e2f176d0278702afa87e4b7`) overlaps release tooling. PR #12 is
12+
an external change under review and must be inspected before any later
13+
implementation overlaps it. The latest 100 public Actions runs contained no
14+
workflow named `Release`; this does not establish private secret or runner
15+
configuration.
16+
17+
The source contract audit confirms that both installers resolve stable bytes
18+
through `/releases/latest/download`, request `checksums.txt`, and map to the
19+
workflow's eight canonical release target tuples. The release workflow requires
20+
successful lint, build, smoke and soak before creating a draft; it holds drafts
21+
for qualification by default. Promotion validates exact release bytes and
22+
source identity, then publishes npm/PyPI before un-drafting GitHub. Therefore a
23+
GitHub-only stable promotion would require a reviewed workflow change; absent
24+
evidence that fork-owned npm/PyPI credentials and namespaces are intended, do
25+
not publish there.
26+
27+
This inventory used unauthenticated public API reads because the worker had no
28+
GitHub CLI login or `GH_TOKEN`/`GITHUB_TOKEN`. Repository secret names, Actions
29+
variables, trusted-publisher configuration, fork scanner access, and runner
30+
availability remain unverified. The CLI graph could not be queried: its cache
31+
resolver returned `secure CLI coordination could not be created (cache-resolve)`
32+
and an isolated `CBM_CACHE_DIR` probe reported a version-cohort conflict. No
33+
repository index or primary checkout was changed by those probes.
34+
535
## Purpose
636

737
The CLI-first migration is architecture-complete enough that remaining work is release qualification, not further MCP migration. Structural changes after this point require evidence from build, reliability, performance, native-Windows, usability, or release validation.

0 commit comments

Comments
 (0)