@drafthq/draft 3.6.0 → 3.7.1

package/core/shared/jira-sync.md

@@ -28,7 +28,7 @@ All Jira content written by Draft (comments and descriptions) MUST include a sig
 
 Append this signature block at the end of every Jira comment:
 
-```
+```text
 ─────────────────────────────
 🤖 Generated by Draft
 ```
@@ -37,7 +37,7 @@ Append this signature block at the end of every Jira comment:
 
 Append this signature line inside `{noformat}` blocks at the end of every Jira description:
 
-```
+```yaml
 ---
 🤖 Generated by Draft
 Branch: [branch-name] | Commit: [short-hash]
@@ -63,7 +63,7 @@ On every sync operation, after posting the comment or attachment:
 
 All Jira comments from Draft follow this format for consistency and scannability:
 
-```
+```json
 [draft] {action}: {1-line summary}
 ─────────────────────────────
 • {key detail 1}
@@ -77,7 +77,8 @@ Attachment: {filename} (if applicable)
 ```
 
 Examples:
-```
+
+```json
 [draft] spec-complete: Specification and plan generated for track add-user-auth
 ─────────────────────────────
 • 3 phases, 12 tasks planned
@@ -90,7 +91,7 @@ Attachments: spec.md, plan.md
 🤖 Generated by Draft
 ```
 
-```
+```json
 [draft] rca-complete: Root cause identified for login timeout
 ─────────────────────────────
 • Root cause: connection pool exhaustion under concurrent load
@@ -118,7 +119,7 @@ Attachment: rca.md
 
 ## Sync Procedure
 
-```
+```text
 1. Verify Jira MCP is available (from context loading state)
    - If unavailable: queue to .jira-sync-queue.json, return
 
@@ -152,8 +153,10 @@ Attachment: rca.md
 ## Failure Handling
 
 If MCP operation fails:
+
 1. Do NOT fail the parent skill
 2. Save pending sync to `draft/tracks/<id>/.jira-sync-queue.json`:
+
    ```json
    {
      "pending": [
@@ -166,5 +169,6 @@ If MCP operation fails:
      ]
    }
    ```
+
 3. On next successful MCP connection, retry queued items
 4. Warn user: "Jira sync queued (MCP unavailable). Will retry on next connection."

package/core/shared/okf-retrieval.md

@@ -20,7 +20,7 @@ If `draft/wiki/` does **not** exist (monolith mode), skip this procedure entirel
 
 The bundle is a tree: `.ai-context.md` (index root: Synopsis + Concept Map) → section indexes (`systems/`, `features/`, `reference/`, `entrypoints/`, `overview/`) → concept pages. Each node advertises a `description` routing key. Navigate it, do not flatten it.
 
-```
+```text
 1. Frame the query
    Extract routing terms from the active task: domain nouns from spec.md
    acceptance criteria, file paths / module names / tech terms from plan.md,

package/core/shared/parallel-analysis.md

@@ -8,7 +8,7 @@
 
 ## Architecture
 
-```
+```text
 Phase 1 (Map) N parallel reader agents bounded scope per agent (4 modules each)
                  each agent reads source files in its assigned modules
                  each agent outputs (A) IR JSON array — structured metadata for tables/diagrams
@@ -97,7 +97,7 @@ Large modules with deep sub-module hierarchies (e.g., 500+ files with 5+ sub-mod
 Use this verbatim as the `prompt` field when spawning each reader agent via the `Agent` tool.
 Replace `{MODULE_LIST}`, `{REPO_ROOT}`, and `{GRAPH_DATA_SUMMARY}` before sending.
 
-```
+```text
 You are a module reader agent. You have two jobs for each assigned module:
 (A) Extract structured IR JSON — metadata for tables and diagrams
 (B) Write a full §7 deep-dive section in Markdown — prose the synthesis agent will paste verbatim into architecture.md
@@ -206,7 +206,7 @@ Only when the graph shows clear internal structure with its own public surface o
 Use this as the prompt for the single synthesis agent in Phase 2.
 Replace `{CONCATENATED_IRS}`, `{GRAPH_DEPENDENCY_DIAGRAM}`, and `{ARCHITECTURE_TEMPLATE_STRUCTURE}`.
 
-```
+```text
 You are the synthesis agent. Your job is to assemble draft/architecture.md from reader outputs.
 
 ## Inputs
@@ -305,7 +305,7 @@ For tier 1–2, skip parallelism — one reader agent handles all modules sequen
 
 When assigning modules to reader agents (tier 3+), apply this priority ordering:
 
-```
+```text
 Rule 1: Assign high fan-in modules to separate readers
         (modules with many callers produce IRs that many other IRs reference)
 
@@ -319,7 +319,8 @@ Rule 4: Use tier table above for modules-per-agent target
 ```
 
 Example grouping heuristic (adapt to actual fan-in data from graph):
