claim flotilla-core session 0003 (placeholder) + sessions.json entry

flotilla-core/0003/SESSION-0003.0-TRANSCRIPT-2026-06-07T18-58--INPROGRESS.md

@@ -0,0 +1,37 @@
+# Session 0003.0 — Transcript
+
+> App: flotilla-core
+> Start: 2026-06-07T18-58 (PST)
+> Type: planning-and-executing
+> Status: **PLACEHOLDER — claimed at session start; finalized at session end.**
+>
+> This file reserves session ID 0003 for flotilla-core. The driver replaces this
+> body with the full transcript and renames the file to its final
+> SESSION-0003.0-TRANSCRIPT-2026-06-07T18-58--<end>.md form at session end.
+
+## Launch prompt
+
+```
+Patchwatch Phase 2 — sub-project A (Capture), in flotilla-core.
+
+The FOUNDATION of the Patchwatch Phase-2 build order (A → B → sweep → C); B's
+session-start notice and the wgl-remediate skill (both shipped in the plugin) have
+nothing to act on until A files findings as Gitea issues.
+
+Scope per the design (docs/superpowers/specs/2026-06-07-patchwatch-phase2-design.md
+§4.1/§5): add gitea issue create/list/close/label support; a new
+`flotilla-core patchwatch sync <deployment>` reconcile verb (dedup on
+(layer,package,advisory), route to the lockfile-owning repo, accumulate
+affected-deployments, self-heal/auto-close); a bot token with issues:write;
+SPEC.md §12.x "Patchwatch Phase 2" written FIRST; tests against a faked Gitea API.
+
+Resumed via `/goal feedback` follow-on ("go for it") from the plugin session that
+shipped 0.23.0.
+
+```
+
+## Deferred decisions
+
+_Autonomous-mode low-confidence calls the driver made and would have
+liked operator input on. Appended as the session runs; surfaced at
+finalize. Empty if none._

flotilla-core/sessions.json

@@ -4,5 +4,8 @@
   },
   "0002": {
     "title": ""
+  },
+  "0003": {
+    "title": ""
   }
 }