@exaudeus/workrail 3.67.0 → 3.68.1

package/docs/plans/workflow-staleness-detection.md

@@ -11,7 +11,7 @@ How to automatically detect when a WorkRail workflow has become stale — out of
 ### How it works
 
 1. `spec/authoring-spec.json` has a `version` field (currently `3`). This is the staleness anchor.
-2. `workflow-for-workflows` stamps `validatedAgainstSpecVersion: <N>` into the workflow JSON at Phase 7 handoff (after the quality gate passes).
+2. `wr.workflow-for-workflows` stamps `validatedAgainstSpecVersion: <N>` into the workflow JSON at Phase 7 handoff (after the quality gate passes).
 3. At `list_workflows` and `inspect_workflow` time, the engine reads the stamp and compares it against the current spec version.
 4. The output schema gains a `staleness` field: `{ level: 'none' | 'possible' | 'likely', reason: string, specVersionAtLastReview?: number }`.
 
@@ -21,7 +21,7 @@ How to automatically detect when a WorkRail workflow has become stale — out of
 |---|---|---|
 | `none` | `validatedAgainstSpecVersion` matches current spec version | Workflow was reviewed against current guidance |
 | `likely` | `validatedAgainstSpecVersion` < current spec version | Spec updated since last review — workflow may need attention |
-| `possible` | No stamp present | Workflow was not created/reviewed via workflow-for-workflows |
+| `possible` | No stamp present | Workflow was not created/reviewed via wr.workflow-for-workflows |
 
 ### Surfacing
 
@@ -30,7 +30,7 @@ How to automatically detect when a WorkRail workflow has become stale — out of
 
 ### What clears the flag
 
-Running `workflow-for-workflows` on the workflow and committing the result. The Phase 7 step stamps the current spec version. No other action required.
+Running `wr.workflow-for-workflows` on the workflow and committing the result. The Phase 7 step stamps the current spec version. No other action required.
 
 ## Implementation Scope
 
@@ -38,7 +38,7 @@ Running `workflow-for-workflows` on the workflow and committing the result. The
 |---|---|
 | `spec/workflow.schema.json` | Add optional `validatedAgainstSpecVersion?: number` field |
 | `spec/authoring-spec.json` | Add explicit bump trigger to `changeProtocol`; add `changelog` array |
-| `workflow-for-workflows.v2.json` | Phase 7: stamp `validatedAgainstSpecVersion` after quality gate passes; note stamp must be committed |
+| `wr.workflow-for-workflows.v2.json` | Phase 7: stamp `validatedAgainstSpecVersion` after quality gate passes; note stamp must be committed |
 | `src/mcp/output-schemas.ts` | Add `staleness?` to `V2WorkflowListItemSchema` and `V2WorkflowInspectOutputSchema` |
 | `src/mcp/handlers/v2-workflow.ts` | Compute staleness from stamp vs current spec version at list/inspect time |
 | Console | Staleness indicator in workflow list; `likely` > `possible` visual hierarchy |
@@ -47,19 +47,19 @@ Running `workflow-for-workflows` on the workflow and committing the result. The
 
 - Must not block workflow execution
 - Must not require per-workflow manual maintenance
