chief-clancy 0.7.4 → 0.8.0

package/src/roles/setup/workflows/init.md

@@ -87,11 +87,16 @@ Which Kanban board are you using?
 [1] Jira
 [2] GitHub Issues
 [3] Linear
-[4] My board isn't listed
+[4] Shortcut
+[5] Notion
+[6] Azure DevOps
+[7] My board isn't listed
 
-If the user selects [4], output the dead-end message and stop:
+Auto-detection hint: silently check `.clancy/.env` for existing board env vars (`JIRA_BASE_URL`, `GITHUB_TOKEN`, `LINEAR_API_KEY`, `SHORTCUT_API_TOKEN`, `NOTION_DATABASE_ID`, `AZDO_ORG`). If detected, show: `Detected: {board} from your env vars. Use this? [Y/n]` — if yes, skip to Q2 for that board.
 
-Clancy currently supports Jira, GitHub Issues, and Linear out of the box.
+If the user selects [7], output the dead-end message and stop:
+
+Clancy currently supports Jira, GitHub Issues, Linear, Shortcut, Notion, and Azure DevOps out of the box.
 
 Your board isn't supported yet — but you can add it:
   · Open an issue:   github.com/Pushedskydiver/clancy/issues
@@ -106,6 +111,32 @@ Do not scaffold anything after this message. Stop completely.
 
 ---
 
+**Shortcut** — ask in this order:
+
+1. `Paste your Shortcut API token: (create one at app.shortcut.com/settings/account/api-tokens)`
+2. `What workflow should Clancy use? (press Enter to auto-detect)` — if blank, auto-detect the first workflow via `GET /api/v3/workflows`
+
+Store as `SHORTCUT_API_TOKEN` and optionally `SHORTCUT_WORKFLOW` in `.clancy/.env`.
+
+**Notion** — ask in this order:
+
+1. `Paste your Notion integration token: (create one at notion.so/my-integrations)`
+2. `What's your Notion database ID? (the 32-character hex string in your database URL)`
+3. `What property name represents the ticket status? [Status]`
+4. `What property name represents the assignee? [Assignee]`
+
+Store as `NOTION_TOKEN`, `NOTION_DATABASE_ID`, and optionally `CLANCY_NOTION_STATUS` and `CLANCY_NOTION_ASSIGNEE` in `.clancy/.env`.
+
+**Azure DevOps** — ask in this order:
+
+1. `What's your Azure DevOps organisation name? (e.g. your-org)`
+2. `What's your Azure DevOps project name?`
+3. `Paste your Azure DevOps personal access token: (needs Work Items Read & Write scope)`
+
+Store as `AZDO_ORG`, `AZDO_PROJECT`, and `AZDO_PAT` in `.clancy/.env`.
+
+---
+
 ### Q2: Board-specific config
 
 Ask each question individually and wait for an answer before moving to the next.
@@ -497,6 +528,47 @@ If `n` or `N`: store `CLANCY_BRANCH_GUARD=false` in `.clancy/.env`.
 
 ---
 
+### Q3i (all boards): Quiet hours
+
+Output:
+
+```
+Pause AFK runs during specific hours? (e.g. business hours, overnight)
+
+[1] Skip — no quiet hours
+[2] Set quiet hours
+```
+
+If [1] or enter: skip — no `CLANCY_QUIET_START` or `CLANCY_QUIET_END` written.
+If [2]: ask:
+
+```
+Quiet start time (HH:MM, 24h format, e.g. 22:00):
+```
+
+Then:
+
+```
+Quiet end time (HH:MM, 24h format, e.g. 06:00):
+```
+
+Store as `CLANCY_QUIET_START` and `CLANCY_QUIET_END` in `.clancy/.env`.
+
+---
+
+### Q3j (all boards): Desktop notifications
+
+Output:
+
+```
+Send desktop notifications when tickets complete or errors occur? [Y/n]
+```
+
+If yes or enter: store `CLANCY_DESKTOP_NOTIFY=true` in `.clancy/.env`.
+If no: store `CLANCY_DESKTOP_NOTIFY=false` in `.clancy/.env`.
+
+---
+
 ### Q4: Base branch (auto-detect)
 
 Silently detect the base branch — do not ask unless detection fails:

package/src/roles/setup/workflows/scaffold.md

@@ -456,6 +456,15 @@ MAX_ITERATIONS=5
 # Prevent accidental commits to the base branch (default: true)
 # CLANCY_BRANCH_GUARD=true
 
+# ─── Optional: Quiet hours ───────────────────────────────────────────────────
+# Pause AFK runs during these hours (24h format). Handles overnight windows.
+# CLANCY_QUIET_START=22:00
+# CLANCY_QUIET_END=06:00
+
+# ─── Optional: Desktop notifications ─────────────────────────────────────────
+# Native OS notifications on ticket completion or error (default: true)
+# CLANCY_DESKTOP_NOTIFY=true
+
 # ─── Optional: Notifications ──────────────────────────────────────────────────
 # Webhook URL for Slack or Teams notifications on ticket completion
 # CLANCY_NOTIFY_WEBHOOK=https://hooks.slack.com/services/your/webhook/url
@@ -563,6 +572,148 @@ MAX_ITERATIONS=20
 
 # ─── Optional: Notifications ──────────────────────────────────────────────────
 # Webhook URL for Slack or Teams notifications on ticket completion
+# ─── Optional: Quiet hours ───────────────────────────────────────────────────
+# CLANCY_QUIET_START=22:00
+# CLANCY_QUIET_END=06:00
+
+# ─── Optional: Desktop notifications ─────────────────────────────────────────
+# CLANCY_DESKTOP_NOTIFY=true
+
+# ─── Optional: Notifications ──────────────────────────────────────────────────
+# CLANCY_NOTIFY_WEBHOOK=https://hooks.slack.com/services/your/webhook/url
+```
+
+### Shortcut
+
+```
+# Clancy — Shortcut configuration
+# Copy this file to .env and fill in your values.
+# Never commit .env to version control.
+
+# ─── Shortcut ────────────────────────────────────────────────────────────────
+SHORTCUT_API_TOKEN=your-api-token
+
+# Optional: workflow name (default: auto-detect first workflow)
+# SHORTCUT_WORKFLOW=Engineering
+
+# ─── Git ──────────────────────────────────────────────────────────────────────
+CLANCY_BASE_BRANCH=main
+
+# ─── Loop ─────────────────────────────────────────────────────────────────────
+MAX_ITERATIONS=5
+
+# ─── Optional: Git host (PR creation) ───────────────────────────────────────
+# GITHUB_TOKEN=ghp_your-token
+# GITLAB_TOKEN=glpat-your-token
+# BITBUCKET_USER=your-username
+# BITBUCKET_TOKEN=your-app-password
+
+# ─── Optional: Pipeline labels ────────────────────────────────────────────────
+# CLANCY_LABEL_BRIEF="clancy:brief"
+# CLANCY_LABEL_PLAN="clancy:plan"
+# CLANCY_LABEL_BUILD="clancy:build"
+
+# ─── Optional: Status transitions ────────────────────────────────────────────
+# CLANCY_STATUS_IN_PROGRESS="In Progress"
+# CLANCY_STATUS_DONE="Done"
+# CLANCY_STATUS_REVIEW="In Review"
+
+# ─── Optional: Quiet hours ───────────────────────────────────────────────────
+# CLANCY_QUIET_START=22:00
+# CLANCY_QUIET_END=06:00
+
+# ─── Optional: Desktop notifications ─────────────────────────────────────────
+# CLANCY_DESKTOP_NOTIFY=true
+
+# ─── Optional: Notifications ──────────────────────────────────────────────────
+# CLANCY_NOTIFY_WEBHOOK=https://hooks.slack.com/services/your/webhook/url
+```
+
+### Notion
+
+```
+# Clancy — Notion configuration
+# Copy this file to .env and fill in your values.
+# Never commit .env to version control.
+
+# ─── Notion ──────────────────────────────────────────────────────────────────
+NOTION_TOKEN=your-integration-token
+NOTION_DATABASE_ID=your-database-id-32-char-hex
+
+# Optional: property name overrides (defaults shown)
+# CLANCY_NOTION_STATUS=Status
+# CLANCY_NOTION_ASSIGNEE=Assignee
+
+# ─── Git ──────────────────────────────────────────────────────────────────────
+CLANCY_BASE_BRANCH=main
+
+# ─── Loop ─────────────────────────────────────────────────────────────────────
+MAX_ITERATIONS=5
+
+# ─── Optional: Git host (PR creation) ───────────────────────────────────────
+# GITHUB_TOKEN=ghp_your-token
+# GITLAB_TOKEN=glpat-your-token
+# BITBUCKET_USER=your-username
+# BITBUCKET_TOKEN=your-app-password
+
+# ─── Optional: Pipeline labels ────────────────────────────────────────────────
+# CLANCY_LABEL_BRIEF="clancy:brief"
+# CLANCY_LABEL_PLAN="clancy:plan"
+# CLANCY_LABEL_BUILD="clancy:build"
+
+# ─── Optional: Quiet hours ───────────────────────────────────────────────────
+# CLANCY_QUIET_START=22:00
+# CLANCY_QUIET_END=06:00
+
+# ─── Optional: Desktop notifications ─────────────────────────────────────────
+# CLANCY_DESKTOP_NOTIFY=true
+
+# ─── Optional: Notifications ──────────────────────────────────────────────────
+# CLANCY_NOTIFY_WEBHOOK=https://hooks.slack.com/services/your/webhook/url
+```
+
+### Azure DevOps
+
+```
+# Clancy — Azure DevOps configuration
+# Copy this file to .env and fill in your values.
+# Never commit .env to version control.
+
+# ─── Azure DevOps ────────────────────────────────────────────────────────────
+AZDO_ORG=your-organisation
+AZDO_PROJECT=your-project
+AZDO_PAT=your-personal-access-token
+
+# ─── Git ──────────────────────────────────────────────────────────────────────
+CLANCY_BASE_BRANCH=main
+
+# ─── Loop ─────────────────────────────────────────────────────────────────────
+MAX_ITERATIONS=5
+
+# ─── Optional: Git host (PR creation) ───────────────────────────────────────
+# GITHUB_TOKEN=ghp_your-token
+# GITLAB_TOKEN=glpat-your-token
+# BITBUCKET_USER=your-username
+# BITBUCKET_TOKEN=your-app-password
+
+# ─── Optional: Pipeline labels ────────────────────────────────────────────────
+# CLANCY_LABEL_BRIEF="clancy:brief"
+# CLANCY_LABEL_PLAN="clancy:plan"
+# CLANCY_LABEL_BUILD="clancy:build"
+
+# ─── Optional: Status transitions ────────────────────────────────────────────
+# CLANCY_STATUS_IN_PROGRESS="Active"
+# CLANCY_STATUS_DONE="Closed"
+# CLANCY_STATUS_REVIEW="Resolved"
+
+# ─── Optional: Quiet hours ───────────────────────────────────────────────────
+# CLANCY_QUIET_START=22:00
+# CLANCY_QUIET_END=06:00
+
+# ─── Optional: Desktop notifications ─────────────────────────────────────────
+# CLANCY_DESKTOP_NOTIFY=true
+
+# ─── Optional: Notifications ──────────────────────────────────────────────────
 # CLANCY_NOTIFY_WEBHOOK=https://hooks.slack.com/services/your/webhook/url
 ```
 
@@ -681,6 +832,13 @@ MAX_ITERATIONS=20
 # Set to "false" to disable skip comments
 # CLANCY_SKIP_COMMENTS=true
 
+# ─── Optional: Quiet hours ───────────────────────────────────────────────────
+# CLANCY_QUIET_START=22:00
+# CLANCY_QUIET_END=06:00
+
+# ─── Optional: Desktop notifications ─────────────────────────────────────────
+# CLANCY_DESKTOP_NOTIFY=true
+
 # ─── Optional: Notifications ──────────────────────────────────────────────────
 # Webhook URL for Slack or Teams notifications on ticket completion
 # CLANCY_NOTIFY_WEBHOOK=https://hooks.slack.com/services/your/webhook/url

package/src/roles/setup/workflows/settings.md

@@ -35,6 +35,9 @@ Source `.clancy/.env` silently. Detect which board is configured:
 - `JIRA_BASE_URL` set → Jira
 - `GITHUB_TOKEN` set → GitHub Issues
 - `LINEAR_API_KEY` set → Linear
+- `SHORTCUT_API_TOKEN` set → Shortcut
+- `NOTION_DATABASE_ID` set → Notion
+- `AZDO_ORG` set → Azure DevOps
 
 ---
 
@@ -58,6 +61,8 @@ General
   [G7] Fix retries        {CLANCY_FIX_RETRIES:-2}          self-healing attempts after verification failure
   [G8] Time limit         {CLANCY_TIME_LIMIT:-30}          per-ticket time limit in minutes (0 = disabled)
   [G9] Branch guard       {on if CLANCY_BRANCH_GUARD=true or unset, off if false}
+  [G10] Quiet hours       {CLANCY_QUIET_START–CLANCY_QUIET_END if set, else off}
+  [G11] Desktop notify    {on if CLANCY_DESKTOP_NOTIFY=true or unset, off if false}
 
 {If Jira:}
 Jira
@@ -113,7 +118,7 @@ Integrations
   [I2] Playwright        {enabled if PLAYWRIGHT_ENABLED=true, else off}
   [I3] Notifications     {configured if CLANCY_NOTIFY_WEBHOOK set, else not set}
 
-  [S]  Switch board      currently: {Jira / GitHub Issues / Linear}
+  [S]  Switch board      currently: {Jira / GitHub Issues / Linear / Shortcut / Notion / Azure DevOps}
   [D]  Save as defaults  save current settings for all future projects
   [X]  Exit
 
@@ -278,6 +283,37 @@ If [2]: write `CLANCY_BRANCH_GUARD=false` to `.clancy/.env`.
 
 ---
 
+### [G10] Quiet hours
+
+```
+Quiet hours — current: {CLANCY_QUIET_START–CLANCY_QUIET_END or "off"}
+Pause AFK runs during these hours. Clancy sleeps until the end of the quiet window.
+
+[1] Set quiet hours
+[2] Off (no quiet hours)
+[3] Cancel
+```
+
+If [1]: prompt `Quiet start time (HH:MM, 24h format):` then `Quiet end time (HH:MM, 24h format):`. Validate HH:MM format (0-23:00-59). Write `CLANCY_QUIET_START` and `CLANCY_QUIET_END` to `.clancy/.env`.
+If [2]: remove `CLANCY_QUIET_START` and `CLANCY_QUIET_END` from `.clancy/.env`.
+
+---
+
+### [G11] Desktop notifications
+
+```
+Desktop notifications — current: {on/off}
+Native OS notifications when tickets complete or errors occur.
+
+[1] Enable (default)
+[2] Disable
+```
+
+If [1]: write `CLANCY_DESKTOP_NOTIFY=true` to `.clancy/.env`.
+If [2]: write `CLANCY_DESKTOP_NOTIFY=false` to `.clancy/.env`.
+
+---
+
 ### [B1] Jira status filter (Jira only)
 
 ```
