marcopanandClaude Opus 4.8 c9c150c942 docs(plans): piano Harness RPC-readiness + piano Backend ...

Due piani separati (decomposizione concordata): il backend dipende da lavoro
harness non testato (gate RPC-ready, id injection, prereq CLI --json/--offset,
fake-Pi). Piano 1 rende l'harness pilotabile via RPC; Piano 2 costruisce il
backend Node/Fastify testato contro il fake-pi-rpc.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-27 19:26:46 +02:00

..

superpowers

docs(plans): piano Harness RPC-readiness + piano Backend

2026-06-27 19:26:46 +02:00

l2-run-report-2026-06-27.md

test(harness): report L2 cardioversione+ablazione + fix phase show (#2)

2026-06-27 16:14:46 +02:00