DEV Evidence / Blocker Aggregator

This is the lightweight report-only entry point for pikasTech/HWLAB#41 and the M5 DEV gate aggregator v2 for pikasTech/HWLAB#58. It helps a commander decide whether the DEV acceptance path is green, blocked, or ready for another repair round across #33-#39, #46, #7, and the MVP DoD in #9.

Run from the repository root:

node scripts/dev-evidence-blocker-aggregator.mjs --pretty

For a short validation response:

node scripts/dev-evidence-blocker-aggregator.mjs --check

To refresh the committed v2 machine and human reports:

node scripts/dev-evidence-blocker-aggregator.mjs --write-report

The generated files are:

reports/dev-gate/dev-m5-gate-aggregator-v2.json
reports/dev-gate/dev-m5-gate-aggregator-v2.md

Source Levels

The aggregator keeps evidence levels separate so fixture output cannot be promoted to live DEV evidence:

Level	Meaning
`SOURCE`	Repository contracts, schemas, docs, manifests, or examples.
`LOCAL`	Localhost or in-process smoke results only.
`DRY-RUN`	Fixture-backed or no-mutation dry-run readiness evidence.
`DEV-LIVE`	Read-only evidence observed from the real DEV route.
`BLOCKED`	Missing issue reads, missing DEV evidence, missing artifacts, or other open blockers.

Current Contract Map

Milestone	Current visible level	Contract entry
M0	`SOURCE`	`docs/m0-contract-audit.md`, protocol schemas, evidence chain examples, M0 validator.
M1	`LOCAL`	`docs/m1-local-smoke.md`, `fixtures/mvp/runtime.json`, `scripts/m1-contract-smoke.mjs`.
M2	`DRY-RUN`	DEV deploy smoke fixture, artifact catalog, runtime boundary, and M2 dry-run validator.
M3	`LOCAL`	Hardware trusted loop topology fixture and local patch-panel smoke.
M4	`LOCAL`	Agent automation loop fixture, local runtime skeleton, skills commit, evidence, and cleanup smoke.
M5	`DRY-RUN`	MVP e2e dry-run plan and orchestration validator.

Blocker Posture

The v2 report reads committed report fixtures only:

reports/dev-gate/dev-preflight-report.json
reports/dev-gate/dev-deploy-report.json
reports/dev-gate/dev-artifacts.json
reports/dev-gate/dev-edge-health.json
reports/dev-gate/dev-m3-hardware-loop.json
reports/dev-gate/dev-m4-agent-loop.json
reports/dev-gate/dev-mvp-gate-report.json
reports/d601-k3s-readonly-observability.json

The report is blocked until real DEV-LIVE evidence is attached for the DEV route and downstream HWLAB runtime services. Current source, local, and dry-run contracts are useful readiness signals, but they are not live DEV proof.

Next-Round Order

The JSON output groups recommended next actions in dependency order:

base-image: preload or tag an approved Node 20 DEV builder image, then rerun the base-image and artifact publish preflights.
artifact-publish, artifact-catalog, ghcr: publish every frozen HWLAB service artifact and record immutable registry digests for the selected origin/main commit.
d601-k3s, kubectl, kubeconfig/maintenance bridge: restore read-only hwlab-dev cluster observability without printing Secrets.
cloud-api-db: prove DEV cloud-api DB env and health readiness with redacted values only.
dev-edge, dev-edge-health, dev-ingress-health: repair :6667/frp/edge/router reachability, then rerun read-only DEV edge health before M3/M4/M5 live loops.

Boundaries

The aggregator does not deploy, call DEV, call PROD, run browser tests, run heavy e2e, read secrets, restart services, or replace HWLAB runtime services with UniDesk services. It is a local report generator and static contract checker only.

3.7 KiB Raw Blame History