-```
+
+```yaml
 reader_A: [highest fan-in module alone] — never share high-fan-in with others
 reader_B: [coupled pair: module_X + module_Y] — modules that call each other
 reader_C: [data layer modules] — shared persistence/cache modules together
@@ -332,24 +333,30 @@ reader_E: [infra/bootstrap modules] — low fan-in, foundational
 ## Failure Modes and Recovery
 
 ### Reader produces prose instead of IR
+
 **Detection:** Output doesn't start with `[` or fails JSON.parse.
 **Recovery:** Retry that reader with stricter constraint:
-```
+
+```text
 RETRY INSTRUCTION: Your previous output was not valid JSON. Output ONLY the JSON array.
 The first character of your response MUST be `[`. No preamble. No explanation.
 ```
+
 **Fallback:** If retry fails, run those modules through the standard sequential analysis.
 
 ### IR is too sparse AND deep-dive is too short
+
 **Detection:** IR `token_budget_used < 150` for a module with >20 files AND deep-dive < 100 lines.
 **Recovery:** Re-run that reader with explicit instruction to read more source files and expand the deep-dive.
 If only the IR is sparse but the deep-dive is substantive, no action needed — prose is the primary output.
 
 ### Synthesis agent re-reads source outside policy
+
 **Detection:** Tool calls to Read for files not in the permitted-sections list during synthesis.
 **Prevention:** The synthesis prompt lists exactly which sections permit source reads. Outside those, synthesis derives from reader prose and IR.
 
 ### One reader agent fails entirely
+
 **Detection:** Agent returns error or times out.
 **Recovery:** Run the failed module group through standard sequential analysis.
 The other readers' IRs are still valid — only the failed group needs re-work.
@@ -359,7 +366,7 @@ This is the blast-radius advantage over single-agent: a reader failure is a part
 
 ## Token Budget Model
 
-```
+```text
 Phase 1 readers (parallel, ceil(M/4) agents):
   Per agent: 4 modules × ~4K source tokens = ~16K input
                  IR output: ~2K tokens/agent

package/core/shared/pattern-learning.md

@@ -11,6 +11,7 @@ Referenced by: `/draft:bughunt`, `/draft:deep-review`, `/draft:review`, `/draft:
 Execute this phase **after** the main analysis and report generation are complete. This phase updates `draft/guardrails.md` with newly discovered patterns.
 
 **Skip this phase if:**
+
 - `draft/` directory does not exist (no Draft context)
 - Analysis found zero findings to learn from
 - Running in a read-only or preview mode
@@ -110,6 +111,7 @@ Append under `## Learned Anti-Patterns`:
 ```
 
 `graph_severity` derivation rules (from live hotspot query `scripts/tools/hotspot-rank.sh --repo .` fanIn values):
+
 - fanIn ≥ 10 in any evidence file → `critical`
 - fanIn 5–9 → `high`
 - fanIn 1–4 → `medium`

package/core/shared/template-contract.md

@@ -19,4 +19,4 @@ See [verification-gates.md](verification-gates.md) for the canonical WS-9 gate c
 
 **Required track artifacts (2.0):** `spec.md`, `plan.md`, `hld.md`, `lld.md`, `metadata.json`, `discovery.md`.
 
-**Scope fields:** `metadata.json:scope_includes` / `scope_excludes` (or spec frontmatter fallback) define track footprint; conflicts block parallel work without explicit exclusion.
+**Scope fields:** `metadata.json:scope_includes` / `scope_excludes` (or spec frontmatter fallback) define track footprint; conflicts block parallel work without explicit exclusion.

package/core/shared/vcs-commands.md

@@ -38,7 +38,7 @@ git rev-list [range]             # Commit listing
 
 Draft uses [Conventional Commits](https://www.conventionalcommits.org/) for traceability:
 
-```
+```text
 <type>(<track_id>): <description>
 
 [optional body]
@@ -49,11 +49,13 @@ Draft uses [Conventional Commits](https://www.conventionalcommits.org/) for trac
 Common `<type>` values: `feat`, `fix`, `refactor`, `test`, `docs`, `chore`, `perf`.
 
 Footer fields (when applicable):
+
 - `Refs: <issue or PR number>` — link to issue tracker
 - `Co-Authored-By: <name> <email>` — for AI-assisted commits
 
 If a Jira ticket is linked in `spec.md`, include it in the body or footer:
-```
+
+```text
 feat(add-auth): implement OAuth2 callback
 
 Refs: ENG-1234
@@ -78,6 +80,7 @@ git push -u origin <branch>
 ```
 
 Then open a PR via the `gh` CLI or the GitHub web UI:
+
 ```bash
 gh pr create --title "<title>" --body "<description>"
 ```

package/core/templates/ai-context.md

@@ -35,7 +35,7 @@ generated_at: "{ISO_TIMESTAMP}"
 
 ## Component Graph
 
-```
+```json
 {project_root}/
 ├── {module1}/ ← {5-10 word description}
 │ ├── {submod1}/ ← {description} ({Ncc} cc, {Nh} h)
@@ -114,6 +114,7 @@ None ✓
 {One paragraph or bullets explaining how components find each other.}
 
 Key injection points:
+
 - `{token1}`: {what it provides}
 - `{token2}`: {what it provides}
 - `{token3}`: {what it provides}
@@ -144,7 +145,7 @@ interface {ServiceName} {
 
 ## Dependency Graph
 
-```
+```json
 [{Component}] -> (HTTP) -> [{ExternalService}]
 [{Component}] -> (SQL) -> [{Database}]
 [{Component}] -> (gRPC) -> [{PeerService}]

package/core/templates/ai-profile.md

@@ -9,12 +9,14 @@ generated_at: "{ISO_TIMESTAMP}"
 # {PROJECT_NAME} Profile
 
 ## Project
+
 - Name: {PROJECT_NAME}
 - One-liner: {ONE_LINE_PRODUCT_DESCRIPTION}
 - Primary users: {USER_TYPES}
 - Repository layout: {monorepo|polyrepo|single-service}
 
 ## Stack
+
 - Language: {LANGUAGE}
 - Framework: {FRAMEWORK}
 - Database: {DATABASE}
@@ -26,17 +28,22 @@ generated_at: "{ISO_TIMESTAMP}"
 - Entry: {ENTRY_POINT}
 
 ## INVARIANTS
+
 {Top 3-5 critical invariants from .ai-context.md, one per line, with file:line refs}
 
 ## NEVER
+
 {2-3 safety rules — things that must never happen}
 
 ## Key Operational Models (from §6 / GRAPH:OPERATIONAL)
+
 - {Most critical flow 1 — one line}
 - {Most critical flow 2 (if space allows)}
 
 ## Active Tracks
+
 {List of active track IDs and one-line descriptions, or "none"}
 
 ## Recent Changes
+
 {Last 3-5 significant commits or changes, one per line}

package/core/templates/architecture.md

@@ -79,6 +79,7 @@ The Graph Health & Fidelity Dashboard (above) is the first artifact any reader o
 The longest and most precise section.
 
 Every invariant must include:
+
 - Precise statement
 - Why violation is dangerous
 - Enforcement mechanism (test, runtime, type system, review, graph constraint, or none)
@@ -86,7 +87,7 @@ Every invariant must include:
 
 Example format:
 
-```
+```text
 ### INV-003: Sentinel Lock Ordering
 **Rule**: `_strategies_lock < _strategy_process_locks < _global_capacity_lock < entry_lock`
 **Fidelity**: High (enforced in code + tests)
@@ -106,6 +107,7 @@ Focus on the highest-value dynamic behavior:
 - Lifecycle sequences (bootstrap, shutdown, reconciliation, failover)
 
 Each backed by:
+
 - Graph-derived paths where available
 - High-quality Mermaid (stateDiagram-v2, sequenceDiagram, or detailed flowchart)
 - Explicit note when the flow is only partially visible in the graph
@@ -135,6 +137,7 @@ Include a short "graph coverage for this view" paragraph.
 ## 6. Error Handling & Failure Mode Catalog
 
 For every major component or flow:
+
 - What can go wrong
 - How it is detected
 - The defined safe response
@@ -145,6 +148,7 @@ For every major component or flow:
 ## 7. State & Data Truth Sources + Reconciliation
 
 For each major domain:
+
 - Authoritative source
 - Derived / cached views
 - Reconciliation mechanisms and lag tolerance
@@ -201,4 +205,4 @@ AI agents are trained by the document itself to treat Stub and Human Judgment cl
 
 **End of clean graph-primary architecture template.**
 
-This is the single forward-looking source of truth. Legacy 28-section volume-oriented material has been retired.
+This is the single forward-looking source of truth. Legacy 28-section volume-oriented material has been retired.

package/core/templates/discovery.md

@@ -67,7 +67,7 @@ track ID, or `_NONE_FOUND_` with justification.
 
 Flat list of files and functions touched in the spike. Files cited here
 without line numbers are exempt from drift checks (they document
-*familiarity*, not pinned facts).
+_familiarity_, not pinned facts).
 
 - _TBD_reference_1_path_ — _TBD_reference_1_symbol_ — _TBD_reference_1_role_
 - _TBD_reference_2_path_ — _TBD_reference_2_symbol_ — _TBD_reference_2_role_

