toga-ai 1.0.986 → 1.0.988

package/knowledge/standalone/apps/claude/workflows/clickup-ticket-workflow.md

@@ -16,6 +16,8 @@ files:
   - claude/agents/ticket-reader.md
   - claude/scripts/hooks/start-gate.js
   - claude/skills/start/scripts/start-helper.js
+  - claude/.claude/settings.json
+  - claude/scripts/install.js
 related:
   - ./ticket-branch-creation-safety.md
   - ./harness-distribution.md
@@ -47,7 +49,9 @@ writes, and agents until the session has a ticket. These replaced `/kickoff`, `/
 4. **`/finish`** — always writes the team KB first. Then one approval list for ticket fields
    (Application, Stakeholders, Task Type, title, Has UI Changes). If the ticket is done: push each
    repo with work, open or update a PR per repo, post a PM comment, set status
-   `development finished`.
+   `development finished`. The PM comment is plain bullets for a non-technical PM: "What
+   changed" always; "Manual steps", "Still open", "Ticket fields changed by Claude" only when
+   they have content. No Apps/Clients/PRs sections. Template: `skills/finish/SKILL.md` Step 15.
 
 ### Ticket branch at /start
 
@@ -73,9 +77,13 @@ writes, and agents until the session has a ticket. These replaced `/kickoff`, `/
 
 - Writes go only to the session's own ticket — the `start-gate` hook blocks any other task id,
   and blocks task creation, deletion, moves, tags, links, docs, chat, and time tracking.
-- `permissions.ask` makes Claude Code ask the developer before every `clickup_update_task`
-  (it cannot be scoped to one argument, so the status change asks too). `clickup_create_comment`
-  posts without a prompt.
+- The `start-gate` hook is the hard limit: session ticket only; fields Application,
+  Stakeholders, Task Type, Pseudocode, Has UI Changes, and the name; statuses `in progress` and
+  `development finished` only.
+- No permission prompt for `clickup_update_task` or `clickup_create_comment` (since 2026-10-09).
+  Field changes are written only after the developer's yes in chat; status changes and the PM
+  comment need no question. Only `Bash(git push *)` stays in `permissions.ask`. `npx toga-ai`
+  strips the old ClickUp rules from a dev's existing `permissions.ask` (see harness distribution).
 - Use only the `clickup` MCP server (`mcp__clickup__clickup_*`). The old read-only
   "claude.ai ClickUP for Dev" server (`mcp__claude_ai_ClickUP_for_Dev__*`) is blocked.
 
@@ -156,6 +164,10 @@ All tested 2026-10-08:
   those, and `create-branch` creates/switches the ticket branch after the dev's yes. (jcardinal)
 - 2026-10-09 — `/start` sets status `to do` -> `in progress`; the gate allows `in progress` and
   `development finished` only. (jcardinal)
+- 2026-10-09 — TRUE-82605: `clickup_update_task` and `clickup_create_comment` no longer ask;
+  the gate is the limit, field changes need the dev's yes in chat. (jcardinal)
+- 2026-10-09 — PM feedback: PM comment is plain bullets for a non-technical PM; Apps, Clients,
+  PRs removed; empty sections left out; field changes as plain sentences with the reason. (jcardinal)
 
 ## Related
 

package/knowledge/standalone/apps/claude/workflows/harness-distribution.md

@@ -6,11 +6,12 @@ project: Claude Harness
 client: shared
 type: workflow
 status: active
-updated: 2026-10-06
+updated: 2026-10-09
 owners: ["jcardinal"]
 files:
   - claude/scripts/install.js
   - claude/knowledge.js
+  - claude/.claude/settings.json
 related:
   - standalone/apps/claude/workflows/knowledge-publish-pipeline.md
 ---