@@ -739,17 +775,18 @@ If [2]: remove `CLANCY_NOTIFY_WEBHOOK` from `.clancy/.env`.
 
 ### [S] Switch board
 
-Show which board is currently active, then offer the other two:
+Show which board is currently active, then offer the others:
 
 ```
-Switch board — currently: {Jira / GitHub Issues / Linear}
+Switch board — currently: {Jira / GitHub Issues / Linear / Shortcut / Notion / Azure DevOps}
 
 [1] {board A}
 [2] {board B}
-[3] Cancel
+...
+[N] Cancel
 ```
 
-Only show the two boards that are not currently active. If the user picks Cancel, loop back to the menu without changing anything.
+Only show the boards that are not currently active. If the user picks Cancel, loop back to the menu without changing anything.
 
 **Step 1: Collect new credentials**
 
@@ -775,6 +812,21 @@ Linear — ask in this order:
 1. `Paste your Linear API key: (create one at linear.app/settings/api)`
 2. `What's your Linear team ID? (find it at linear.app/settings/teams — click your team, copy the ID from the URL)`
 
+Shortcut — ask in this order:
+1. `Paste your Shortcut API token: (create one at app.shortcut.com/settings/account/api-tokens)`
+2. `What workflow should Clancy use? (press Enter to auto-detect)`
+
+Notion — ask in this order:
+1. `Paste your Notion integration token: (create one at notion.so/my-integrations)`
+2. `What's your Notion database ID? (32-character hex string from your database URL)`
+3. `Status property name? [Status]`
+4. `Assignee property name? [Assignee]`
+
+Azure DevOps — ask in this order:
+1. `What's your Azure DevOps organisation name?`
+2. `What's your project name?`
+3. `Paste your Azure DevOps personal access token: (needs Work Items Read & Write scope)`
+
 **Step 2: Verify credentials**
 
 Verify the new credentials before making any changes — same checks as the init preflight and doctor workflow. Show the result:
@@ -814,6 +866,9 @@ If no: print `Cancelled. No changes made.` and loop back to the menu.
    - Jira: `JIRA_BASE_URL`, `JIRA_USER`, `JIRA_API_TOKEN`, `JIRA_PROJECT_KEY`, `CLANCY_JQL_STATUS`, `CLANCY_JQL_SPRINT`
    - GitHub: `GITHUB_TOKEN`, `GITHUB_REPO`
    - Linear: `LINEAR_API_KEY`, `LINEAR_TEAM_ID`
+   - Shortcut: `SHORTCUT_API_TOKEN`, `SHORTCUT_WORKFLOW`
+   - Notion: `NOTION_TOKEN`, `NOTION_DATABASE_ID`, `CLANCY_NOTION_STATUS`, `CLANCY_NOTION_ASSIGNEE`, `CLANCY_NOTION_LABELS`, `CLANCY_NOTION_PARENT`
+   - Azure DevOps: `AZDO_ORG`, `AZDO_PROJECT`, `AZDO_PAT`
    - Git host (all boards): `GITLAB_TOKEN`, `BITBUCKET_USER`, `BITBUCKET_TOKEN`, `CLANCY_GIT_PLATFORM`, `CLANCY_GIT_API_URL`, `CLANCY_STATUS_REVIEW`
 2. Write the new board credentials to `.clancy/.env`
 3. If switching to Jira: also ask the status filter question (same as init Q3) and write `CLANCY_JQL_STATUS` to `.clancy/.env`

