devflow-kit 2.4.0 → 2.5.0

package/dist/skills/git/references/tracker/github/gather-release-evidence.md

@@ -0,0 +1,19 @@
+## Operation: gather-release-evidence
+
+Load when the resolved tracker provider is `github` and the operation is `gather-release-evidence`.
+
+**Mechanics held here:** the last release tag, the closing-keyword rule, this provider's history grammar, resolving which issues the range's merged PRs close — one listing, with its bounded fallback — and the trace map.
+
+### Process
+
+1a. **Last release tag.** Step 1's `git describe` can return a non-release marker tag. From `WORKTREE_PATH` (else cwd), run `node "${DEVFLOW_DIR:-$HOME/.devflow}/scripts/release-trace.cjs" last-tag`: `LAST_TAG <tag>` ⇒ that tag is `{last_tag}`; `LAST_TAG none` ⇒ step 1's initial-commit rule; anything else ⇒ keep step 1's tag and report status `INDETERMINATE (last release tag unresolved)`.
+3a. **Closing-keyword rule.** A candidate follows, on the same line, a whitespace token matching `^\(?(close[sd]?|fix(e[sd])?|resolve[sd]?|refs):?$` (case-insensitive). Take the next token, plus each further token while the previous one ends in `,`. Split each on `,`, strip one leading `(` and every trailing character in `[.,;:)\]!?]`, drop empties, then apply step 5's anchored gate unchanged. Read each message as `git log --format=%B` lines.
+3b. **This provider's history grammar** is `^#[1-9][0-9]{0,8}$`. A bare number is not a reference here either: a keyword-anchored candidate must carry the `#`, and step 4 renders every number it reads from a merged PR as `#{n}` before step 5's gate.
+4. If `gh` is authenticated and remote is reachable, resolve which issues the range's merged PRs close — **one listing, never one call per commit** — and merge the result with the commit-message set:
+   - **Once, before the listing:** this repo's identity, `gh api 'repos/{owner}/{repo}' --jq '.owner.login + "/" + .name'`, and the tag's UTC date, `TAG_DATE=$(TZ=UTC git log -1 --date=format-local:%Y-%m-%d --format=%cd {last_tag})`, shape-gated `^[0-9]{4}-[0-9]{2}-[0-9]{2}$` — a local date can drop a PR merged just after the tag. If `TAG_DATE` fails this gate, treat it as **the listing fails** below: emit `TRACEABILITY: DEGRADED ({reason})` and go straight to that bullet's ≤25-PR fallback.
+   - **The listing:** `gh pr list --state merged --search "merged:>=$TAG_DATE" --limit 200 --json number,mergeCommit,closingIssuesReferences`; with no tag, omit `--search`.
+   - **Map locally, with no further call:** keep a listed PR when its `mergeCommit.oid` is in `git rev-list {last_tag}..HEAD`, or when a range commit's subject ends `(#N)` naming it. Keep only references whose `repository.owner.login`/`name` equal this repo's identity — any other ⇒ `TRACEABILITY: DEGRADED (foreign issue reference {ref})`. Render each kept number `#{n}`.
+   - **Coverage:** a range subject carries a PR marker (`(#N)` or `Merge pull request #N`) but no listed PR maps into the range ⇒ `TRACEABILITY: DEGRADED (merged-PR listing did not cover the range)`. A listing of exactly 200 ⇒ status `INDETERMINATE (merged-PR listing hit its 200 cap)`, returning what was collected.
+   - **The listing fails** (an older `gh` reports `Unknown JSON field`) ⇒ `TRACEABILITY: DEGRADED ({reason})`, then fall back to `gh pr view N --json closingIssuesReferences` over the PR numbers in `(#N)` / `Merge pull request #N` subjects — after a listing that succeeds, also over each range `(#N)` naming no listed PR — each N gated `^[1-9][0-9]{0,8}$`, filtered and rendered as above, bounded at ≤25 PRs; report the remainder as `THROTTLED ({n} not processed)` and never report the enrichment as complete while PRs went unresolved.
+   - On any 4xx → DEGRADED for that item, continue. On 5xx → 1 retry; still 5xx → DEGRADED for that item, continue. On the secondary rate limit of `### Provider signals (GitHub)` in this operation's `backlink-shipped-issues` reference → stop GitHub enrichment immediately, report remaining as `THROTTLED`.
+6. **Per-commit trace map.** In one shell: `trap 'rm -- "$T"' EXIT; T="$(mktemp)"`, then one 40-hex SHA per line into `$T` — each range commit step 4 tied to a PR with ≥1 kept reference (its `mergeCommit.oid`, or a subject naming it). From `WORKTREE_PATH` (else cwd), run `node "${DEVFLOW_DIR:-$HOME/.devflow}/scripts/release-trace.cjs" map --from {last_tag} --grammar github --traced-file "$T"; echo "exit=$?"`. Accept only `exit=0` after a first line `TRACE from:<ref> scanned:<n> traced:<n> untraced:<n> exempt:<n> unmatched:<n> bound:<ok|hit>`; copy every line above `exit=0` verbatim under `### TRACE_MAP`. Anything else ⇒ `TRACEABILITY: DEGRADED (trace map unavailable)`, `### TRACE_MAP` = `(unavailable)`, status `INDETERMINATE (trace map unavailable)`. `bound:hit` ⇒ status `INDETERMINATE (trace scan bound 500 hit)`. An `INDETERMINATE` status outranks every other.

package/dist/skills/git/references/tracker/github/manage-debt.md