@@ -45,6 +46,12 @@ There are **two copies** of `knowledge.js` on a developer's machine, and the ski
 - **Publish Action (`.github/workflows/publish.yml`, on push to `_main`: bump patch, `npm publish`).** Devs get a change only after a version bump (`/start` runs `npx toga-ai@latest` when installed != latest).
   - `npm publish` **E404** ("could not be found or you do not have permission") = auth failure, not a missing package: the `NPM_TOKEN` secret in the repo's **Actions environment** expired. Fix: new npm Automation token, update the secret, re-run only the latest failed run.
   - A publish ships the whole tip of `_main`, so earlier failed runs are not lost. Do not retry old runs (they hit "version already published").
+- **Removing a permission rule from the shipped `.claude/settings.json` does not remove it from devs.** `mergeSettings()` only adds template rules. To retire one, also list it in `RETIRED_TOGA_PERMISSIONS` (`scripts/install.js`); `npx toga-ai` then filters it out of the dev's existing lists.
+- **Auto mode blocks Claude from editing permission rules in `.claude/settings.json`** ("Self-Modification" safety classifier) — subagents too, even when the lead asked, and no approval prompt is shown. A person makes that one edit by hand; Claude can then do the rest (`install.js`, skill text).
+
+## Change history
+
+- 2026-10-09 — Added permission-retire (`RETIRED_TOGA_PERMISSIONS`) and auto-mode settings-edit gotchas. (jcardinal)
 
 ## Related
 

package/package.json

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

package/skills/finish/SKILL.md

@@ -482,7 +482,7 @@ No session notes at all → under WHY write `not recorded — this work was not
 Never copy a key, token, or password into the body — write `a secret (redacted)` and list it
 under TEAM RULE CHECK.
 
-Keep every PR url for Steps 15 and 17.
+Keep every PR url for Step 17.
 
 **Secret scan** (PR body and PM comment, before posting):
 
@@ -496,19 +496,43 @@ could not be read — fix the path. Never post until it prints `{ok:true}`.
 
 ## Step 15 — PM comment (Claude writes and posts it — no approval)
 
-Draft a short comment for the PM and release notes. Plain words, no code dumps, no secrets,
-no local paths:
+Draft a short comment for a non-technical project manager (also used for release notes):
 
 ```
-**What changed:** <for users/clients, 1-3 plain lines>
-**Apps:** <Application values>
-**Clients:** <Stakeholders values>
-**PRs:** <one url per repo>
-**Manual steps:** <deploy / SQL file + database + order — or "None">
-**Still open:** <anything left — or "Nothing">
-**Ticket fields changed by Claude:** <from Step 10 — or "None">
+**What changed**
+
+- <plain, PM-friendly point>
+- <...>
+
+**Manual steps**
+
+- <plain point>
+
+**Still open**
+
+- <plain point>
+
+**Ticket fields changed by Claude**
+
+- <plain sentence with the reason>
 ```
 
+Rules:
+
+1. **Write for a PM, not a developer.** Say what users or clients will notice, or what the work
+   achieved. No file names, paths, commands, skill names, code terms, code dumps, or secrets.
+2. **Bullets in every section.** One point per bullet.
+3. **Only "What changed" is always there.** Leave out "Manual steps", "Still open", and
+   "Ticket fields changed by Claude" entirely when they have nothing — never write "None".
+4. **Manual steps in plain words** — e.g. "A database update must run before release", not a
+   SQL file name.
+5. **Ticket field changes (from Step 10) as plain sentences with the reason** — e.g. "The Has
+   UI Changes field was unchecked because this task had no UI changes." / "Added TOGa Desk to
+   Application because the work also changed the Desk app."
+6. **No Apps, Clients, or PRs sections.** Apps and clients are in the ticket fields; PRs link
+   to the ticket through the GitHub integration.
+7. **One blank line between sections**, and between a heading and its bullets.
+
 Do not ask the developer to approve it. Write the text to a temp file
 (`toga-comment-<TICKET>.md` in the OS temp dir), run the **Secret scan** on it, delete the
 file. Stop only on a hit. Then post it, and show the posted text in the Step 17 report: