# Session 0004.0 — Transcript > App: flotilla-core > Start: 2026-06-07T22-20 (PST) > Type: planning-and-executing > Status: **PLACEHOLDER — claimed at session start; finalized at session end.** > > This file reserves session ID 0004 for flotilla-core. The driver replaces this > body with the full transcript and renames the file to its final > SESSION-0004.0-TRANSCRIPT-2026-06-07T22-20--.md form at session end. ## Launch prompt ``` Build deploy-time + retroactive provisioning of the Patchwatch label set across all deployments, integrated with the config-onboarding model. Tracked as flotilla-core issue #10. PROBLEM: `patchwatch sync` files issues with patchwatch/lane/sev labels, but the least-privilege GITEA_ISSUE_TOKEN (0.11.0) cannot create labels (soft-fails 422). On repos whose labels were never created, capture files UNLABELED issues -> breaks dedup-on-resync and surfacing. Bit the first sweep on ben.stull/rfc-app (#36-#40 filed unlabeled). DESIRED: Label provisioning is the DEPLOY identity's job (GITEA_BOT_TOKEN, repo write), keeping capture least-privilege: 1. gitea.py idempotent label APIs (list_labels + create_label/ensure_label) + faked-API tests 2. single taxonomy source derived from patchwatch.issue_labels (patchwatch, patchwatch/lane:*, sev:*) 3. ensure-labels over repos findings ROUTE to (issue_target routing: app_source_repo, wiggleverse/flotilla-core, app main repo for os-layer); idempotent; GITEA_BOT_TOKEN 4. config-onboarding integration: doctor REPORTS missing labels + fix/heal path that CREATES them 5. run at DEPLOY time (idempotent, non-fatal) 6. RETROACTIVE --all sweep across every registered deployment; backfill rfc-app 7. GRACEFUL DEGRADATION where deploy identity lacks repo-admin (ben.stull/*): report, don't fail DISCIPLINE: docs-lead-automation (SPEC §4 + §12.5 + design doc first), TDD vs faked Gitea API, SemVer minor bump + CHANGELOG, branch->PR->merge. Consider capture dedup by body marker (belt-and-suspenders) so correctness no longer DEPENDS on the label. ``` ## 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._