package/core/templates/guardrails.md

@@ -32,21 +32,25 @@ Run `/draft:learn` to scan the codebase and update learned patterns. Quality com
 <!-- Hard constraints that must never be violated. Check [x] to enable enforcement. -->
 
 ### Git & Version Control
+
 - [ ] No direct commits to main/master
 - [ ] No force push to shared branches
 - [ ] PR required for all changes
 
 ### Code Quality
+
 - [ ] No console.log/print statements in production code
 - [ ] No commented-out code blocks
 - [ ] No TODO comments without linked issue
 
 ### Security
+
 - [ ] No secrets/credentials in code
 - [ ] No disabled security checks without documented exception
 - [ ] Dependencies must pass security audit
 
 ### Testing
+
 - [ ] Tests required before merge
 - [ ] No skipped tests without documented reason
 - [ ] Coverage must not decrease
@@ -67,6 +71,7 @@ Run `/draft:learn` to scan the codebase and update learned patterns. Quality com
 - [x] G1.12: No `shared_ptr` binding to non-trivial objects (EventDriver holders) in callbacks
 
 ### C++/Systems — Concurrency & Locking
+
 - [x] G2.1: No mutable operations under shared/read locks
 - [x] G2.2: Always release spinlock before invoking callbacks or `Finish()`
 - [x] G2.3: No expensive object destruction under spinlock protection
@@ -74,12 +79,14 @@ Run `/draft:learn` to scan the codebase and update learned patterns. Quality com
 - [x] G2.5: No synchronous waits (`Trigger::Wait`) in async code paths
 
 ### C++/Systems — Control Flow & Error Handling
+
 - [x] G3.1: Always `return` after `Finish()` in conditional blocks
 - [x] G3.2: CHECKs for internal consistency only — never for external input validation
 - [x] G3.3: No side-effecting expressions inside DCHECK
 - [x] G3.4: CHECK/DCHECK/LOG(DFATAL) selection per severity matrix
 
 ### C++/Systems — Format & API Correctness
+
 - [x] G4.1: Printf format specifiers must match argument types
 - [x] G4.2: MemTracer Print vs Printf selection (lazy construction vs immediate materialization)
 - [x] G4.3: Use Maybe-prefixed MemTracer variants only when op may be finished
@@ -87,9 +94,11 @@ Run `/draft:learn` to scan the codebase and update learned patterns. Quality com
 - [x] G4.5: `boost::optional<bool>` tests presence, not value — use `*xx` or `.value_or()`
 
 ### C++/Systems — GFlags & Runtime Configuration
+
 - [x] G5.1: Snapshot gflag values at op start — never depend on flag stability mid-op
 
 ### C++/Systems — Performance
+
 - [x] G6.1: Avoid `ByteSize()` on proto objects in hot paths
 - [x] G6.2: Prefer repeated fields over map fields in proto for serialization-sensitive paths
 - [x] G6.3: No inline execution in `SpawnWorkersAndJoin` `done_cb`

package/core/templates/hld.md

@@ -194,9 +194,9 @@ For each component, populate one subsection:
 
 Provide a brief list and summary of all inventions associated with the proposed design.
 
-1. 
-2. 
-3. 
+1.
+2.
+3.
 
 **Were Invention Disclosure Forms (IDFs) submitted for the inventions listed?**
 
@@ -208,6 +208,7 @@ Provide a brief list and summary of all inventions associated with the proposed
 ### Third Party Technology (TPT)
 
 **TPT includes:**
+
 - **Open Source Software (OSS):** Software licensed under an Open Source License (e.g., MIT, BSD, GPL, Apache)
 - **Commercial (non-OSS) Technology:** Non- software, documentation, content, APIs, SDKs, logos, artwork, data, GUIs, Tools, databases, and other intellectual property NOT licensed under an Open Source License
 
@@ -289,7 +290,7 @@ Provide a brief list and summary of all inventions associated with the proposed
 
 ### Cost Implications <!-- REQUIRED -->
 
-*Primarily for SaaS deployments*
+_Primarily for SaaS deployments_
 
 - Include cloud cost calculation here
 - Is there any cost to the customer for cloud workloads?