package/src/roles/setup/workflows/update.md

@@ -161,9 +161,45 @@ This touches:
 It never modifies:
 - `.clancy/docs/` — codebase documentation
 - `.clancy/progress.txt` — progress log
-- `.clancy/.env` — credentials
 - `CLAUDE.md`
 
+It may **append** to:
+- `.clancy/.env` — adds missing env var defaults (see Step 4a)
+
+---
+
+## Step 4a — Backfill missing env var defaults
+
+After the installer finishes, read `.clancy/.env` and check for missing pipeline label variables. These were introduced in v0.7.4 and won't exist in `.env` files from earlier installs.
+
+**Check for and append if missing:**
+
+```
+# Pipeline labels (added in v0.7.4)
+CLANCY_LABEL_BRIEF=clancy:brief
+CLANCY_LABEL_PLAN=clancy:plan
+CLANCY_LABEL_BUILD=clancy:build
+```
+
+For each variable:
+1. Read `.clancy/.env` content
+2. If the variable name does NOT appear anywhere in the file (not even commented out), append it with its default value
+3. If the variable already exists (even with a different value), leave it untouched
+
+Add a blank line and a `# Pipeline labels (added in v0.7.4)` comment header before the new variables, but only if at least one variable was added.
+
+**Display what was added (if any):**
+```
+📋 Added missing env var defaults to .clancy/.env:
+   CLANCY_LABEL_BRIEF=clancy:brief
+   CLANCY_LABEL_PLAN=clancy:plan
+   CLANCY_LABEL_BUILD=clancy:build
+
+   Customise these via /clancy:settings → L1/L2/L3
+```
+
+If nothing was added, display nothing.
+
 ---
 
 ## Step 5 — Check for local patches

package/src/roles/strategist/workflows/approve-brief.md

@@ -218,10 +218,11 @@ Platform-specific pre-creation lookups.
 
 ### GitHub
 
-**Pipeline label for children:** Determine the pipeline label based on planner role and flags:
-- `--skip-plan` flag → `CLANCY_LABEL_BUILD` (default: `clancy:build`)
-- Planner role enabled (`CLANCY_ROLES` includes `planner`) → `CLANCY_LABEL_PLAN` (default: `clancy:plan`)
-- Planner role NOT enabled → `CLANCY_LABEL_BUILD` (default: `clancy:build`)
+**Pipeline label for children — this is mandatory, always apply a pipeline label to every child ticket.** Determine which label to use:
+- `--skip-plan` flag → use `CLANCY_LABEL_BUILD` from `.clancy/.env` if set, otherwise `clancy:build`
+- Planner role enabled (`CLANCY_ROLES` includes `planner`) → use `CLANCY_LABEL_PLAN` from `.clancy/.env` if set, otherwise `clancy:plan`
+- Planner role NOT enabled → use `CLANCY_LABEL_BUILD` from `.clancy/.env` if set, otherwise `clancy:build`
+Ensure the label exists on the board (create it if missing), then add it to each child ticket.
 
 **Labels to apply per ticket:**
 - The pipeline label determined above (`CLANCY_LABEL_PLAN` or `CLANCY_LABEL_BUILD`) — replaces `CLANCY_LABEL` on children
