toga-ai 1.0.225 → 1.0.226

package/knowledge/2.0/apps/worker2/INDEX.md

@@ -4,6 +4,7 @@
 |-----|---------|-------|
 | [Worker (worker2) Architecture](architecture.md) | Worker (repo `worker2`) is an AWS Elastic Beanstalk **Worker Tier** application that processes background jobs. | worker2/Controller/Index.php, worker2/Worker/, worker2/LambdaFunctions/, _underscore/Worker.php |
 | [ClickUp Connectivity Watchdog](features/clickup-connectivity-watchdog.md) | A cron watchdog that emails when the ClickUp integration looks disconnected during business hours. | worker2/Worker/Clickup/Health.php, worker2/Database/ClickupHealthWatchdog.sql |
+| [ClickUp GitHub-tab Auto-linking & Ticket-id Branch Naming](features/clickup-github-autolink.md) | How ClickUp surfaces branches/PRs/commits in a ticket's **GitHub tab**, and the branch / PR-title naming convention that triggers it. |  |
 | [ClickUp Project & Opportunity Multi-List Routing](features/clickup-project-routing.md) | Routes ClickUp tasks into the correct **secondary multi-list memberships** based on their custom-field values, via the `clickup` webhook. | worker2/Worker/Clickup/Project.php, worker2/Worker/Clickup.php |
 | [ClickUp Rich-Text Custom Fields via Quill Delta (API)](features/clickup-richtext-api.md) | ClickUp custom text fields (type `text` and long-text) support rich formatting only through a **Quill Delta** written to the undocumented `value_richtext` key o | test/@dave/clickup_md2delta.js, .claude/skills/plan-ticket/scripts/clickup.js |
 | [ClickUp Work Type Automation (Committed / Conditional / Stretch)](features/clickup-work-type-automation.md) | The ClickUp webhook handler (`_Worker_Clickup`) automatically maintains each task's **Work Type** custom field — `Committed`, `Conditional`, or `Stretch` — base | worker2/Worker/Clickup.php, worker2/Tests/Worker/ClickupWorkTypeTest.php |

package/knowledge/2.0/apps/worker2/features/clickup-github-autolink.md

@@ -0,0 +1,44 @@
+---
+title: ClickUp GitHub-tab Auto-linking & Ticket-id Branch Naming
+framework: "2.0"
+repo: worker2
+project: Worker
+client: shared
+type: feature
+status: active
+updated: 2026-06-29
+owners: [dfranks]
+files: []
+related:
+  - ../workflows/ticket-to-pseudocode-planning.md
+---
+
+## Summary
+
+How ClickUp surfaces branches/PRs/commits in a ticket's **GitHub tab**, and the branch /
+PR-title naming convention that triggers it. This is the linkage the `/work-ticket` skill
+depends on when it ships PRs for a planned ticket.
+
+## How it works
+
+- ClickUp's **native GitHub integration** automatically surfaces a branch, PR, or commit in a
+  ticket's GitHub tab **whenever the ticket id appears in the branch name and/or the PR
+  title/body**. The match is on the textual ticket id (e.g. `TRUE-79868`).
+- **There is no ClickUp API call to create this link.** The `plan-ticket/scripts/clickup.js`
+  helper exposes only `get` and `push` (the latter writes the `📝 Pseudocode` field). Linking
+  is purely a side effect of the ticket id appearing in Git metadata.
+- Therefore the durable rule for ticket work: name the **git branch as the BARE ticket id**
+  (e.g. `TRUE-79868`), **one branch per repo**, and include the ticket id in the PR body.
+  PRs default to base branch **`_main`**.
+
+## Branch naming overrides the generic git-workflow rule
+
+⚠ This intentionally **overrides** the generic `feature/<short-description>` type-prefix rule
+in `.claude/rules/toga/common/git-workflow.md` **for ticket-driven work**. The bare ticket-id
+branch name is exactly what ClickUp's native GitHub integration auto-links on, so a
+`feature/…` prefix would break the auto-link. Confirmed against live repos already on
+`TRUE-79142` (worker) and `TRUE-77219` (api2).
+
+## Change history
+
+- 2026-06-29 — Initial doc: ClickUp native GitHub integration auto-links any branch/PR carrying the ticket id (no API call; clickup.js exposes only get/push); convention is bare-ticket-id branch name (one per repo) + ticket id in PR body, base `_main`. Bare-id naming intentionally overrides git-workflow.md's feature/ prefix for ticket work, confirmed from live TRUE-79142 (worker) and TRUE-77219 (api2) branches (dfranks)

package/knowledge/2.0/apps/worker2/workflows/ticket-to-pseudocode-planning.md