@@ -0,0 +1,101 @@
+## Operation: manage-debt
+
+Load when the resolved tracker provider is `github` and the operation is `manage-debt`.
+
+**Mechanics held here:** the `**Process:**` body — locating the rolling tech-debt item, creating it when absent, and updating its description.
+
+### Process
+
+1. Find or create "Tech Debt Backlog" issue with `tech-debt` label
+2. Check issue body size; archive if > 60000 chars (per devflow:git)
+3. Extract items to add:
+   - `## Fix Separately` entries from `{REVIEW_DIR}/resolution-summary.md` (FIX_SEPARATE from Triage agent)
+   - `## Deferred to Tech Debt` entries from `{REVIEW_DIR}/resolution-summary.md` (TECH_DEBT from Triage agent)
+   - Pre-existing issues (Category 3) from review reports
+4. Deduplicate against existing items using semantic matching
+5. Remove items that have been fixed (verify in codebase)
+6. Compose updated issue body to `$DEVFLOW_BODY_RAW`; apply the Comment-sink scrub (D11) and post via `gh issue edit {number} --body-file "$DEVFLOW_BODY"`
+7. Return the backlog issue number for Tracked field backfill in resolution-summary.md
+
+### Tech Debt Issue Management
+
+Every body below reaches GitHub through `$DEVFLOW_BODY`, the file the D11 scrub chain
+produced — manage-debt is a body-posting op, so the scrub is unconditional. Each post
+therefore writes ITS OWN content to `$DEVFLOW_BODY_RAW` first: `$DEVFLOW_BODY` is the
+scrubber's output, not a shared mailbox, and posting it without composing into
+`$DEVFLOW_BODY_RAW` in the same step publishes whatever the last scrub happened to leave.
+
+```bash
+MAX_SIZE=60000
+
+post_scrubbed() {
+    # Compose → scrub → post, chained with && from the FIRST link: the compose is
+    # inside the chain, so a failed write stops the post instead of letting the
+    # scrubber scrub — and the chain publish — whatever the RAW file last held.
+    # Never a pipeline: a pipeline's exit status hides a scrubber crash (fail-open).
+    printf '%s\n' "$1" > "$DEVFLOW_BODY_RAW" \
+      && node "${DEVFLOW_DIR:-$HOME/.devflow}/scripts/redact-secrets.cjs" \
+        "$DEVFLOW_BODY_RAW" "$DEVFLOW_BODY" \
+      && gh issue comment "$2" --body-file "$DEVFLOW_BODY"
+}
+
+add_tech_debt_item() {
+    local new_item="$1"
+    local current_body
+    # Items append to the BODY (Process step 6) — a comment would leave the body
+    # invariant, so the probe below could never fire and the archive successor would
+    # be unreachable. A failed read must stop: an empty body REPLACES the backlog.
+    current_body=$(gh issue view "$TECH_DEBT_ISSUE" --json body -q '.body') || return 1
+    local body_length=${#current_body}
+
+    if [ "$body_length" -gt "$MAX_SIZE" ]; then
+        echo "Tech debt issue approaching size limit, archiving..."
+        archive_tech_debt_issue
+        # The successor is a different issue with a different body; if the archive
+        # degraded, TECH_DEBT_ISSUE still names the predecessor and this returns
+        # what the first read did.
+        current_body=$(gh issue view "$TECH_DEBT_ISSUE" --json body -q '.body') || return 1
+    fi
+
+    # Same chain, same reason, as post_scrubbed — only the sink differs: `gh issue
+    # edit` replaces the whole body, so what is composed is the body just read plus
+    # the new item, under its trailing `## Items` heading.
+    printf '%s\n%s\n' "$current_body" "$new_item" > "$DEVFLOW_BODY_RAW" \
+      && node "${DEVFLOW_DIR:-$HOME/.devflow}/scripts/redact-secrets.cjs" \
+        "$DEVFLOW_BODY_RAW" "$DEVFLOW_BODY" \
+      && gh issue edit "$TECH_DEBT_ISSUE" --body-file "$DEVFLOW_BODY"
+}
+
+archive_tech_debt_issue() {
+    local old_issue=$TECH_DEBT_ISSUE
+    local new_url
+    local new_number
+
+    # The successor's body is a posted body: compose, scrub, and create only on a
+    # clean scrubber exit. `gh issue create` prints the new issue's URL, so the
+    # number is its last path segment — parsed command output, checked to be a digit
+    # run before it becomes the issue every later post targets. One `&&` chain end to
+    # end, compose included — the archive comment names the real successor, and the
+    # close happens only after it lands. A failure anywhere reports and stops without
+    # returning non-zero: TECH_DEBT_ISSUE still names the still-open predecessor, so
+    # the caller's item lands there rather than being dropped.
+    printf '%s\n' "Continued from #${old_issue}
+
+## Items
+" > "$DEVFLOW_BODY_RAW" \
+      && node "${DEVFLOW_DIR:-$HOME/.devflow}/scripts/redact-secrets.cjs" \
+        "$DEVFLOW_BODY_RAW" "$DEVFLOW_BODY" \
+      && new_url=$(gh issue create \
+        --title "Tech Debt Backlog" \
+        --label "tech-debt" \
+        --body-file "$DEVFLOW_BODY") \
+      && new_number="${new_url##*/}" \
+      && [[ "$new_number" =~ ^[0-9]+$ ]] \
+      && TECH_DEBT_ISSUE="$new_number" \
+      && post_scrubbed "## Archived
+This issue reached the size limit.
+**Continued in:** #${TECH_DEBT_ISSUE}" "$old_issue" \
+      && gh issue close "$old_issue" \
+      || echo "TRACEABILITY: DEGRADED (tech-debt archive failed for #${old_issue})"
+}
+```

package/dist/skills/git/references/tracker/github/post-wave-report.md

@@ -0,0 +1,28 @@
+## Operation: post-wave-report
+
+Load when the resolved tracker provider is `github` and the operation is `post-wave-report`.
+
+**Mechanics held here:** the `**Process:**` body — locating the wave's tracking item and posting or updating the report.
+
+### Inputs
+
+- `TRACKING_ISSUE`: tracker issue reference for the parent tracking issue
+- `WAVE_REPORT_PATH`: Repo-relative or absolute path to the wave-report.md file written by the wave orchestrator (repo-relative paths are resolved against WORKTREE_PATH when supplied, else the current worktree root)
+- `WAVE_ID`: Timestamped wave directory slug (`YYYY-MM-DD_HHMM`) — used as the dedup marker
+- `WORKTREE_PATH` (optional): See worktree-support skill
+
+### Process
+
+1. Check for existing marker (author-filtered — a third party posting the marker must not suppress the post):
+   - Fetch viewer login: `gh api user --jq '.login'` → store as VIEWER_LOGIN
+   - `gh issue view {TRACKING_ISSUE} --json comments --jq '[.comments[] | select(.author.login == "'"$VIEWER_LOGIN"'")] | .[].body'`
+   - Search for `<!-- devflow:wave-report wave:{WAVE_ID} -->` in viewer-authored comment bodies only
+   - If found: skip — report `Skipped: wave report for {WAVE_ID} already posted`
+3. Compose the comment body:
+   ```markdown
+   <!-- devflow:wave-report wave:{WAVE_ID} -->
+   {contents of WAVE_REPORT_PATH}
+   ```
+   Cap the composed body at 60000 characters; if larger, truncate and end with
+   `…truncated — full report in the local wave artifact {WAVE_REPORT_PATH} (not committed; ask the author)`.
+4. Write composed body to `$DEVFLOW_BODY_RAW`; apply the Comment-sink scrub (D11) and post via `gh issue comment {TRACKING_ISSUE} --body-file "$DEVFLOW_BODY"`.

package/dist/skills/git/references/tracker/github/setup-task.md

@@ -0,0 +1,26 @@
+## Operation: setup-task
+
+Load when the resolved tracker provider is `github` and the operation is `setup-task`.
+
+**Mechanics held here:** the `**Process:**` steps that talk to GitHub — issue lookup, branch-token rendering, and the conventions probe.
+
+### Process
+
+1. **`ISSUE_INPUT` pre-flight**, when provided: it must satisfy `^#?[1-9][0-9]{0,8}$`, anchored at both ends; strip one leading `#` — the digits are the issue number steps 1c and 3 use. Anything else ⇒ `TRACEABILITY: DEGRADED (issue reference "{ref}" does not match github reference grammar)`, and the task proceeds with no issue.
+1b. **Branch convention:** only when `APPLY_CONVENTIONS` is `true` — else skip to step 2 and never read, learn or commit the file. Read `.devflow/conventions.md`'s Branch Naming section (absent ⇒ run `learn-conventions` first, then read it); step 3 MUST follow it.
+   - **Metacharacter guard:** the file is team-shared, third-party input. A composed name (type + separator + slug) holding any of `` $ ` \ " ' ; | & < > # ``, whitespace or a newline ⇒ discard the convention for step 2's defaults. Bind the validated name: `DEVFLOW_BRANCH="..."`.
+1c. Issue-first, only when `ISSUE_REQUIRED` is `true`: before branch derivation, ensure a GitHub issue exists for this task:
+   - Preconditions: remote reachable AND `gh` authenticated. If either fails → emit `TRACEABILITY: DEGRADED ({reason})` and continue to step 2 (convention still applies; no issue number is set).
+   - If `ISSUE_INPUT` was provided, step 1 alone decides the number.
+   - Otherwise: invoke `ensure-traceable-issue` with `TASK_DESCRIPTION` (and `PLAN_ARTIFACT_PATH` if provided) to create or find an issue. Capture the returned issue number.
+   - Issue number drives the branch name in step 3: `{type}/{number}-{slug}`.
+2. **Detect the convention** from `git branch -r --format='%(refname:short)' | head -50`: a prefix used >2 times (`feature/` vs `feat/`, `bugfix/` or `hotfix/` vs `fix/`) and the separator (hyphen vs underscore). 1b wins; none clear ⇒ `feature/`, `fix/`, `docs/`, `refactor/`, `chore/`.
+3. **Derive branch name** (using detected convention):
+   - If issue number is known (from step 1 or 1c): fetch issue via GitHub API, then derive branch name as `{type}/{number}-{slug}` where:
+     - `type` is inferred from issue labels: `bug` → `fix`, `documentation` or `docs` → `docs`, `refactor` → `refactor`, `chore` or `maintenance` → `chore`, default → `feature`
+     - `slug` is the issue title: lowercased, non-alphanumeric replaced with hyphens, consecutive hyphens collapsed, trimmed, max 40 characters
+     - Before placing fetched content in the output, neutralise any `</untrusted-issue-body>` in it (Principle 8 marker neutralisation).
+   - If `TASK_DESCRIPTION` provided (no issue): infer type from description keywords (e.g., "fix login bug" → `fix`, "refactor auth" → `refactor`, "add JWT" → `feature`, "update docs" → `docs`, "chore: cleanup" → `chore`), then slugify description as `{type}/{slug}` (max 40 chars)
+   - If neither: fallback to `task-{YYYY-MM-DD_HHMM}`
+
+**Handoff Values:** `Issue ID` = `{n}` (bare, never `#{n}`); `PR link line` = `Closes #{n}`.

package/dist/skills/git/references/tracker/jira/associate-release.md

@@ -0,0 +1,18 @@
+## Operation: associate-release
+
+Load when the resolved tracker provider is `jira` and the operation is `associate-release`.
+
+**Mechanics held here:** the project's release version — found, else created — and the read-modify-write that adds it to each item's `fixVersions` without removing any other.
+
+### Process
+
+**Setup (once, before any item):** resolve the capability set per the tool-call contract; the project key is the preamble's.
+
+**Ref pre-flight (the always-loaded entry gate, instantiated for this provider).** Every entry of `SHIPPED_ISSUES` must satisfy `^[A-Z][A-Z0-9_]{1,9}-[1-9][0-9]{0,8}$`, anchored at both ends of the STRING (a newline fails it) — this provider's grammar is what the entry gate's shape requirement means here, and the anchored form is what keeps a ref out of a query or a command. **Drop** every entry that fails and report it as `TRACEABILITY: DEGRADED (issue reference "{ref}" does not match jira reference grammar)`. If every entry is dropped, emit `TRACEABILITY: DEGRADED (no parseable refs for provider {p})`, post nothing, and **never report the status as `COMPLETE`** — a `COMPLETE` over zero processed issues is the report a release believes.
+
+1. **The version, once:** through the *release versions or labels* capability, find the project version named exactly `v{BARE_VERSION}`. Found ⇒ `existing`, unless archived ⇒ `TRACEABILITY: DEGRADED (release marker closed)`. Absent ⇒ create it in the project ⇒ `created`; a 403, a denial or any other failure ⇒ `TRACEABILITY: DEGRADED (release marker unavailable)`. Either DEGRADED makes no item call.
+2. **Read once:** one *batch fetch* over the admitted keys, bounded `≤50`, requesting `fixVersions`. A key it returns nothing for ⇒ that item DEGRADED; one already holding the version ⇒ Already set.
+3. **Add**, per item, 1s apart, through the *edit issue fields* capability. Prefer the tool's additive operation; otherwise write the item's current `fixVersions` ∪ the version, and only when step 2 returned that field whole — else that item DEGRADED, with no write. Another version on the item stays; the item counts as Added.
+4. On backpressure, follow `### Provider signals (Jira)` in this operation's `backlink-shipped-issues` reference.
+
+**Residual race, not closed:** the union write drops a version another writer adds between steps 2 and 3; the additive operation has no such window.

package/dist/skills/git/references/tracker/jira/backlink-shipped-issues.md

@@ -0,0 +1,49 @@
+## Operation: backlink-shipped-issues
+
+Load when the resolved tracker provider is `jira` and the operation is `backlink-shipped-issues`.
+
+**Mechanics held here:** the `**Process:**` body — the hoisted identity lookup, the dedup ladder, the back-link post and the inter-item throttle — and, because this is the tracker operation that owns the fan-out, this provider's rate-limit signal for the always-loaded D4 and D11 contracts.
+
+### Provider signals (Jira)
+
+The D4 degradation contract and the D11 comment-sink scrub state the rules; what they leave to the provider is the SIGNAL. These are this provider's.
+
+- **Backpressure is REACTIVE ONLY.** The signal is a `Retry-After` value on a 429. It is **reported, never slept on** — the value can outlast the spawn, and an agent asleep in one is killed before it reports anything. **STOP** the fan-out on a 429 rather than waiting out the window item by item, because continuing to issue requests into one extends the penalty.
+- **There is no pre-emptive rung.** This provider publishes no remaining-request count, so there is no threshold at which the inter-item delay rises. A rung keyed on one would never engage, and a module that stated one would read as coverage while providing none.
+- **Unavailability:** the *add comment* or *list comments with authors* capability absent or denied — D4's "no remote" condition on this provider.
+
+### Dedup ladder — in order, first available rung wins
+
+Rungs, strongest evidence first, each named for a CAPABILITY and never for a tool: **1 `entity-property`** (*entity property read/write*, or *create remote link* / *attachment create, URL form*) → **2 `comment-edit-in-place`** (*edit comment in place*) → **3 `authored-marker`** (*list comments with authors*, matching only what *identify current user* says this account authored — that identity resolved **once per spawn at Setup, never in the loop**) → **4 `post-with-warning`** (nothing above reachable ⇒ `TRACEABILITY: DEGRADED (dedup unavailable — duplicate possible)` and **post anyway**). `## Dedup Strategy` records one of these four TOKENS, a **hint that may only narrow the probe order** — the live probe is the sole authority for the rung reached and for the DEGRADED reason.
+
+**This provider lands on `authored-marker`** by default — the filter compares against the `accountId` *identify current user* resolves — and drops to `post-with-warning` when that capability is absent or denied. The rungs above are reachable wherever this server exposes them: an entity property is the cleanest dedup on offer, being no comment at all, with nothing to quote.
+
+**The marker is the comment's FIRST LINE and nothing else.** This provider's comment format has no HTML-comment node, so the marker is visible prose — line 1 is exactly `devflow:shipped v{BARE_VERSION}`. Match line 1 for equality — a marker on any later line **does not suppress**, because a marker at line 5 of a third-party comment is quoted text, not a devflow post, and a substring search over the whole comment is precisely how a quoter acquires the power to silence a release note.
+
+The namespace is **per comment kind**: this operation owns `devflow:shipped` and no other. A single global marker would make the three kinds mutually suppress — one kind's comment satisfying another kind's dedup predicate — so each operation owns its own namespace and callers pass inputs only.
+
+### Process
+
+**Setup (once, before the loop):** resolve the capability set, the current-user `accountId` from the *identify current user* capability, and the dedup rung.
+
+**Ref pre-flight (the always-loaded entry gate, instantiated for this provider).** Every entry of `SHIPPED_ISSUES` must satisfy `^[A-Z][A-Z0-9_]{1,9}-[1-9][0-9]{0,8}$`, anchored at both ends of the STRING (a newline fails it) — this provider's grammar is what the entry gate's shape requirement means here, and the anchored form is what keeps a ref out of a query or a command. **Drop** every entry that fails and report it as `TRACEABILITY: DEGRADED (issue reference "{ref}" does not match jira reference grammar)`. If every entry is dropped, emit `TRACEABILITY: DEGRADED (no parseable refs for provider {p})`, post nothing, and **never report the status as `COMPLETE`** — a `COMPLETE` over zero processed issues is the report a release believes.
+
+**Hoist first where the provider allows it — the numbered path below is the FALLBACK.** One bounded *list by filter* read over the ≤50 keys per operation, markers matched in memory: one read instead of a hundred.
+
+**Aggregate call budget — the fallback's ceiling.** `authored-marker` is this provider's default landing rung, and there each item's marker check is a paged comment listing rather than one call. The op-level cost is therefore a PRODUCT, and it is bounded: `≤50` items × `≤2` pages = **`≤100`** marker calls. Exceeding the budget ⇒ stop and report the remainder as `TRUNCATED ({n} not processed)`.
+
+For each issue the hoist did not answer, within the operation's `≤50` bound:
+
+1. Read that issue's devflow-authored comments through the rung Setup selected, newest-first, bounded at `≤2` pages.
+2. If line 1 of any such comment equals `devflow:shipped v{BARE_VERSION}`, skip this issue.
+3. Compose the two-line comment — line 1 the marker, line 2 `This was shipped in v{BARE_VERSION}.` — and post it through `### Posting gate` below.
+4. Wait 1s between issues.
+
+### Posting gate
+
+The tool-call contract governs the write; this operation names its steps and restates none of its rules.
+
+1. Compose this post's own content into `$DEVFLOW_BODY_RAW` — a fresh `mktemp` per invocation, under D11's removal `trap`.
+2. Run `node "${DEVFLOW_DIR:-$HOME/.devflow}/scripts/redact-secrets.cjs" --emit "$DEVFLOW_BODY_RAW"`.
+3. Require line 1 to be `D11-OK`; verify `<bytes>` against the received body's byte length; echo `SCRUB: N [type:count,…]`; and when N > 0 also emit `SECRET-EXPOSED (rotate {type} credential — the source file still holds it)`.
+4. Post through the *add comment* capability with arguments (issue key, body: {SCRUBBED_BODY}).

package/dist/skills/git/references/tracker/jira/create-release.md

@@ -0,0 +1,17 @@
+## Operation: create-release
+
+Load when the resolved tracker provider is `jira` and the operation is `create-release`.
+
+**Mechanics held here:** the closed-issues step only. Tag creation, release creation and notes composition stay with the operation and are unchanged — they are release-host mechanics, not tracker mechanics.
+
+### Process
+
+Inside step 5 (compose release notes):
+
+   - If `SHIPPED_ISSUES` is provided: append a `## Closed Issues` section rendering each entry through `## Reference Rendering` — **first ≤50 issues** (the same bound `backlink-shipped-issues` applies); if truncated, add a final `…and {n} more issues` line (D4 degrade if enrichment fails).
+   - Pre-flight the list against `^[A-Z][A-Z0-9_]{1,9}-[1-9][0-9]{0,8}$`, anchored at both ends, and **drop** every entry that fails, reporting each as `TRACEABILITY: DEGRADED (issue reference "{ref}" does not match jira reference grammar)` — a bare number among them goes with them, in silence: `ambiguous issue reference` answers a reference a caller named, not one line of a list nobody chose. Every entry dropped ⇒ `TRACEABILITY: DEGRADED (no parseable refs for provider {p})` and the section is omitted rather than rendered empty.
+   - `## Reference Rendering` absent, or its token discarded by the gate below ⇒ render the key itself on its own line, and record the discard under `### Substitutions`.
+
+**The read-site shape gate for `## Reference Rendering`.** The token arrives from the tracker configuration file, which is hand-editable and machine-wide, so it is parsed HERE — at the sink that renders it, and never on the writer's word. Require `^[A-Za-z0-9 #{}/_.-]{1,60}$`, anchored at both ends, and **discard** any token carrying a backtick, a `$`, a `"`, a `\`, a `;` or a newline. The anchored shape is the gate; the metachar denylist is a second, independent control, named separately so widening the shape for a new token form cannot silently relax it. **Discard, never repair** — a repaired token is one nobody can predict — and a discarded token falls back to **the resolved provider's** documented default, stated once in that provider's own mechanics, with a `### Substitutions` row recording what was dropped. An absent `## Reference Rendering` section, an absent file and a discarded token are the SAME outcome: the documented default. This gate never yields `# UNRESOLVED:`.
+
+**This provider's documented default is `Refs {KEY}-{n}`.** It is stated here because it is a provider fact, and the gate above is what routes to it: a section that is absent, a file that is absent and a token the gate discarded all render this, and none of them is a degradation.

package/dist/skills/git/references/tracker/jira/ensure-pr-ready.md

@@ -0,0 +1,22 @@
+## Operation: ensure-pr-ready
+
+Load when the resolved tracker provider is `jira` and the operation is `ensure-pr-ready`.
+
+**Mechanics held here:** step 4b's TRACKER half only — resolving the issue key for this branch and rendering the link line. The open-PR lookup and the PR-body edit are **PR-host** mechanics, stated once for every provider in `references/pr/ensure-pr-ready.md`: devflow deliberately keeps pull requests on their existing host while the tracker is this one, so nothing about the PR surface is provider-dependent and none of it is restated here.
+
+### Process
+
+4b. (ALWAYS-ON) Ensure the PR body contains a `## Related Issues` section naming the verified issue when one is known. Resolution order:
+   a. Prefer the issue key returned by `setup-task` / `ensure-traceable-issue` for this branch — it was verified at creation time.
+   b. Otherwise fall back to the branch name pattern `{type}/{KEY}-{slug}`: extract the segment matching `^[A-Z][A-Z0-9_]{1,9}-[1-9][0-9]{0,8}$` and verify it with the *fetch by key* capability. If the call fails, or the issue is not open, **skip silently** — never render a link for an unverified reference. A branch name can carry a token that merely looks like one, and the existence check is the guard.
+   c. The *fetch by key* capability absent or denied ⇒ `TRACEABILITY: DEGRADED (no tracker tool for fetch by key)` and skip the section; the PR is never blocked on it.
+
+   Render the line through `## Reference Rendering`. **This provider has no closing-reference magic** — a reference in a PR body does not transition or close anything here, and claiming otherwise in the rendered text would promise an effect that never happens; closing is a `## Transitions` matter and `gather-release-evidence` reports the absence as `TRACEABILITY: DEGRADED (unsupported by jira)`. `## Reference Rendering` absent, or its token discarded by the gate below ⇒ render the key on its own line under the section heading, and record the discard under `### Substitutions`.
+
+   Publish the section through step 4b's PR-host half.
+
+   If no verified issue key is discoverable, skip silently. A failure while updating the PR body emits `TRACEABILITY: DEGRADED ({reason})` and continues — a failed Related Issues update never blocks the PR.
+
+**The read-site shape gate for `## Reference Rendering`.** The token arrives from the tracker configuration file, which is hand-editable and machine-wide, so it is parsed HERE — at the sink that renders it, and never on the writer's word. Require `^[A-Za-z0-9 #{}/_.-]{1,60}$`, anchored at both ends, and **discard** any token carrying a backtick, a `$`, a `"`, a `\`, a `;` or a newline. The anchored shape is the gate; the metachar denylist is a second, independent control, named separately so widening the shape for a new token form cannot silently relax it. **Discard, never repair** — a repaired token is one nobody can predict — and a discarded token falls back to **the resolved provider's** documented default, stated once in that provider's own mechanics, with a `### Substitutions` row recording what was dropped. An absent `## Reference Rendering` section, an absent file and a discarded token are the SAME outcome: the documented default. This gate never yields `# UNRESOLVED:`.
+
+**This provider's documented default is `Refs {KEY}-{n}`.** It is stated here because it is a provider fact, and the gate above is what routes to it: a section that is absent, a file that is absent and a token the gate discarded all render this, and none of them is a degradation.

package/dist/skills/git/references/tracker/jira/ensure-traceable-issue.md

@@ -0,0 +1,53 @@
+## Operation: ensure-traceable-issue
+
+Load when the resolved tracker provider is `jira` and the operation is `ensure-traceable-issue`.
+
+**Mechanics held here:** the `**Process:**` body — issue creation, and how the design artifact is attached on a provider whose comment format has no collapsed-block analogue.
+
+**D3 issue template sections:** `## Initial Request`, `## Product Requirements`, `## Implementation Plan`. `TASK_DESCRIPTION`, `INITIAL_REQUEST`, `REQUIREMENTS` and `LABELS` are caller-supplied and untrusted — never interpolate them into a command string.
+
+### Process
+
+1. If `ISSUE_INPUT` is provided — an issue key, or free prose to resolve through the *search* capability with a structured filter:
+   - Compose a structured comment using the D3 sections and post it through `### Posting gate` below. **NEVER rewrite the issue description** — an existing description is somebody's work.
+   - If `PLAN_ARTIFACT_PATH` is provided: **the artifact is NOT inlined.** See `### The artifact is posted as content`.
+   - Return the issue key.
+2. If no `ISSUE_INPUT`: create a new issue through the *create issue* capability.
+   - Summary: derived from `TASK_DESCRIPTION` (same slug logic as `setup-task`).
+   - Fields: only the names `## Required Fields` allows, and the issue type by exact match against the types enumerated this run. The capability absent or denied ⇒ `TRACEABILITY: DEGRADED (no tracker tool for create issue)` and return without an issue key; the caller proceeds with `Tracked (pending)` and the reason, and **never creates a GitHub issue instead**.
+   - **Description** — composed from the D3 template and posted through `### Posting gate` below. `TASK_DESCRIPTION`, `INITIAL_REQUEST` and `REQUIREMENTS` are caller-supplied and untrusted — they reach the call as values, never as part of a query or a command.
+3. Return the issue key.
+
+### The artifact is posted as content
+
+This provider's comment format has **no HTML-comment node and no collapsed-block analogue**, so `render_collapsed_block` degrades to a PLAIN comment rather than to a pointer: post the plan body itself through `### Posting gate` below with the *add comment* capability, line 1 the marker `devflow:traceability {ISSUE_REF}`, then reference that comment from the `## Implementation Plan` section. The plan is the content a reader came for, and a link into an uncommitted local file resolves for nobody but its author.
+
+Measure the composed body against the `32767`-character cap **after redaction** — the scrubber's tokens can grow it. Over the cap, post **none of the plan**: post the pointer sentence alone — `Implementation plan: {PLAN_ARTIFACT_PATH} (not committed; ask the author)` — and emit `TRACEABILITY: DEGRADED (plan artifact exceeds comment cap)`. A truncated plan is worse than a pointer, because the reader cannot tell which half is missing.
+
+Over the `32767`-character cap after redaction, truncate in **preservation order** — line 1 the marker, then the status and DEGRADED lines, then the pointer sentence; the untrusted middle is what gets cut — and end with `NOTE: body exceeded the 32767-character cap after redaction — truncated/stub posted`. The pointer sentence is the last thing to go because it is the only line that still leads somewhere.
+
+### Query safety
+
+Caller-supplied prose reaches the tracker as a QUERY here and nowhere else in this provider's mechanics, so the rule is stated here once.
+
+- **Prefer a structured filter argument.** Compose a query string only when no structured filter argument can express the predicate; a structured argument cannot be re-parsed into a different question.
+- A caller-supplied value may appear **only as a quoted string literal**, and only in value position — never as a field name, never as an operator, never in an ordering clause. A value that decides the SHAPE of a query is a value that can become a different query.
+- Escape `\` first and then `"`. The other order escapes the backslash the second pass just inserted and leaves the quote live.
+- After escaping, **drop** any value still carrying `"`, `\`, a newline or a backtick. Repair is forbidden: a repaired value is one nobody can predict, and dropping it costs a search result while repairing it costs the query.
+- Every query carries the `≤50` result bound and reports what it could not return as `TRUNCATED ({n} not processed)`.
+
+### Posting gate
+
+The tool-call contract governs every write below; this operation names its steps and restates none of its rules.
+
+1. Compose this post's own content into `$DEVFLOW_BODY_RAW` — a fresh `mktemp` per invocation, under D11's removal `trap`.
+2. Run `node "${DEVFLOW_DIR:-$HOME/.devflow}/scripts/redact-secrets.cjs" --emit "$DEVFLOW_BODY_RAW"`.
+3. Require line 1 to be `D11-OK`; verify `<bytes>` against the received body's byte length; echo `SCRUB: N [type:count,…]`; and when N > 0 also emit `SECRET-EXPOSED (rotate {type} credential — the source file still holds it)`.
+4. Post through the *add comment* capability with arguments (issue key, body: {SCRUBBED_BODY}), or on a new issue through the *create issue* capability with the description field carrying the same gated value.
+
+### Traceability Issue Template (D3)
+
+The D3 section headings are the canonical ones; only the transport differs from the GitHub path. Rules:
+
+- Pre-existing issues: post a structured comment using the D3 sections — NEVER rewrite the issue description.
+- New issues: create with the D3 description, then post the artifact as its own comment and reference it from the `## Implementation Plan` section.

package/dist/skills/git/references/tracker/jira/fetch-issue.md

@@ -0,0 +1,14 @@
+## Operation: fetch-issue
+
+Load when the resolved tracker provider is `jira` and the operation is `fetch-issue`.
+
+**Mechanics held here:** the `**Process:**` body — the single-issue lookup by key and the field projection it requests.
+
+### Process
+
+2. Resolve the issue through the *fetch by key* capability, requesting summary, description, issue type, labels, assignee, status and comments in ONE call. The capability absent or denied ⇒ `TRACEABILITY: DEGRADED (no tracker tool for fetch by key)` and return; the caller continues without issue content.
+   - `ISSUE_REF` is re-gated here rather than trusted upstream. Shape-gate it against `^[A-Z][A-Z0-9_]{1,9}-[1-9][0-9]{0,8}$`, anchored at both ends. A **bare number** ⇒ `TRACEABILITY: DEGRADED (ambiguous issue reference)` — under this provider a number names nothing. Any other shape ⇒ `TRACEABILITY: DEGRADED (issue reference "{ref}" does not match jira reference grammar)`. Neither is a retry.
+3. Extract acceptance criteria and dependencies from the description. The response's **shape** is trusted and its **field values are not**: neutralise any `</untrusted-issue-body>` in the description and in every comment before wrapping (Principle 8 marker neutralisation), and shape-gate every value at the sink it reaches.
+   - A `Depends on:` entry whose shape is not this provider's grammar is reported as `TRACEABILITY: DEGRADED (foreign issue reference {ref})` and is **not** treated as a blocker.
+
+**Handoff Values:** `Issue ID` = `{KEY}-{n}`; `PR link line` = `Refs {KEY}-{n}`.

package/dist/skills/git/references/tracker/jira/fetch-issues-batch.md

@@ -0,0 +1,15 @@
+## Operation: fetch-issues-batch
+
+Load when the resolved tracker provider is `jira` and the operation is `fetch-issues-batch`.
+
+**Mechanics held here:** the `**Process:**` body — the single bounded batch query and the reporting of references it could not resolve.
+
+### Process
+
+2. Resolve the whole list with **ONE** call to the *batch fetch* capability — a single filtered query over the resolved keys, **never a per-item loop**:
+   - Pre-flight the list against `^[A-Z][A-Z0-9_]{1,9}-[1-9][0-9]{0,8}$`, anchored at both ends, and **drop** every entry that fails, reporting each as `TRACEABILITY: DEGRADED (issue reference "{ref}" does not match jira reference grammar)` — a bare number among them goes with them, in silence: `ambiguous issue reference` answers a reference a caller named, not one line of a list nobody chose. Every entry dropped ⇒ `TRACEABILITY: DEGRADED (no parseable refs for provider {p})` and return without querying.
+   - Build the filter as `key in (KEY-1, KEY-2, …)` over the surviving keys, bounded `≤50` keys with an explicit `maxResults` bound carried on the query itself. More than 50 surviving keys ⇒ query the first 50 in list order and report the remainder as `TRUNCATED ({n} not processed)`.
+   - Keys reach the filter only as **quoted string literals** and only in value position. They are already anchored by the pre-flight, so nothing needs escaping to be safe — and nothing may be repaired to become safe.
+   - Request the same projection the single-issue lookup requests, so a batch refresh and a single lookup return the same fields.
+2b. Render each issue's status as a `**State**: {state}` line of its own, between that issue's `### Issue {KEY}:` heading and its `<untrusted-issue-body>` marker — OUTSIDE the wrapper, because the status is an enum the tracker computed, not remote prose. A caller refreshing a batch reads it to see a ticket closed out of band.
+2c. A key the query returned nothing for is reported once and is not retried individually: a missing key is a permission or a deletion, and a second call answers the same thing at twice the cost.

package/dist/skills/git/references/tracker/jira/gather-release-evidence.md

@@ -0,0 +1,18 @@
+## Operation: gather-release-evidence
+
+Load when the resolved tracker provider is `jira` and the operation is `gather-release-evidence`.
+
+**Mechanics held here:** the last release tag, resolving which issues a commit range closes, the honest reporting of what this provider cannot resolve, and the trace map.
+
+### Process
+
+1a. **Last release tag.** Step 1's `git describe` can return a non-release marker tag. From `WORKTREE_PATH` (else cwd), run `node "${DEVFLOW_DIR:-$HOME/.devflow}/scripts/release-trace.cjs" last-tag`: `LAST_TAG <tag>` ⇒ that tag is `{last_tag}`; `LAST_TAG none` ⇒ step 1's initial-commit rule; anything else ⇒ keep step 1's tag and report status `INDETERMINATE (last release tag unresolved)`.
+3a. **Closing-keyword rule.** A candidate follows, on the same line, a whitespace token matching `^\(?(close[sd]?|fix(e[sd])?|resolve[sd]?|refs):?$` (case-insensitive). Take the next token, plus each further token while the previous one ends in `,`. Split each on `,`, strip one leading `(` and every trailing character in `[.,;:)\]!?]`, drop empties, then apply step 5's anchored gate unchanged. Read each message as `git log --format=%B` lines.
+4. Resolve which issues the commit range closes:
+   - **There is no closing-reference capability on this provider.** Emit `TRACEABILITY: DEGRADED (unsupported by jira)` once for the whole step and fall back to the commit-message set alone — the refs parsed out of the candidate references the agent extracted from the range's commit messages.
+   - **This provider's history grammar** is `^[A-Z][A-Z0-9_]{1,9}-[1-9][0-9]{0,8}$`, and its KEY segment must equal the resolved project key after ASCII-upper normalisation — a well-formed key belonging to another project is a `TRACEABILITY: DEGRADED (foreign issue reference {ref})`, not a shipped issue.
+   - Pre-flight the list against `^[A-Z][A-Z0-9_]{1,9}-[1-9][0-9]{0,8}$`, anchored at both ends, and **drop** every entry that fails, reporting each as `TRACEABILITY: DEGRADED (issue reference "{ref}" does not match jira reference grammar)` — a bare number among them goes with them, in silence: `ambiguous issue reference` answers a reference a caller named, not one line of a list nobody chose. Every entry dropped ⇒ `TRACEABILITY: DEGRADED (no parseable refs for provider {p})`.
+   - Confirm the survivors exist with **one** call to the *batch fetch* capability over the whole set, bounded `≤50` with `TRUNCATED ({n} not processed)` for the remainder — **one query, never a per-item loop**.
+   - **Because the closing-reference step degraded, the enrichment is incomplete by construction: never report the status as `COMPLETE`.** Report `PARTIAL ({n} DEGRADED)` whenever any step above degraded, and `TRUNCATED ({n} not processed)` whenever the bound was reached. A release that reads `COMPLETE` over an unresolvable evidence set is the one report nobody re-checks.
+   - On a tool error for an individual item → DEGRADED for that item, continue. On backpressure → follow `### Provider signals (Jira)` in this operation's `backlink-shipped-issues` reference, which is where this provider's one signal is stated.
+6. **Per-commit trace map.** `{KEY}` is the resolved project key; with none usable, skip the run and take the arm below. From `WORKTREE_PATH` (else cwd), run `node "${DEVFLOW_DIR:-$HOME/.devflow}/scripts/release-trace.cjs" map --from {last_tag} --grammar jira --key {KEY}; echo "exit=$?"`. Accept only `exit=0` after a first line `TRACE from:<ref> scanned:<n> traced:<n> untraced:<n> exempt:<n> unmatched:<n> bound:<ok|hit>`; copy every line above `exit=0` verbatim under `### TRACE_MAP`. Anything else ⇒ `TRACEABILITY: DEGRADED (trace map unavailable)`, `### TRACE_MAP` = `(unavailable)`, status `INDETERMINATE (trace map unavailable)`. `bound:hit` ⇒ status `INDETERMINATE (trace scan bound 500 hit)`. An `INDETERMINATE` status outranks every other.

package/dist/skills/git/references/tracker/jira/manage-debt.md

@@ -0,0 +1,37 @@
+## Operation: manage-debt
+
+Load when the resolved tracker provider is `jira` and the operation is `manage-debt`.
+
+**Mechanics held here:** the `**Process:**` body — locating the rolling tech-debt item, creating it when absent, and updating its description.
+
+### Process
+
+1. Find or create the rolling "Tech Debt Backlog" item. `## Tech Debt` defaults to a **single rolling item**, so this operation looks for exactly one: use the *search* capability once with a structured filter over the resolved project and the tech-debt label. Absent ⇒ create it with the *create issue* capability, using only the field names `## Required Fields` allows.
+2. Check the item's description length against the `32767`-character cap; archive when it is over.
+3. Extract items to add:
+   - `## Fix Separately` entries from `{REVIEW_DIR}/resolution-summary.md` (FIX_SEPARATE from Triage agent)
+   - `## Deferred to Tech Debt` entries from `{REVIEW_DIR}/resolution-summary.md` (TECH_DEBT from Triage agent)
+   - Pre-existing issues (Category 3) from review reports
+4. Deduplicate against existing items using semantic matching.
+5. Remove items that have been fixed (verify in codebase).
+6. Compose the updated description and post it through the gate in `### Posting gate` below, using the *update description* capability.
+7. Return the backlog item's key for Tracked field backfill in resolution-summary.md.
+
+### Archiving at the cap
+
+Over `32767` characters the rolling item is closed and a successor is created, exactly as the provider-independent rule says — but the composed successor body is a POSTED body and goes through the same gate:
+
+1. Compose `Continued from {OLD_KEY}` plus an empty `### Items` section.
+2. Create the successor through the gate below. Only on a clean gate does the successor become the item later posts target.
+3. Post a back-link on the predecessor naming the successor's key, then close the predecessor.
+4. A failure anywhere reports and stops without returning non-zero: the predecessor is still open, so the caller's item lands there rather than being dropped.
+
+### Posting gate
+
+The tool-call contract governs every write below; this operation names its steps and restates none of its rules.
+
+1. Compose this post's own content into `$DEVFLOW_BODY_RAW` — a fresh `mktemp` per invocation, under D11's removal `trap`. `$DEVFLOW_BODY_RAW` is the scrubber's input and nothing else ever reads it.
+2. Run `node "${DEVFLOW_DIR:-$HOME/.devflow}/scripts/redact-secrets.cjs" --emit "$DEVFLOW_BODY_RAW"`.
+3. Require line 1 to be `D11-OK`; verify `<bytes>` against the received body's byte length; echo `SCRUB: N [type:count,…]`; and when N > 0 also emit `SECRET-EXPOSED (rotate {type} credential — the source file still holds it)`.
+4. Post through the *update description* capability with arguments (issue key, description: {SCRUBBED_BODY}).
+5. Over the `32767` cap after redaction, truncate in **preservation order** — the first line, then the status and DEGRADED lines, then the pointer sentence; the untrusted middle is what gets cut — and end with `NOTE: body exceeded the 32767-character cap after redaction — truncated/stub posted`.

package/dist/skills/git/references/tracker/jira/post-wave-report.md

@@ -0,0 +1,33 @@
+## Operation: post-wave-report
+
+Load when the resolved tracker provider is `jira` and the operation is `post-wave-report`.
+
+**Mechanics held here:** the `**Process:**` body — locating the wave's tracking item and posting the report once.
+
+### Inputs
+
+- `TRACKING_ISSUE`: tracker issue reference for the parent tracking issue
+- `WAVE_REPORT_PATH`: Repo-relative or absolute path to the wave-report.md file written by the wave orchestrator (repo-relative paths are resolved against WORKTREE_PATH when supplied, else the current worktree root)
+- `WAVE_ID`: Timestamped wave directory slug (`YYYY-MM-DD_HHMM`) — used as the dedup marker
+- `WORKTREE_PATH` (optional): See worktree-support skill
+
+### Process
+
+**Setup (once):** resolve the capability set and the current-user `accountId` from the *identify current user* capability. `accountId` unavailable ⇒ `TRACEABILITY: DEGRADED (dedup unavailable — duplicate possible)` and post anyway.
+
+1. Check for an existing marker on the tracking item, author-filtered — a third party posting the marker must not suppress the post.
+   - Read the tracking item's comments through the *list comments with authors* capability and keep only the ones that `accountId` authored.
+   - This operation owns the `devflow:wave` namespace and no other. Match **line 1** of each such comment for equality against `devflow:wave {WAVE_ID}`; a marker on any later line **does not suppress**.
+   - **The scan is a FULL scan, not a newest-first early exit.** A wave report's marker carries a wave id, and wave ids are not monotonic in comment order, so an early exit can miss the one comment that matters. Bound it at `≤5` pages and **fail closed**: if the bound is reached before the scan completes, report `TRUNCATED ({n} not processed)` and **DO NOT POST** — a duplicate wave report is a worse outcome than a missing one, because the next run cannot tell which is authoritative.
+   - If found: skip — report `Skipped: wave report for {WAVE_ID} already posted`.
+3. Compose the comment: line 1 the marker `devflow:wave {WAVE_ID}`, then the contents of `WAVE_REPORT_PATH`. Cap the composed content at `32767` characters; over the cap, truncate in **preservation order** — the marker, then the status and DEGRADED lines, then the pointer sentence — and end with `…truncated — full report in the local wave artifact {WAVE_REPORT_PATH} (not committed; ask the author)`.
+4. Post it through `### Posting gate` below.
+
+### Posting gate
+
+The tool-call contract governs the write; this operation names its steps and restates none of its rules.
+
+1. Compose this post's own content into `$DEVFLOW_BODY_RAW` — a fresh `mktemp` per invocation, under D11's removal `trap`.
+2. Run `node "${DEVFLOW_DIR:-$HOME/.devflow}/scripts/redact-secrets.cjs" --emit "$DEVFLOW_BODY_RAW"`.
+3. Require line 1 to be `D11-OK`; verify `<bytes>` against the received body's byte length; echo `SCRUB: N [type:count,…]`; and when N > 0 also emit `SECRET-EXPOSED (rotate {type} credential — the source file still holds it)`.
+4. Post through the *add comment* capability with arguments (issue key, body: {SCRUBBED_BODY}).

package/dist/skills/git/references/tracker/jira/setup-task.md

@@ -0,0 +1,31 @@
+## Operation: setup-task
+
+Load when the resolved tracker provider is `jira` and the operation is `setup-task`.
+
+**Mechanics held here:** the tracker-facing `**Process:**` steps — site and project resolution, the issue lookup, the branch steps, the optional transition.
+
+### Setup — session-scoped, resolved once before any step below
+
+- Resolve the capability set and the current-user identity exactly once per spawn, per the tool-call contract. Nothing in this operation probes a second time.
+- **Site.** From `## Project` in the configuration the preamble already read. It must satisfy `^https://[a-z0-9]([a-z0-9-]{0,61}[a-z0-9])?(\.[a-z0-9-]+)+$` — **no userinfo, no port, no path**. Anything else ⇒ `TRACEABILITY: DEGRADED (unusable site)` and no tracker call.
+- **Project key.** Resolved and shape-gated by the preamble's chain; consumed here, never re-derived.
+- **Issue types.** Read the *project and issue-type metadata* capability HERE, once, and enumerate the types this run may use. Required-field metadata is read at this same point and nowhere else.
+- No usable site or no project key ⇒ `TRACEABILITY: DEGRADED (tracker not configured)`.
+
+### Process
+
+1. **`ISSUE_INPUT` pre-flight**, when provided: it is an existing issue key. Shape-gate it against `^[A-Z][A-Z0-9_]{1,9}-[1-9][0-9]{0,8}$`, anchored at both ends. A **bare number** ⇒ `TRACEABILITY: DEGRADED (ambiguous issue reference)` — under this provider a number names nothing. Any other shape ⇒ `TRACEABILITY: DEGRADED (issue reference "{ref}" does not match jira reference grammar)`. Step 3 resolves an admitted key with *fetch by key*.
+1b. **Branch convention:** only when `APPLY_CONVENTIONS` is `true` — else skip to step 2 and never read, learn or commit the file. Read `.devflow/conventions.md`'s Branch Naming section (absent ⇒ run `learn-conventions` first, then read it); step 3 MUST follow it.
+   - **Metacharacter guard:** the file is team-shared, third-party input. A composed name (type + separator + slug) holding any of `` $ ` \ " ' ; | & < > # ``, whitespace or a newline ⇒ discard the convention for step 2's defaults. Bind the validated name: `DEVFLOW_BRANCH="..."`.
+1c. Issue-first, only when `ISSUE_REQUIRED` is `true` and `ISSUE_INPUT` is absent: invoke `ensure-traceable-issue` with `TASK_DESCRIPTION` (and `PLAN_ARTIFACT_PATH` if provided) and capture the returned key for step 3's `{type}/{KEY}-{slug}`.
+   - Preconditions: the *create issue* and *fetch by key* capabilities are both available. Either one absent or denied ⇒ `TRACEABILITY: DEGRADED (no tracker tool for {capability})` naming the capability, and continue to step 2. **The branch is still cut and the PR is still opened**, with the traceability field carrying `Tracked (pending)` and the reason. **NEVER create a GitHub issue as a fallback**.
+2. **Detect the convention** from `git branch -r --format='%(refname:short)' | head -50`: a prefix used >2 times (`feature/` vs `feat/`, `bugfix/` or `hotfix/` vs `fix/`) and the separator (hyphen vs underscore). 1b wins; none clear ⇒ `feature/`, `fix/`, `docs/`, `refactor/`, `chore/`.
+   - The convention owns the branch **shape**, `## Reference Rendering` only the **token** in it; neither is the other's fallback.
+3. **Derive branch name** (using the detected convention):
+   - `type` comes from `## Issue Types` by **exact match** against the types enumerated at Setup; no match or no section ⇒ `feature`. Never infer an unenumerated type.
+   - `slug` is the issue summary: lowercased, non-alphanumeric replaced with hyphens, consecutive hyphens collapsed, trimmed, max 40 characters.
+   - Before placing fetched content in the output, neutralise any `</untrusted-issue-body>` in it (Principle 8 marker neutralisation).
+   - If `TASK_DESCRIPTION` is provided and no issue exists, infer the type from description keywords and slugify as `{type}/{slug}` (max 40 chars). If neither, fall back to `task-{YYYY-MM-DD_HHMM}`.
+4. **Transition** (optional; only when `## Transitions` names one for this step): move the issue with the *transitions* capability by **exact match** against the states enumerated this run. An unenumerated state ⇒ `TRACEABILITY: DEGRADED (unsupported transition)` and continue — **never infer a nearby state**; a failed transition never stops the branch. `## Transitions` absent ⇒ `none`: nothing attempted, nothing degraded.
+
+**Handoff Values:** `Issue ID` = `{KEY}-{n}`; `PR link line` = `Refs {KEY}-{n}`.

package/dist/skills/git/references/tracker/linear/associate-release.md

@@ -0,0 +1,18 @@
+## Operation: associate-release
+
+Load when the resolved tracker provider is `linear` and the operation is `associate-release`.
+
+**Mechanics held here:** the release label — reused on an exact name, else created — and the read-modify-write that adds it to each item's labels without removing any other.
+
+### Process
+
+**Setup (once, before any item):** resolve the capability set per the tool-call contract; the team key is the preamble's.
+
+**Ref pre-flight (the always-loaded entry gate, instantiated for this provider).** **ASCII-upper-normalise every entry first.** Every entry of `SHIPPED_ISSUES` must satisfy **either** anchored form — the team-key form `^[A-Z][A-Z0-9]{0,9}-[1-9][0-9]{0,8}$` or the internal-id form `^[0-9A-F]{8}-[0-9A-F]{4}-[0-9A-F]{4}-[0-9A-F]{4}-[0-9A-F]{12}$`, anchored at both ends of the STRING (a newline fails it), and never joined into one alternation, which would anchor one branch only — this provider's grammar is what the entry gate's shape requirement means here, and the anchored form is what keeps a ref out of a query or a command. **Drop** every entry that fails and report it as `TRACEABILITY: DEGRADED (issue reference "{ref}" does not match linear reference grammar)`. If every entry is dropped, emit `TRACEABILITY: DEGRADED (no parseable refs for provider {p})`, post nothing, and **never report the status as `COMPLETE`** — a `COMPLETE` over zero processed issues is the report a release believes.
+
+1. **The label, once:** through the *release versions or labels* capability, list the labels named exactly `v{BARE_VERSION}` that the resolved team can apply. Exactly one ⇒ reuse it, `existing`; none ⇒ create it in that team, `created`; two or more ⇒ `TRACEABILITY: DEGRADED (ambiguous release marker)`. A failed read or create ⇒ `TRACEABILITY: DEGRADED (release marker unavailable)`. Either DEGRADED makes no item call.
+2. **Read once:** one *batch fetch* over the admitted references, bounded `≤50`, requesting labels. A reference it returns nothing for ⇒ that item DEGRADED; one already holding the label ⇒ Already set.
+3. **Add**, per item, 1s apart, through the *edit issue fields* capability. The stock issue update REPLACES the label set, so prefer an additive operation; otherwise write the item's current labels ∪ the release label, and only when step 2 returned them whole — else that item DEGRADED, with no write. Another release label on the item stays; the item counts as Added.
+4. On backpressure, follow `### Provider signals (Linear)` in this operation's `backlink-shipped-issues` reference.
+
+**Residual race, not closed:** the union write drops a label another writer adds between steps 2 and 3; the additive operation has no such window.