-- No auto-fixing (that's workflow-for-workflows territory)
+- No auto-fixing (that's wr.workflow-for-workflows territory)
 - No mass migration — bootstrap via organic adoption
 
 ## Required Companion Changes (must ship with the feature)
 
 1. **`authoring-spec.json` `changeProtocol`**: add "Increment `version` when any required-level rule is added, removed, or materially changed."
 2. **`authoring-spec.json` `changelog`**: add a `changelog` array so the `reason` string in staleness output can reference what changed.
-3. **`workflow-for-workflows` Phase 7**: add note — "The `validatedAgainstSpecVersion` field was written to the workflow file — commit it for the staleness signal to take effect."
+3. **`wr.workflow-for-workflows` Phase 7**: add note — "The `validatedAgainstSpecVersion` field was written to the workflow file — commit it for the staleness signal to take effect."
 
 ## Accepted Tradeoffs
 
 - Existing unstamped workflows show `possible` permanently until reviewed — acceptable, `possible` is the correct coarse signal for unreviewed workflows
-- External workflows not using workflow-for-workflows may never get stamped — acceptable, same reason
+- External workflows not using wr.workflow-for-workflows may never get stamped — acceptable, same reason
 - Spec version granularity: a spec update touching one archetype flags all workflows — mitigated by changelog + specific reason string
 
 ## Residual Risks
@@ -69,12 +69,12 @@ Running `workflow-for-workflows` on the workflow and committing the result. The
 
 ## Switch Trigger
 
-If teams rarely run workflow-for-workflows and `possible` becomes permanent noise for 80%+ of workflows, add a CI step that stamps workflows automatically.
+If teams rarely run wr.workflow-for-workflows and `possible` becomes permanent noise for 80%+ of workflows, add a CI step that stamps workflows automatically.
 
 ## Decision Log
 
 - **Candidate A (git-date inference) rejected**: CI-noise failure mode disqualifying; no actionable reason string; not deterministic.
 - **Candidate C (hybrid) rejected**: complexity; git-date fallback inherits A's wallpaper problem.
-- **Candidate B selected**: deterministic, architectural fix, self-clearing via workflow-for-workflows, follows `workflowHash` pattern.
+- **Candidate B selected**: deterministic, architectural fix, self-clearing via wr.workflow-for-workflows, follows `workflowHash` pattern.
 - **Challenge**: spec version too coarse. Mitigated by changelog + reason string. Position held.
 - **Review**: no direction change. Three companion changes required pre-ship.

package/docs/plans/workrail-platform-vision.md

@@ -75,7 +75,7 @@ Users should be able to use WorkRail at any level without understanding the leve
 
 - Create a workflow from scratch for a recurring task.
 - Full access to all features (loops, fragments, references, delegation).
-- Use the workflow-for-workflows or author manually.
+- Use the wr.workflow-for-workflows or author manually.
 - **Requirement**: strong authoring spec, good examples, validation tooling.
 
 ### Level 4: Distribute workflows
@@ -124,7 +124,7 @@ Available Workflows:
 
 ## WorkRail Built-in
 - coding-task-agentic: Lean Coding Task
-- workflow-for-workflows: Workflow Authoring
+- wr.workflow-for-workflows: Workflow Authoring
 
 ## monorepo (repo-level)
 - ci-release: CI Release Flow
@@ -261,7 +261,7 @@ Package-bundled references (schema, authoring spec, setup guide) are also expose
 
 ### Now: JSON + agent-assisted
 
-JSON remains the engine format. The workflow-for-workflows helps authors create workflows through structured agent guidance. The authoring spec and schema define correctness.
+JSON remains the engine format. The wr.workflow-for-workflows helps authors create workflows through structured agent guidance. The authoring spec and schema define correctness.
 
 ### Next: Markdown authoring
 

package/docs/reference/agent-context-cleaner-snippet.md

@@ -55,7 +55,7 @@ function cleanContextForWorkflowNext(
 ```typescript
 // During your workflow execution:
 const response = await workflow_next({
-  workflowId: "coding-task-workflow-agentic",
+  workflowId: "wr.coding-task",
   completedSteps: ["phase-6-prep"],
   context: cleanContextForWorkflowNext(fullContext, [
     'featureBranch',      // I created this

package/docs/reference/agent-context-guidance.md

@@ -10,7 +10,7 @@ Agents currently send back the ENTIRE context (15-20KB) on every `workflow_next`
 
 ```json
 {
-  "workflowId": "coding-task-workflow-agentic",
+  "workflowId": "wr.coding-task",
   "completedSteps": ["phase-6-prep"],
   "context": {
     // All 17KB of data including:
@@ -28,7 +28,7 @@ Agents currently send back the ENTIRE context (15-20KB) on every `workflow_next`
 
 ```json
 {
-  "workflowId": "coding-task-workflow-agentic", 
+  "workflowId": "wr.coding-task", 
   "completedSteps": ["phase-6-prep"],
   "context": {
     // Only what you need or changed:
@@ -84,7 +84,7 @@ Never send these back:
 
 ```json
 {
-  "workflowId": "coding-task-workflow-agentic",
+  "workflowId": "wr.coding-task",
   "completedSteps": ["phase-6-prep", "phase-6-implement"],
   "context": {
     "currentStep": { /* current */ },
@@ -100,7 +100,7 @@ Never send these back:
 
 ```json
 {
-  "workflowId": "coding-task-workflow-agentic",
+  "workflowId": "wr.coding-task",
   "completedSteps": ["phase-2-informed-clarification"],
   "context": {
     "clarifiedRequirements": "Updated requirements...", // MODIFIED

package/docs/reference/context-optimization.md

@@ -17,7 +17,7 @@ The MCP server is **completely stateless**. This means:
 ### Before Optimization
 ```json
 {
-      "workflowId": "coding-task-workflow-agentic",
+      "workflowId": "wr.coding-task",
   "completedSteps": ["phase-1", "phase-2"],
   "context": {
     // 17KB of accumulated state including:
@@ -35,7 +35,7 @@ The MCP server is **completely stateless**. This means:
 ### After Optimization
 ```json
 {
-      "workflowId": "coding-task-workflow-agentic",
+      "workflowId": "wr.coding-task",
   "completedSteps": ["phase-1", "phase-2", "phase-3"],
   "context": {
     // Only what's needed for the next step:

package/docs/roadmap/now-next-later.md

@@ -57,8 +57,8 @@ Lightweight cross-cutting roadmap. **This is the single entry point** -- check h
 - ~~**Top-level runCondition tracing**~~ -- `nextTopLevel()` now emits `evaluated_condition` trace entries for each step, explaining why sparse DAGs jump from phase 0 to phase 6; `formatConditionTrace()` produces `SKIP: taskComplexity (equals)` / `PASS: taskComplexity=Medium (not_equals: Small)`
 - ~~**Filter chips cross-contamination fix**~~ -- selecting a source no longer hides/changes tag pill counts; `sourceFilteredWorkflows` / `tagFilteredWorkflows` added to ViewModel state
 - ~~**Windows CI fix**~~ -- duplicate `createFakeStdout` declaration in shutdown-hooks.test.ts resolved; unblocked release pipeline
-- ~~**Trial the quality gate and readiness audit**~~ -- `workflow-for-workflows.v2.json` and `production-readiness-audit.json` exercised extensively on the MVI refactor and MCP stability work; STANDARD/THOROUGH depth validated
-- ~~**Assessment-gate adoption in mr-review-workflow**~~ -- `mr-review-workflow.agentic.v2.json` already has assessmentRefs/assessmentConsequences alongside `bug-investigation`, `coding-task-workflow-agentic.lean.v2`, and `workflow-for-workflows.v2`
+- ~~**Trial the quality gate and readiness audit**~~ -- `wr.workflow-for-workflows.v2.json` and `wr.production-readiness-audit.json` exercised extensively on the MVI refactor and MCP stability work; STANDARD/THOROUGH depth validated
+- ~~**Assessment-gate adoption in mr-review-workflow**~~ -- `mr-review-workflow.agentic.v2.json` already has assessmentRefs/assessmentConsequences alongside `bug-investigation`, `wr.coding-task.lean.v2`, and `wr.workflow-for-workflows.v2`
 - ~~**Console CPU spiral**~~ -- all three fixes shipped: `change` SSE events no longer invalidate worktrees, enrichWorktree semaphore MAX=8, fs.watch filtered to `.jsonl` writes
 - ~~**Console MVI architecture**~~ -- all 6 views refactored to Repository → UseCases → Reducer → ViewModel → pure presenter; 290+ new tests; `console/CLAUDE.md` documents the pattern (#332)
 - ~~**MCP server stability**~~ -- `wireStdoutShutdown` (EPIPE crash), `clearIfStaleLock` (stale lock after crash), `HttpServer.stop()` idempotency, port exhaustion graceful degradation (#332, #335)

package/docs/roadmap/open-work-inventory.md

@@ -162,7 +162,7 @@ For explicit status on the major older planning docs themselves, see `docs/roadm
   - shared `resolveRefsAndBuildEnvelope` helper, parallel resolution, discriminated union types
 - **What remains**:
   - project-attached references via `.workrail/references.json` with drift detection (future)
-  - validate more real bundled workflows with `references`, beyond the newly added `production-readiness-audit.json` rubric reference
+  - validate more real bundled workflows with `references`, beyond the newly added `wr.production-readiness-audit.json` rubric reference
 - **Source doc**: `docs/plans/content-coherence-and-references.md`
 
 ### Authorable response supplements
@@ -201,9 +201,9 @@ For explicit status on the major older planning docs themselves, see `docs/roadm
 
 - **Status**: partial / in progress
 - **Recently shipped**:
-  - `workflows/workflow-for-workflows.v2.json` now supports both creating a new workflow and modernizing an existing one (`#152`, from issue `#151`)
-  - `workflows/workflow-for-workflows.v2.json` has now also been redesigned into a deeper workflow-quality gate with explicit effectiveness targeting, quality architecture, state-economy audit, execution simulation, adversarial review, redesign looping, and final trust handoff
-  - `workflows/production-readiness-audit.json` was added and then tightened into an evidence-driven readiness review with readiness hypothesis, neutral fact packet, reviewer families, contradiction handling, blind-spot confidence capping, and explicit `security_performance` coverage
+  - `workflows/wr.workflow-for-workflows.v2.json` now supports both creating a new workflow and modernizing an existing one (`#152`, from issue `#151`)
+  - `workflows/wr.workflow-for-workflows.v2.json` has now also been redesigned into a deeper workflow-quality gate with explicit effectiveness targeting, quality architecture, state-economy audit, execution simulation, adversarial review, redesign looping, and final trust handoff
+  - `workflows/wr.production-readiness-audit.json` was added and then tightened into an evidence-driven readiness review with readiness hypothesis, neutral fact packet, reviewer families, contradiction handling, blind-spot confidence capping, and explicit `security_performance` coverage
 - **Active focus now**:
   - validate the redesigned quality gate and readiness audit on real tasks, then tune `STANDARD` vs `THOROUGH` depth and ceremony from evidence
   - next highest-value modernization candidate remains `workflows/exploration-workflow.json`
@@ -220,27 +220,27 @@ For explicit status on the major older planning docs themselves, see `docs/roadm
   - tighter loop-control wording and newer evidence-oriented review / verification structure
 - **Highest-priority bundled workflows to revamp**:
   - `workflows/exploration-workflow.json`
-  - `workflows/adaptive-ticket-creation.json`
+  - `workflows/wr.adaptive-ticket-creation.json`
   - `workflows/mr-review-workflow.json`
   - `workflows/mr-review-workflow.agentic.json`
   - `workflows/bug-investigation.json`
   - `workflows/bug-investigation.agentic.json`
   - `workflows/design-thinking-workflow.json`
   - `workflows/design-thinking-workflow-autonomous.agentic.json`
-  - `workflows/documentation-update-workflow.json`
-  - `workflows/document-creation-workflow.json`
+  - `workflows/wr.documentation-update.json`
+  - `workflows/wr.document-creation.json`
 - **Additional older bundled workflows to review for modernization**:
-  - `workflows/intelligent-test-case-generation.json`
+  - `workflows/wr.intelligent-test-case-generation.json`
   - `workflows/learner-centered-course-workflow.json`
-  - `workflows/presentation-creation.json`
-  - `workflows/personal-learning-materials-creation-branched.json`
-  - `workflows/scoped-documentation-workflow.json`
-  - `workflows/relocation-workflow-us.json`
-  - `workflows/workflow-diagnose-environment.json`
+  - `workflows/wr.presentation-creation.json`
+  - `workflows/wr.personal-learning-materials.json`
+  - `workflows/wr.scoped-documentation.json`
+  - `workflows/wr.relocation-us.json`
+  - `workflows/wr.diagnose-environment.json`
 - **Lower priority / already more modern**:
-  - `workflows/coding-task-workflow-agentic.v2.json` — superseded by the lean v2 variant as the current modern example
-  - `workflows/workflow-for-workflows.json` — older large-form version; `workflow-for-workflows.v2.json` is now the deeper quality-gate path
-  - `workflows/cross-platform-code-conversion.v2.json` — already v2 and already uses several modern authoring features
+  - `workflows/wr.coding-task.v2.json` — superseded by the lean v2 variant as the current modern example
+  - `workflows/wr.workflow-for-workflows.json` — older large-form version; `wr.workflow-for-workflows.v2.json` is now the deeper quality-gate path
+  - `workflows/wr.cross-platform-code-conversion.v2.json` — already v2 and already uses several modern authoring features
   - `workflows/bug-investigation.agentic.v2.json`
   - `workflows/mr-review-workflow.agentic.v2.json`
 - **What “modernization” should mean here**:

package/docs/workflows.md

@@ -24,14 +24,14 @@ WorkRail includes **20 production workflows** across multiple categories.
 
 Feature implementation and coding workflows
 
-### `coding-task-workflow-agentic`
+### `wr.coding-task`
 
 **Agentic Task Dev Workflow (Lean • Notes-First • WorkRail Executor)** (v1.0.0)
 
 The user guides the agent through understanding the task, selecting an approach, planning in slices, implementing incrementally, and verifying the result through explicit review and validation checkpoints.
 
 - **Steps**: 12
-- **File**: `workflows/coding-task-workflow-agentic.lean.v2.json`
+- **File**: `workflows/wr.coding-task.lean.v2.json`
 
 ## Debugging
 
@@ -46,7 +46,7 @@ A systematic bug investigation workflow that finds the true source of bugs throu
 - **Steps**: 10
 - **File**: `workflows/bug-investigation.json`
 
-### `bug-investigation-agentic`
+### `wr.bug-investigation`
 
 **Bug Investigation (v2 • Notes-First • WorkRail Executor)** (v2.0.0)
 
@@ -68,7 +68,7 @@ An adaptive workflow to guide an AI agent in performing a comprehensive code rev
 - **Steps**: 10
 - **File**: `workflows/mr-review-workflow.json`
 
-### `mr-review-workflow-agentic`
+### `wr.mr-review`
 
 **MR Review Workflow (v2 • Notes-First • Parallel Reviewer Families)** (v2.1.0)
 
@@ -81,45 +81,45 @@ A v2-first MR review workflow that uses a shared fact packet, parallel reviewer
 
 Creating and maintaining documentation
 
-### `document-creation-workflow`
+### `wr.document-creation`
 
 **Document Creation Workflow** (v0.0.1)
 
-Create BROAD or COMPREHENSIVE documentation spanning multiple components/systems. Perfect for: project READMEs, complete API documentation, user guides covering multiple features, technical specifications for systems. Uses complexity triage (Simple/Standard/Complex) to adapt rigor. For SINGLE, BOUNDED subjects (one class, one integration), use scoped-documentation-workflow instead for better scope discipline.
+Create BROAD or COMPREHENSIVE documentation spanning multiple components/systems. Perfect for: project READMEs, complete API documentation, user guides covering multiple features, technical specifications for systems. Uses complexity triage (Simple/Standard/Complex) to adapt rigor. For SINGLE, BOUNDED subjects (one class, one integration), use wr.scoped-documentation instead for better scope discipline.
 
 - **Steps**: 11
-- **File**: `workflows/document-creation-workflow.json`
+- **File**: `workflows/wr.document-creation.json`
 
-### `documentation-update-workflow`
+### `wr.documentation-update`
 
 **Documentation Update & Maintenance Workflow** (v1.0.0)
 
-UPDATE and MAINTAIN existing documentation. Analyzes Git history to detect staleness, identifies outdated sections, and systematically refreshes docs while preserving valuable content. Perfect for: refreshing docs after code changes, scheduled maintenance, addressing feedback. NOT for creating new docs - use scoped-documentation-workflow or document-creation-workflow for new documentation.
+UPDATE and MAINTAIN existing documentation. Analyzes Git history to detect staleness, identifies outdated sections, and systematically refreshes docs while preserving valuable content. Perfect for: refreshing docs after code changes, scheduled maintenance, addressing feedback. NOT for creating new docs - use wr.scoped-documentation or wr.document-creation for new documentation.
 
 - **Steps**: 15
-- **File**: `workflows/documentation-update-workflow.json`
+- **File**: `workflows/wr.documentation-update.json`
 
-### `scoped-documentation-workflow`
+### `wr.scoped-documentation`
 
 **Scoped Documentation Workflow** (v1.0.0)
 
-Create documentation for a SINGLE, BOUNDED subject with strict scope enforcement. Perfect for: one class/component, one integration point, one mechanism, one architecture decision. Prevents documentation sprawl through continuous boundary validation (9+/10 scope compliance required). NOT for: project READMEs, multi-component systems, or comprehensive guides - use document-creation-workflow for those.
+Create documentation for a SINGLE, BOUNDED subject with strict scope enforcement. Perfect for: one class/component, one integration point, one mechanism, one architecture decision. Prevents documentation sprawl through continuous boundary validation (9+/10 scope compliance required). NOT for: project READMEs, multi-component systems, or comprehensive guides - use wr.document-creation for those.
 
 - **Steps**: 10
-- **File**: `workflows/scoped-documentation-workflow.json`
+- **File**: `workflows/wr.scoped-documentation.json`
 
 ## Exploration & Analysis
 
 Understanding codebases and systems
 
-### `adaptive-ticket-creation`
+### `wr.adaptive-ticket-creation`
 
 **Adaptive Ticket Creation Workflow** (v0.1.0)
 
 An intelligent workflow for creating high-quality Jira tickets. Uses LLM-driven path selection to automatically choose between Simple, Standard, or Epic complexity paths based on request analysis.
 
 - **Steps**: 9
-- **File**: `workflows/adaptive-ticket-creation.json`
+- **File**: `workflows/wr.adaptive-ticket-creation.json`
 
 ### `wr.discovery`
 
@@ -130,20 +130,20 @@ A bundled upstream thinking workflow that merges the old exploration and design-
 - **Steps**: 12
 - **File**: `workflows/wr.discovery.json`
 
-### `intelligent-test-case-generation`
+### `wr.intelligent-test-case-generation`
 
 **Intelligent Test Case Generation from Tickets** (v0.0.1)
 
 Transforms ticket requirements into systematic test cases using evidence-driven analysis, dual-brain processing (NLP + LLM), document discovery, and progressive scenario expansion. Produces integration and end-to-end tests optimized for developer readability and LLM consumption with confidence scoring and validation loops.
 
 - **Steps**: 12
-- **File**: `workflows/intelligent-test-case-generation.json`
+- **File**: `workflows/wr.intelligent-test-case-generation.json`
 
 ## Learning & Education
 
 Course design and learning materials
 
-### `personal-learning-course-design`
+### `wr.personal-learning-course-design`
 
 **Personal Learning Course Design Workflow** (v1.0.0)
 
@@ -152,36 +152,36 @@ A systematic workflow for designing effective personal learning courses with thr
 - **Steps**: 11
 - **File**: `workflows/learner-centered-course-workflow.json`
 
-### `personal-learning-materials-creation-branched`
+### `wr.personal-learning-materials`
 
 **Personal Learning Materials Creation Workflow (Branched)** (v1.0.0)
 
 A systematic workflow for creating high-quality learning materials with three thoroughness paths: Quick Start (essential materials), Balanced (comprehensive system), and Comprehensive (enterprise-grade). Adapts depth and features based on user time constraints and quality goals.
 
 - **Steps**: 6
-- **File**: `workflows/personal-learning-materials-creation-branched.json`
+- **File**: `workflows/wr.personal-learning-materials.json`
 
-### `presentation-creation`
+### `wr.presentation-creation`
 
 **Dynamic Presentation Creation Workflow** (v0.1.0)
 
 A comprehensive workflow for creating dynamic, interesting, and insightful presentations. Guides users through audience analysis, content strategy, visual design, and delivery preparation to create compelling presentations that engage and inform.
 
 - **Steps**: 9
-- **File**: `workflows/presentation-creation.json`
+- **File**: `workflows/wr.presentation-creation.json`
 
 ## Other
 
 Miscellaneous workflows
 
-### `cross-platform-code-conversion`
+### `wr.cross-platform-code-conversion`
 
 **Cross-Platform Code Conversion** (v0.1.0)
 
 Guides an agent through converting code from one platform to another (e.g., Android to iOS, iOS to Web). Triages files by difficulty, delegates easy literal translations to parallel subagents, then the main agent tackles platform-specific code requiring design decisions.
 
 - **Steps**: 9
-- **File**: `workflows/cross-platform-code-conversion.v2.json`
+- **File**: `workflows/wr.cross-platform-code-conversion.v2.json`
 
 ### `design-thinking-workflow`
 
@@ -201,32 +201,32 @@ Autonomous design thinking: minimal human input; doc-first execution; supports A
 - **Steps**: 16
 - **File**: `workflows/design-thinking-workflow-autonomous.agentic.json`
 
-### `relocation-workflow-us`
+### `wr.relocation-us`
 
 **Relocation Decision Workflow (US v1 — AreaSpec • Custom Areas • Dossier • Evidence • Ranking)** (v0.2.0)
 
 A bias-resistant, evidence-driven relocation workflow for the United States. Helps users discover what they care about, generate a broad candidate pool (including optional custom areas), screen it with strict caps, deep-dive shortlisted areas, and produce a master dossier plus per-location profile docs with a transparent, explainable weighted ranking.
 
 - **Steps**: 19
-- **File**: `workflows/relocation-workflow-us.json`
+- **File**: `workflows/wr.relocation-us.json`
 
-### `workflow-diagnose-environment`
+### `wr.diagnose-environment`
 
 **Diagnostic: Environment & Subagents** (v1.0.0)
 
 Automated capability detection for Agentic IDEs. Probes for subagent access and generates a local configuration file.
 
 - **Steps**: 2
-- **File**: `workflows/workflow-diagnose-environment.json`
+- **File**: `workflows/wr.diagnose-environment.json`
 
-### `workflow-for-workflows`
+### `wr.workflow-for-workflows`
 
 **Workflow Authoring Workflow (Lean, References-First)** (v2.0.0)
 
 Guides an agent through creating a new WorkRail workflow: understand the task, choose the shape, draft the JSON, validate with real validators, review the method, and optionally refine.
 
 - **Steps**: 8
-- **File**: `workflows/workflow-for-workflows.v2.json`
+- **File**: `workflows/wr.workflow-for-workflows.v2.json`
 
 ---
 
@@ -236,7 +236,7 @@ Tell your AI agent which workflow to use:
 
 ```
 "Use the bug-investigation workflow to debug this issue"
-"Use the coding-task-workflow-agentic to implement this feature"
+"Use the wr.coding-task to implement this feature"
 ```
 
 Or browse programmatically:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@exaudeus/workrail",
-  "version": "3.67.0",
+  "version": "3.68.1",
   "description": "Step-by-step workflow enforcement for AI agents via MCP",
   "license": "MIT",
   "repository": {