@@ -272,9 +273,9 @@ Set CLANCY_BRIEF_ISSUE_TYPE in .clancy/.env.
 ```
 Stop.
 
-**Pipeline label for children:** Same logic as GitHub — determine the pipeline label from `--skip-plan` flag and planner role.
+**Pipeline label for children — mandatory, same logic as GitHub.** Use `CLANCY_LABEL_PLAN` or `CLANCY_LABEL_BUILD` from `.clancy/.env` (defaults: `clancy:plan` / `clancy:build`). Always apply to every child ticket.
 
-**Labels:** Jira auto-creates labels — no pre-creation needed. Apply: the pipeline label (`CLANCY_LABEL_PLAN` or `CLANCY_LABEL_BUILD`), `clancy:afk` or `clancy:hitl`. `CLANCY_LABEL` is NOT applied to children when pipeline labels are active.
+**Labels:** Jira auto-creates labels — no pre-creation needed. Apply: the pipeline label determined above, `clancy:afk` or `clancy:hitl`. `CLANCY_LABEL` is NOT applied to children when pipeline labels are active.
 
 **Components:** If `CLANCY_COMPONENT` is set, it maps to the Jira `components` field.
 
@@ -305,7 +306,7 @@ query {
 }
 ```
 
-**Pipeline label for children:** Same logic as GitHub/Jira — determine the pipeline label from `--skip-plan` flag and planner role.
+**Pipeline label for children — mandatory, same logic as GitHub/Jira.** Use `CLANCY_LABEL_PLAN` or `CLANCY_LABEL_BUILD` from `.clancy/.env` (defaults: `clancy:plan` / `clancy:build`). Always apply to every child ticket.
 
 For each required label (the pipeline label, `component:{CLANCY_COMPONENT}`, `clancy:afk`, `clancy:hitl`): search by exact name. `CLANCY_LABEL` is NOT applied to children when pipeline labels are active. If not found in team labels, check workspace labels:
 
@@ -643,9 +644,9 @@ Created by Clancy on {YYYY-MM-DD}.
 
 ## Step 11a — Remove brief label from parent
 
-Only if a parent ticket exists AND all tickets were created successfully. Remove `CLANCY_LABEL_BRIEF` from the parent ticket. Best-effort — warn on failure, never stop.
+Only if a parent ticket exists AND all tickets were created successfully. Remove the brief label from the parent ticket. Best-effort — warn on failure, never stop.
 
-Read `CLANCY_LABEL_BRIEF` from `.clancy/.env`. Default: `clancy:brief`.
+Use `CLANCY_LABEL_BRIEF` from `.clancy/.env` if set, otherwise `clancy:brief`.
 
 ### GitHub
 

package/src/roles/strategist/workflows/brief.md

@@ -621,7 +621,7 @@ Continue — do not stop. The local file is the source of truth.
 
 Only for board-sourced briefs (ticket key was provided). Inline text and file briefs skip this step.
 
-Read `CLANCY_LABEL_BRIEF` from `.clancy/.env`. Default: `clancy:brief`. Read `CLANCY_LABEL_PLAN` and `CLANCY_LABEL_BUILD` for cleanup during re-briefs.
+**This step is mandatory for board-sourced briefs — always apply the label.** Use `CLANCY_LABEL_BRIEF` from `.clancy/.env` if set. If not set, use `clancy:brief` as the default. Ensure the label exists on the board (create it if missing), then add it to the ticket. Also read `CLANCY_LABEL_PLAN` (default: `clancy:plan`) and `CLANCY_LABEL_BUILD` (default: `clancy:build`) for cleanup during re-briefs.
 
 ### Re-brief cleanup (`--fresh` flag)