@@ -6,13 +6,14 @@ project: Worker
 client: shared
 type: workflow
 status: active
-updated: 2026-06-26
+updated: 2026-06-29
 owners: [dfranks]
 files:
   - test/@dave/clickup_md2delta.js
 related:
   - ../features/clickup-richtext-api.md
   - ../features/talos-meeting-notes-integration.md
+  - ../features/clickup-github-autolink.md
 ---
 
 ## Summary
@@ -55,6 +56,34 @@ under `test/@dave/approach/`):
   **Architecture decision** · **Phases** (each with file paths + pseudocode) · **Testing** ·
   **Risks** · **Owners / open questions** · **Key files**.
 
+## Downstream: plan → work pipeline
+
+Planning is the **first half** of a two-skill pipeline. Once the plan is approved and pushed
+to the ticket's `📝 Pseudocode` field, the **downstream `/work-ticket <TICKET-ID>` skill**
+(also a local skill, not in the team repo) implements it:
+
+1. **Loads the approved plan FROM the ticket's `📝 Pseudocode` field** — the field is the
+   source of truth, not the local `approach/<TICKET>.md`. It reads via
+   `plan-ticket/scripts/clickup.js get <TICKET>`, which returns JSON
+   `{id, custom_id, name, status, description, pseudocodeFieldId, url, fields:{…}}` where
+   `fields` is the non-empty custom fields keyed by display name. The plan is the `fields`
+   entry whose key contains "Pseudocode" (case-insensitive), as plain text. **Stops if empty.**
+2. **Primes framework context** (self-answered `/kickoff`) from the plan's
+   **Repos / Framework / Client** header line.
+3. **Implements phase-by-phase** with implementer subagents (worktree-isolated for independent
+   repos) + TOGA reviewers (php-reviewer / sql-reviewer) looping until clean.
+4. **Per repo in the plan's Repos header:** branch → commit → push, then opens **one PR per
+   repo** with `gh` (default base branch `_main`).
+5. **Reports and STOPS.**
+
+**Autonomy boundary (decided):** `/work-ticket` runs autonomously through PR creation, then
+stops. It **never changes the ClickUp ticket status** — advancing the ticket for approval is
+always a manual developer action, because the developer must review the PR(s) first.
+
+See [ClickUp GitHub-tab auto-linking & ticket-id branch naming](../features/clickup-github-autolink.md)
+for the branch/PR naming convention `/work-ticket` relies on.
+
 ## Change history
 
+- 2026-06-29 — Added the downstream half: `/plan-ticket` → `/work-ticket` pipeline. Records how `/work-ticket` loads the approved plan from the `📝 Pseudocode` field (clickup.js `get` JSON shape, "Pseudocode"-keyed plain-text value), implements phase-by-phase with reviewer loops, branches/commits/PRs per repo, and STOPS at PR creation — never touching ClickUp status (manual gate) (dfranks)
 - 2026-06-26 — Initial doc: ticket→pseudocode planning procedure (ClickUp read → codebase investigation → Talos DevCore grounding → phased plan → approval gate → guarded richtext push); records the shape, not the local skill source (dfranks)

package/knowledge/INDEX.md

@@ -17,7 +17,7 @@ _Auto-generated by `knowledge.js index`. Do not hand-edit._
 ## 2.0 framework
 
 - **_underscore** (_Underscore) _(framework core)_ — 17 doc(s) → [2.0/apps/_underscore/INDEX.md](2.0/apps/_underscore/INDEX.md)
-- **worker2** (Worker) — 20 doc(s) → [2.0/apps/worker2/INDEX.md](2.0/apps/worker2/INDEX.md)
+- **worker2** (Worker) — 21 doc(s) → [2.0/apps/worker2/INDEX.md](2.0/apps/worker2/INDEX.md)
 - **api2** (API) — 7 doc(s) → [2.0/apps/api2/INDEX.md](2.0/apps/api2/INDEX.md)
 - **dbchanges2** (Database Changes) _(framework core)_ — 3 doc(s) → [2.0/apps/dbchanges2/INDEX.md](2.0/apps/dbchanges2/INDEX.md)
 - **toga2-supply** (TOGa Supply) — 3 doc(s) → [2.0/apps/toga2-supply/INDEX.md](2.0/apps/toga2-supply/INDEX.md)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "toga-ai",
-  "version": "1.0.225",
+  "version": "1.0.226",
   "description": "TOGA Technology Team Claude Knowledge System — shared AI coding harness with skills, knowledge base CLI, and project installer for Claude Code.",
   "keywords": [
     "claude",