Step 0 Spike Test
Validate the full L3 planning stage by producing a plan artifact for the Step 0 spike test item, confirming end-to-end pipeline API connectivity.
Operator approved with 'Spike test approval' - plan is scoped to pipeline validation only, not real implementation work, consistent with the step-0 spike test purpose.
Verify that GET /queue, GET /item/{id}, POST /artifact, and POST /advance all return 2xx responses from within the field-notes cloud environment. No code changes required - this step is a connectivity and auth check using the existing ?token= parameter pattern.
app/api/scan/github-trending/route.tsDocument that pipeline item 1 traversed L1 Curate -> L2 Assess -> L3 Plan without errors. Confirm the pipeline_items and pipeline_artifacts tables in Taproot Postgres contain the expected rows (id=1, stages assess and plan, both artifacts written).
app/api/scan/github-trending/route.tsPipeline item 1 is in plan_ready stage after this routine completes
A plan artifact exists in pipeline_artifacts for item 1 at stage='plan'
GET /item/1 returns artifacts for both stage='assess' and stage='plan'
L4 Execute CCR can be triggered manually against item 1 to complete the full pipeline smoke test
Spike test item has no real GitHub repo or enrichment data - L4 Execute must handle test items gracefully and not attempt real code changes
The assess artifact for this item is minimal (fit: high, notes: spike test artifact) - L4 Execute should detect the test context and produce a stub output rather than real implementation
Spike test approval