Inventory and registry availability
DA-REL-006 discovers only a bounded data-only artifact descriptor and its exact immutable inputs. Discovery grants no operator capability or private-scope admission; an absent central capability retains normal held behavior.
Public source opt-ins retain their bounded original declarative policy bytes beside the parsed policy and digest at the exact discovered revision. Independent canonical development admission verifies their agreement; older inventory without those bytes remains held until fresh discovery. This adds no private coverage, executable source authority or Maintenance/durable report fields.
src/github.mjs performs authenticated GitHub GETs and public registry reads.
src/policy.mjs selects active manifests, resolves catalog ranges, discovers
runtime cycles and computes eligible stable versions. scripts/inventory.mjs
writes ignored local reports and a gated reconciliation matrix.
Manual empty-attempt recovery may read complete immutable public trees at the originating and explicitly selected current source revisions. A source advance qualifies only when every non-operational blob/commit identity and mode remain equal; documentary/workflow/version-guard/test changes cannot conceal a changed manifest, lockfile, workspace, canonical intake policy or implementation. Unknown or truncated trees remain holds before state publication or consumer writes.
Manual partial-operation reconciliation uses current inventory facts rather than immutable-tree recovery projection. It requires the exact stored operation, state revision and completed originating run, then accepts only qualified advanced public source with complete empty branch/PR/orphan evidence. Inventory records the strict already-satisfied/remaining target partition before ordinary planning independently decides whether a new matrix entry exists.
DA-INV-001 — Revision-bound discovery
Requirement. Inventory MUST discover active workspace manifests at an exact source revision and retain ownership, consumer and portability evidence.
Acceptance details
- The default branch commit MUST be resolved before tree/file reads; explicit notification revisions MAY select a particular source commit for hint verification only; the production graph MUST use current default branches.
- Truncated trees, missing root manifests and duplicate public package owners MUST fail discovery.
- Workspace includes/excludes and catalogs MUST determine active first-party dependency edges.
- Private application manifests MAY be consumers but MUST NOT become public package owners.
DA-INV-002 — Registry authority
Requirement. Registry metadata MUST determine available stable versions; notification payloads MUST NOT authorize a version that the registry cannot qualify.
Acceptance details
- Only HTTP 404 MAY mean unpublished; other registry failures MUST fail the scan.
- Candidates MUST be stable, non-deprecated and no newer than a valid stable
latesttag. - First-party runtime and required peer prerequisites MUST be available recursively until the candidate set converges.
- An optional first-party peer MAY be absent without excluding the candidate.
DA-INV-003 — Portable target eligibility
Requirement. Inventory MUST withhold reconciliation targets whose source cannot support a portable registry update.
Acceptance details
- First-party
link:orfile:dependencies and unpublished external prerequisites MUST hold the consumer. - Required Changesets onboarding and explicit holds MUST be satisfied before inclusion in the matrix.
- The selected rollout phase MUST restrict the matrix, and each consumer MUST pin an exact pnpm version.
- Reports MUST retain blocked reasons rather than describe held consumers as healthy writable targets.
DA-INV-004 — Runtime cycle discovery
Requirement. Inventory MUST identify runtime strongly connected components so already-compatible cyclic dependencies can avoid repeated release bumps.
Acceptance details
- Runtime and optional-runtime edges MUST participate, including internal workspace edges.
- Components with multiple members or a self-edge MUST be reported deterministically.
- Cycle-aware rules MUST use lockfile updates for applicable compatible runtime ranges.
DA-INV-005 — Bounded public source transport
Requirement. Production inventory MUST bind credential-free public source-file reads to the exact Git tree while avoiding file-by-file GitHub API quota.
Acceptance details
- Public visibility, an immutable source revision and the requested tree blob identity MUST be verified before reading source bytes.
- Exact raw bytes MUST reproduce the Git blob SHA; unsafe coordinates, redirects, HTTP failures, oversized responses and mismatches MUST hold discovery without an API fallback.
- Each response MUST retain a 4 MiB bound and 30-second timeout; each repository reader MUST cap requests at256 files and total bytes at16 MiB, without authorization credentials.
- Repeated reads MAY reuse only an invocation-local result for the same revision/path; registry and publication-proof budgets MUST remain unchanged.
DA-INV-006 — Sanitized HTTP failure context
Requirement. HTTP failures MUST retain bounded diagnostic status and quota context without exposing credentials or response bodies.
Acceptance details
- Confirmed quota exhaustion MUST remain distinct from an unclassified permission or HTTP failure.
- Diagnostics MAY retain origin/path, numeric quota/reset/retry values and a bounded request identity; URL credentials, query strings, authorization and response bodies MUST NOT be retained.
- Diagnostics MUST NOT add retries, grant permissions, suppress failed evidence or admit writes.
Operational reports
Before planning writable waves, inventory audits the frozen coordinator graph under DA-OPS-002/003. Denied qualification retains read-only observations but plans with writes disabled and emits no writable target matrix. State-only pilot reporting remains separately gated and available.
The report contains schemaVersion, exact repository source revisions,
manifests, package owners, consumer edges, cycles, eligible versions and
unpublished names. These operational reports remain under ignored reports/
and Actions artifacts; the public specification site does not embed them.
Wave mode additionally reads pnpm lock importers at the exact tree revision via Git blobs (including large lockfiles), registry integrity/dependency contracts, and complete current workflow/check/status evidence. Missing lock or observation coverage remains explicit. Flat mode retains its existing discovery contract.
Qualification collects push and PR workflow contracts separately and observes all current workflow runs/checks/statuses. Branch evidence retains PR/commit authors, exact ancestry and candidate lock data; rerun actors are not owners.
Workflow expectations honor exact changed-path and default-branch trigger filters; non-triggering image/deployment workflows are not invented missing checks, while unknown path coverage remains fail-closed and every observed current workflow still participates in qualification.
Tooling observations follow DA-TOOL-002. Production discovery includes root lock evidence and records the exact source SHA with cohort findings. Those observations neither add update targets nor turn missing evidence into success. Reviewed Node CLI bytes remain distinct from whole-recipe capability. Root Deno formatter declarations are reported as requiring source qualification, not proof that a generic Node-only contract may replace an existing runtime.
Tooling discovery additionally hashes the exact root manifest and lockfile bytes under DA-TOOL-004, so historical cohort CI context remains visibly distinct from changed current source/artifacts and unqualified version recipes.
Completion callbacks settle before the full inventory starts under DA-WAVE-005. Their PR head revisions are verified independently and never passed as graph discovery overrides.
Current public owned versions remain in normalized registry observations even outside latest eligibility under DA-PUB-001/002. Optional-runtime contracts are retained alongside runtime/peer metadata. Production wave inventory collects bounded authenticated public publication evidence; flat selection and the latest-only candidate closure remain unchanged.
Publication artifact reads reuse the existing contents-read workflow token for explicitly public repositories. Inventory requests no App credentials or extra permissions. Missing artifact-read access remains an explicit publication hold; it does not justify widening access automatically.
Canonical-intake opt-ins are bounded declarative JSON read at the exact admitted default-branch source. Their immutable digest and exact chapter paths accompany configuration; no candidate policy or executable module can widen write paths.
Wave inventories retain the unpruned stable candidate pool and a source-policy digest for reviewed channel projection. The normal available pool remains latest-only; path-specific prerequisite closure cannot widen another consumer.
DA-WAVE-009 retains structured originating unpublished/local-path findings beside the existing human constraints. Fresh exact-target discovery reconstructs the same unpublished findings from immutable source and observed registry absence before replanning; matching text cannot grant scope authority. Human summaries retain selected SDK scope and deferred update/hold/wait counts.