stack/docs/release-integrity/TASKS.md

Tasks — Release Integrity Workstream (RI-050, #1275)

Single-writer: the RI-050 orchestrator (jarvis, dragon-lin) only. Workers read but never modify.

Mission: alpha 0.0.50 release-integrity floor (decisions SDLC-D-033..038). PRD: docs/PRD.md § Release Integrity Workstream Issue: #1275 (remains open until RI-V-001 closes) Base branch: next (all cards branch from origin/next, squash-merge via PR)

Execution note: the agent column uses pi-glm-5.3 — outside the pipeline-cron model table on purpose. This workstream is executed by jarvis on dragon-lin with local pi workers (pi --model zai/glm-5.3:high); pipeline crons must not auto-claim these rows.

Status values: not-started | in-progress | done | blocked | failed | needs-qa done requires: repo quality gates green, independent review recorded, terminal-green CI on the PR head, squash merge to next, and acceptance evidence in notes.

id	status	description	issue	agent	repo	branch	depends_on	estimate	notes
RI-0-001	in-progress	Bootstrap: issue #1275, PRD section, this DAG, scratchpad (docs only)	#1275	pi-glm-5.3	mosaicstack/stack	docs/ri-050-mission-bootstrap	—	6K
RI-1-001	in-progress	RI-N1: canonical terminal verification command + publish-pipeline exact-commit gate (every publish step depends on verify; commit identity check; fail closed)	#1275	pi-glm-5.3	mosaicstack/stack	feat/ri-050-publish-gate	RI-0-001	25K
RI-1-002	not-started	RI-N1 negative control: checked-in tests proving a broken mandatory check blocks every publish step and that DAG edges cannot be bypassed	#1275	pi-glm-5.3	mosaicstack/stack	test/ri-050-publish-gate-negative	RI-1-001	12K
RI-2-001	in-progress	RI-N2 (Forge): remove stub-executor false success; --simulate typed simulated results that satisfy nothing; literal-true gates and echo-review replaced with real gates or typed waiting-for-authority	#1275	pi-glm-5.3	mosaicstack/stack	fix/ri-050-forge-fail-closed	RI-0-001	20K
RI-2-002	not-started	RI-N2 (MACP): gate runner fails closed on empty commands, stub executors, and unimplemented CI-provider gates unless explicit simulate; typed capability failures	#1275	pi-glm-5.3	mosaicstack/stack	fix/ri-050-macp-fail-closed	RI-0-001	15K
RI-3-001	not-started	RI-N4: complete probe inventory mapping every TS and shell quality-rail check to one canonical check with disposition (preserve/strengthen/retire, each named)	#1275	pi-glm-5.3	mosaicstack/stack	docs/ri-050-qr-probe-inventory	RI-0-001	12K
RI-3-002	not-started	RI-N4: TS evaluator absorbs effective shell probes; typed results (passed/failed/blocked/error/not-applicable) with versioned digested check definitions; shell commands become thin adapters; contract/parity/negative-control tests	#1275	pi-glm-5.3	mosaicstack/stack	feat/ri-050-qr-evaluator	RI-3-001	30K
RI-4-001	not-started	RI-N3: one PRD application service — mission --plan persists mission↔PRD linkage (ids/versions/selected requirements); mosaic prdy routes through the service or becomes a named import/export adapter; Markdown is a labeled generated view; explicit conflict-aware import	#1275	pi-glm-5.3	mosaicstack/stack	feat/ri-050-prd-authority	RI-0-001	35K
RI-5-001	not-started	RI-N5: typed freshness states (current/stale/partial/unknown/unavailable); no failed-fetch-renders-empty; stale derived verdicts → unknown; mutations disabled when stale; failure-matrix tests	#1275	pi-glm-5.3	mosaicstack/stack	feat/ri-050-web-stale-safety	RI-0-001	25K
RI-V-001	not-started	Final verification + release evidence: all cards verified merged, negative controls demonstrated, real next publish run green on exact commit, evidence pack recorded	#1275	pi-glm-5.3	mosaicstack/stack	docs/ri-050-release-evidence	RI-1-002, RI-2-001, RI-2-002, RI-3-002, RI-4-001, RI-5-001	10K

Dispatch waves (max 2 parallel workers)

1. RI-1-001 + RI-2-001
2. RI-2-002 + RI-4-001
3. RI-3-001 + RI-5-001
4. RI-1-002 + RI-3-002
5. RI-V-001

Budget

Derived soft cap: 250K tokens (no explicit cap given). Projected total: 190K. Conservative mode (1 worker) above 70% projected; freeze above 90%.