@lumenflow/cli 3.10.1 → 3.11.1

package/templates/core/ai/onboarding/vendor-support.md.template

@@ -187,31 +187,25 @@ pnpm wu:claim --id WU-XXX --lane "<Lane>" --cloud
 LUMENFLOW_CLOUD=1 pnpm wu:claim --id WU-XXX --lane "<Lane>"
 ```
 
-Explicit activation (`--cloud` or `LUMENFLOW_CLOUD=1`) always takes precedence over
-auto-detection.
+Cloud activation is explicit-only. `--cloud` and `LUMENFLOW_CLOUD=1` are the only
+runtime activation paths.
 
-### Config-Driven Auto-Detection (Opt-In)
+### Cloud Config Compatibility Fields
 
-For environments where agents should automatically enter cloud mode, enable
-auto-detection in `workspace.yaml`:
+The workspace schema still carries `cloud.auto_detect` and `env_signals`, but they do
+not activate cloud mode at runtime:
 
 ```yaml
 cloud:
-  auto_detect: true # default: false
-  env_signals:
-    - name: CI # presence check (any non-empty value)
-    - name: CODEX
-    - name: GITHUB_ACTIONS
-      equals: 'true' # exact match required
+  auto_detect: false
+  env_signals: []
 ```
 
 **Key design decisions:**
 
-- `auto_detect` defaults to `false` (opt-in, not opt-out)
-- No vendor-specific signals are hardcoded; all signals are user-configured
-- Each signal supports either presence checks (`name` only) or exact-value
-  matches (`name` + `equals`)
-- Explicit activation always wins over auto-detection
+- Runtime identity signals are intentionally ignored for activation
+- Explicit activation always wins because it is the only activation path
+- Config fields remain for compatibility, migration, and future policy metadata
 
 ### Cloud Lifecycle
 
@@ -225,10 +219,10 @@ cloud:
 
 ### Vendor-Specific Notes
 
-- **Codex**: Set `LUMENFLOW_CLOUD=1` in the environment or configure auto-detection with `name: CODEX`
-- **Claude web**: Use `--cloud` flag explicitly or configure `name: CLAUDE_CODE` in env_signals
-- **GitHub Actions**: Configure `name: GITHUB_ACTIONS, equals: 'true'` in env_signals
-- **Antigravity**: Expected to work with explicit `--cloud` flag; auto-detection signals TBD
+- **Codex**: Set `LUMENFLOW_CLOUD=1` or pass `--cloud`
+- **Claude web**: Use `--cloud` explicitly
+- **GitHub Actions**: Set `LUMENFLOW_CLOUD=1` in the job environment
+- **Antigravity**: Use explicit `--cloud` activation
 
 ---
 

package/templates/core/ai/onboarding/wu-create-checklist.md.template

@@ -2,116 +2,65 @@
 
 **Last updated:** {{DATE}}
 
-Before running `pnpm wu:create`, verify these items.
+Use this checklist before running `pnpm wu:create`.
 
 ---
 
-## Step 1: Check Valid Lanes
+## Step 1: Confirm the Lane
 
 ```bash
-grep -A 30 "lanes:" workspace.yaml
+pnpm lane:status
+pnpm wu:infer-lane --paths "packages/@lumenflow/cli/src/init.ts" --desc "Fix init docs drift"
 ```
 
-**Format:** `"Parent: Sublane"` (colon + single space)
-
-Examples:
-
-- `"Framework: CLI"`
-- `"Framework: Core"`
-- `"Operations: CI/CD"`
-- `"Content: Documentation"`
+The lane should match the real implementation scope, not just the first file you noticed.
 
 ---
 
-## Step 2: Required Fields
+## Step 2: Gather the Required Fields
 
-| Field              | Required For | Example                                          |
-| ------------------ | ------------ | ------------------------------------------------ |
-| `--id`             | All          | `WU-1234`                                        |
-| `--lane`           | All          | `"Experience: Chat"`                             |
-| `--title`          | All          | `"Add feature"`                                  |
-| `--description`    | All          | `"Context: ... Problem: ... Solution: ..."`      |
-| `--acceptance`     | All          | `--acceptance "Works"` (repeatable)              |
-| `--exposure`       | All          | `ui`, `api`, `backend-only`, `documentation`     |
-| `--code-paths`     | Code WUs     | `"src/a.ts,src/b.ts"`                            |
-| `--test-paths-unit`| Code WUs     | `"src/__tests__/a.test.ts"`                      |
-| `--spec-refs`      | Feature WUs  | `"lumenflow://plans/WU-XXX-plan.md"`             |
-
----
+| Field                 | Required For          | Example                                                |
+| --------------------- | --------------------- | ------------------------------------------------------ |
+| `--lane`              | All WUs               | `"Framework: CLI"`                                     |
+| `--title`             | All WUs               | `"Eliminate onboarding docs drift"`                    |
+| `--description`       | All WUs               | `"Context: ... Problem: ... Solution: ..."`            |
+| `--acceptance`        | All WUs               | `--acceptance "Docs and templates stay aligned"`       |
+| `--exposure`          | All WUs               | `documentation`                                        |
+| `--code-paths`        | Non-documentation WUs | `"packages/@lumenflow/cli/src/init.ts"`                |
+| `--test-paths-manual` | Non-documentation WUs | `"Run focused init/docs-sync tests"`                   |
+| `--test-paths-unit`   | Code WUs              | `"packages/@lumenflow/cli/src/__tests__/init.test.ts"` |
+| `--spec-refs`         | Feature WUs           | `"lumenflow://plans/WU-XXXX-plan.md"`                  |
 
-## Step 3: Plan Storage
-
-Plans go in `$LUMENFLOW_HOME/plans/` (NOT in project):
-
-```bash
-mkdir -p $LUMENFLOW_HOME/plans
-# or if LUMENFLOW_HOME is not set:
-mkdir -p ~/.lumenflow/plans
-
-# Create your plan
-vim ~/.lumenflow/plans/WU-XXX-plan.md
-```
-
-Reference in wu:create:
-
-```bash
---spec-refs "lumenflow://plans/WU-XXX-plan.md"
-```
+`--id` is optional. If omitted, `wu:create` allocates the next WU ID automatically.
 
 ---
 
-## Step 4: Validate First
+## Step 3: Decide Plan Storage
+
+If the work needs a plan, prefer repo-native or `lumenflow://plans/` references:
 
 ```bash
-pnpm wu:create --id WU-XXX ... --validate
+pnpm plan:create --id INIT-XXX --title "Plan title"
+pnpm wu:create --lane "Framework: CLI" --title "..." --plan
 ```
 
-Fix errors, then remove `--validate` to create.
+Avoid pointing `--spec-refs` at random local filesystem notes that other agents cannot resolve.
 
 ---
 
-## Complete Example
+## Step 4: Validate Before Creating
 
 ```bash
-pnpm wu:create \
-  --id WU-1234 \
-  --lane "Framework: CLI" \
-  --title "Add feature X" \
-  --description "Context: Users need X. Problem: X doesn't exist. Solution: Add X." \
-  --acceptance "Feature X works as specified" \
-  --acceptance "Unit tests pass with >90% coverage" \
-  --code-paths "packages/@lumenflow/cli/src/x.ts" \
-  --test-paths-unit "packages/@lumenflow/cli/__tests__/x.test.ts" \
-  --exposure backend-only \
-  --spec-refs "lumenflow://plans/WU-1234-plan.md"
+pnpm wu:create --lane "Framework: CLI" --title "..." --description "..." \
+  --acceptance "..." --exposure documentation --validate
 ```
 
----
-
-## Common Errors
-
-### "Lane format invalid"
-
-**Cause:** Missing colon or space in lane format.
-
-**Fix:** Use `"Parent: Sublane"` format (colon + space).
-
-### "Missing required field"
-
-**Cause:** Required field not provided.
-
-**Fix:** Add the missing `--field` argument.
-
-### "WU already exists"
-
-**Cause:** WU with this ID already exists.
-
-**Fix:** Use a different ID or check existing WUs.
+Let validation tell you which fields are still missing before you create the real spec.
 
 ---
 
 ## After Creation
 
-1. Review the created YAML: `cat docs/04-operations/tasks/wu/WU-XXX.yaml`
-2. Claim the WU: `pnpm wu:claim --id WU-XXX --lane "Lane"`
-3. cd to worktree: `cd worktrees/<lane>-wu-xxx`
+1. Review `{{DOCS_TASKS_PATH}}/wu/WU-XXX.yaml`.
+2. Claim it with `pnpm wu:claim --id WU-XXX --lane "<Lane>"`.
+3. Move into the worktree immediately.

package/templates/core/ai/onboarding/wu-sizing-guide.md.template

@@ -0,0 +1,48 @@
+# Work Unit Sizing Guide
+
+**Last updated:** {{DATE}}
+
+Use this summary when deciding whether a WU still fits in a single agent session.
+
+---
+
+## Baseline Heuristics
+
+| Complexity | Files | Tool Calls | Suggested Strategy          |
+| ---------- | ----- | ---------- | --------------------------- |
+| Simple     | <20   | <50        | Single session              |
+| Medium     | 20-50 | 50-100     | Checkpoint and resume       |
+| Complex    | 50+   | 100+       | Decompose or orchestrate    |
+| Oversized  | 100+  | 200+       | Split before implementation |
+
+These are guardrails, not a license to keep pushing once context is clearly degrading.
+
+---
+
+## Context Safety Triggers
+
+Checkpoint and hand off when any of these happen:
+
+- Context usage approaches 50% and is still climbing
+- Tool calls exceed roughly 50 in one session
+- File churn keeps widening without clear closure
+- You have to repeatedly rediscover the same repo rules
+
+---
+
+## Recovery Pattern
+
+```bash
+pnpm mem:checkpoint "state before handoff" --wu WU-XXX
+pnpm wu:brief --id WU-XXX --client codex-cli
+```
+
+If the WU is clearly too large, split it instead of relying on a heroic handoff.
+
+---
+
+## Docs-Only Exception
+
+Documentation WUs can tolerate broader file counts when the change pattern is shallow and mechanical, but they still need to stay understandable in one session.
+
+If the docs work starts spilling into CLI, core, or packaging changes, treat it like a normal cross-code WU again.

package/templates/vendors/claude/.claude/skills/bug-classification/SKILL.md.template

@@ -2,7 +2,7 @@
 name: bug-classification
 description: Classify bugs (P0-P3) and determine fix-in-place vs separate Bug WU. Use when bug discovered mid-WU, deciding bug priority, or handling production issues.
 version: 1.0.0
-source: docs/04-operations/_frameworks/lumenflow/lumenflow-agent-capsule.md
+source: {{DOCS_OPERATIONS_PATH}}/_frameworks/lumenflow/lumenflow-agent-capsule.md
 source_sections: §8 (Bug Handling Mid-WU)
 last_updated: {{DATE}}
 allowed-tools: Read, Grep
@@ -189,4 +189,4 @@ blocking: []
 
 ## Reference
 
-See [LumenFlow Agent Capsule](../../../docs/04-operations/_frameworks/lumenflow/lumenflow-agent-capsule.md) for complete bug handling guide.
+See [LumenFlow Agent Capsule](../../../{{DOCS_OPERATIONS_PATH}}/_frameworks/lumenflow/lumenflow-agent-capsule.md) for complete bug handling guide.

package/templates/vendors/claude/.claude/skills/code-quality/SKILL.md.template

@@ -2,7 +2,7 @@
 name: code-quality
 description: Shared patterns for SOLID/DRY code review, hexagonal architecture compliance, TypeScript best practices, and performance anti-patterns. Use when reviewing code quality, checking architecture boundaries, or validating TypeScript patterns.
 version: 1.1.0
-source: docs/04-operations/_frameworks/lumenflow/lumenflow-agent-capsule.md
+source: {{DOCS_OPERATIONS_PATH}}/_frameworks/lumenflow/lumenflow-agent-capsule.md
 source_sections: Core Principles, Hexagonal Architecture
 last_updated: {{DATE}}
 allowed-tools: Read, Grep, Glob
@@ -10,7 +10,7 @@ allowed-tools: Read, Grep, Glob
 
 # Code Quality Skill
 
-**Source**: `docs/04-operations/_frameworks/lumenflow/lumenflow-agent-capsule.md` (canonical)
+**Source**: `{{DOCS_OPERATIONS_PATH}}/_frameworks/lumenflow/lumenflow-agent-capsule.md` (canonical)
 
 ## When to Use
 

package/templates/vendors/claude/.claude/skills/context-management/SKILL.md.template

@@ -2,7 +2,7 @@
 name: context-management
 description: Session checkpoint patterns, output bypass for large results, when to spawn fresh sub-agents. Use for long-running sessions, context exhaustion, or agent coordination.
 version: 1.4.0
-source: docs/04-operations/_frameworks/lumenflow/agent/onboarding/agent-invocation-guide.md
+source: {{DOCS_ONBOARDING_PATH}}/agent-invocation-guide.md
 source_sections: Context Tiers, Session Management, Wave Orchestration
 last_updated: {{DATE}}
 allowed-tools: Read, Write, Bash
@@ -10,7 +10,7 @@ allowed-tools: Read, Write, Bash
 
 # Context Management Skill
 
-**Source**: `docs/04-operations/_frameworks/lumenflow/agent/onboarding/agent-invocation-guide.md`
+**Source**: `{{DOCS_ONBOARDING_PATH}}/agent-invocation-guide.md`
 
 Patterns for managing context in long-running AI coding sessions.
 
@@ -56,7 +56,7 @@ pnpm wu:brief --id WU-XXX --client claude-code
 - Recovery mechanisms are complex and vendor-specific
 - Prevention (fresh agent) is simpler and more reliable than recovery
 
-**This is not failure—it's disciplined execution.** See [wu-sizing-guide.md](../../../docs/04-operations/_frameworks/lumenflow/wu-sizing-guide.md) for complete sizing thresholds.
+**This is not failure—it's disciplined execution.** See [wu-sizing-guide.md](../../../{{DOCS_OPERATIONS_PATH}}/_frameworks/lumenflow/wu-sizing-guide.md) for complete sizing thresholds.
 
 ---
 

package/templates/vendors/claude/.claude/skills/execution-memory/SKILL.md.template

@@ -2,7 +2,7 @@
 name: execution-memory
 description: Memory layer for session tracking, context recovery, and agent coordination. Use when resuming work after /clear, coordinating with parallel agents, or managing long-running sessions.
 version: 1.2.0
-source: docs/04-operations/_frameworks/lumenflow/agent/onboarding/quick-ref-commands.md
+source: {{QUICK_REF_LINK}}
 source_sections: Memory Commands
 last_updated: {{DATE}}
 allowed-tools: Read, Bash, Grep

package/templates/vendors/claude/.claude/skills/initiative-management/SKILL.md.template

@@ -94,7 +94,7 @@ Edits initiative YAML fields atomically using micro-worktree isolation:
 
 ## Initiative Structure
 
-Initiatives are defined in `docs/04-operations/tasks/initiatives/INIT-001.yaml`:
+Initiatives are defined in `{{DOCS_TASKS_PATH}}/initiatives/INIT-001.yaml`:
 
 ```yaml
 id: INIT-001
@@ -157,7 +157,7 @@ pnpm wu:brief --id WU-1504 --evidence-only         # Evidence only, no prompt ou
 - Validation agents checking orchestrator's work
 - Explore agents for codebase research
 
-See [agent-invocation-guide.md](../../../docs/04-operations/_frameworks/lumenflow/agent/onboarding/agent-invocation-guide.md) for decision tree.
+See [agent-invocation-guide.md](../../../{{DOCS_ONBOARDING_PATH}}/agent-invocation-guide.md) for decision tree.
 
 ## Best Practices
 

package/templates/vendors/claude/.claude/skills/library-first/SKILL.md.template

@@ -2,7 +2,7 @@
 name: library-first
 description: Validate well-known libraries solve your problem before custom code. Use when implementing parsing, dates, validation, or any non-trivial logic.
 version: 1.0.0
-source: docs/04-operations/_frameworks/lumenflow/agent/onboarding/library-first-toolkit.md
+source: {{DOCS_ONBOARDING_PATH}}/library-first-toolkit.md
 source_sections: Validation Protocol, Decision Tree, Context7 Query Templates
 last_updated: {{DATE}}
 allowed-tools: Read, mcp__context7__*
@@ -10,7 +10,7 @@ allowed-tools: Read, mcp__context7__*
 
 # Library-First Skill
 
-**Source**: `docs/04-operations/_frameworks/lumenflow/agent/onboarding/library-first-toolkit.md` (canonical)
+**Source**: `{{DOCS_ONBOARDING_PATH}}/library-first-toolkit.md` (canonical)
 
 Search for libraries BEFORE writing custom code. Custom implementations create debt, violate DRY/SOLID, and introduce bugs that libraries have already solved.
 

package/templates/vendors/claude/.claude/skills/lumenflow-gates/SKILL.md.template

@@ -2,7 +2,7 @@
 name: lumenflow-gates
 description: Quality gates troubleshooting (format, lint, typecheck, tests). Use when gates fail, debugging format/lint/typecheck errors, or determining if failure is from your changes vs pre-existing.
 version: 2.1.0
-source: docs/04-operations/_frameworks/lumenflow/lumenflow-agent-capsule.md
+source: {{DOCS_OPERATIONS_PATH}}/_frameworks/lumenflow/lumenflow-agent-capsule.md
 source_sections: Validation & Gates
 last_updated: {{DATE}}
 allowed-tools: Read, Bash, Grep
@@ -10,7 +10,7 @@ allowed-tools: Read, Bash, Grep
 
 # LumenFlow Gates Skill
 
-**Source**: `docs/04-operations/_frameworks/lumenflow/lumenflow-agent-capsule.md` (canonical)
+**Source**: `{{DOCS_OPERATIONS_PATH}}/_frameworks/lumenflow/lumenflow-agent-capsule.md` (canonical)
 
 ## When to Use
 
@@ -84,4 +84,4 @@ pnpm tasks:validate       # WU YAML validation
 
 ---
 
-**Full spec**: [LumenFlow Agent Capsule](../../../docs/04-operations/_frameworks/lumenflow/lumenflow-agent-capsule.md)
+**Full spec**: [LumenFlow Agent Capsule](../../../{{DOCS_OPERATIONS_PATH}}/_frameworks/lumenflow/lumenflow-agent-capsule.md)

package/templates/vendors/claude/.claude/skills/multi-agent-coordination/SKILL.md.template

@@ -2,7 +2,7 @@
 name: multi-agent-coordination
 description: Coordinate multiple agents on parallel WUs using git branch locking. Use when spawning sub-agents, coordinating parallel WUs, or handling abandoned WU recovery.
 version: 2.1.0
-source: docs/04-operations/_frameworks/lumenflow/agent/onboarding/agent-invocation-guide.md
+source: {{DOCS_ONBOARDING_PATH}}/agent-invocation-guide.md
 last_updated: {{DATE}}
 allowed-tools: Read, Bash, Grep
 ---
@@ -87,4 +87,4 @@ pnpm mem:checkpoint "Ready for handoff" --wu WU-XXX  # Handoff
 
 ---
 
-**Full docs**: [agent-invocation-guide.md](../../../docs/04-operations/_frameworks/lumenflow/agent/onboarding/agent-invocation-guide.md) | [execution-memory skill](../execution-memory/SKILL.md)
+**Full docs**: [agent-invocation-guide.md](../../../{{DOCS_ONBOARDING_PATH}}/agent-invocation-guide.md) | [execution-memory skill](../execution-memory/SKILL.md)

package/templates/vendors/claude/.claude/skills/tdd-workflow/SKILL.md.template

@@ -2,7 +2,7 @@
 name: tdd-workflow
 description: Test-driven development workflow. RED-GREEN-REFACTOR applies to all code; 5-step ports-first for hex architecture. Use when implementing new features, writing tests, or working with hexagonal architecture.
 version: 2.1.0
-source: docs/04-operations/_frameworks/lumenflow/lumenflow-agent-capsule.md
+source: {{DOCS_OPERATIONS_PATH}}/_frameworks/lumenflow/lumenflow-agent-capsule.md
 source_sections: AI-TDD 5-Step Workflow, Hexagonal Architecture
 last_updated: {{DATE}}
 allowed-tools: Read, Write, Edit, Bash, Grep
@@ -10,7 +10,7 @@ allowed-tools: Read, Write, Edit, Bash, Grep
 
 # TDD Workflow Skill
 
-**Source**: `docs/04-operations/_frameworks/lumenflow/lumenflow-agent-capsule.md` (canonical)
+**Source**: `{{DOCS_OPERATIONS_PATH}}/_frameworks/lumenflow/lumenflow-agent-capsule.md` (canonical)
 
 ## When to Use
 
@@ -138,4 +138,4 @@ pnpm test:coverage           # Check coverage
 
 ---
 
-**Full spec**: [LumenFlow Agent Capsule](../../../docs/04-operations/_frameworks/lumenflow/lumenflow-agent-capsule.md)
+**Full spec**: [LumenFlow Agent Capsule](../../../{{DOCS_OPERATIONS_PATH}}/_frameworks/lumenflow/lumenflow-agent-capsule.md)

package/templates/vendors/claude/.claude/skills/worktree-discipline/SKILL.md.template

@@ -2,7 +2,7 @@
 name: worktree-discipline
 description: Prevents the "absolute path trap" in Write/Edit/Read tools. Use when working in worktrees, before file operations, or when changes don't appear in git status.
 version: 2.0.0
-source: docs/04-operations/_frameworks/lumenflow/lumenflow-agent-capsule.md
+source: {{DOCS_OPERATIONS_PATH}}/_frameworks/lumenflow/lumenflow-agent-capsule.md
 source_sections: Worktree Discipline, Tool Usage
 last_updated: {{DATE}}
 allowed-tools: Read, Bash, Grep
@@ -25,7 +25,7 @@ allowed-tools: Read, Bash, Grep
 
 // WRONG - Absolute path bypasses worktree
 Write({
-  file_path: '/home/user/source/project/apps/web/src/validator.ts',
+  file_path: '<absolute-path>/apps/web/src/validator.ts',
   content: '...',
 });
 // Result: Written to MAIN checkout, not worktree!
@@ -51,13 +51,13 @@ Write({
 
 2. **Check file path format**:
 
-   | Pattern                           | Safe? | Example                  |
-   | --------------------------------- | ----- | ------------------------ |
-   | Starts with `/home/` or `/Users/` | NO    | `/home/user/.../file.ts` |
-   | Contains full repo path           | NO    | `/source/project/...`    |
-   | Starts with package name          | YES   | `apps/web/src/...`       |
-   | Starts with `./` or `../`         | YES   | `./src/lib/...`          |
-   | Just filename                     | YES   | `README.md`              |
+   | Pattern                             | Safe? | Example                        |
+   | ----------------------------------- | ----- | ------------------------------ |
+   | Starts with an absolute-root prefix | NO    | `<absolute-path>/.../file.ts`  |
+   | Contains full repo path             | NO    | `<repo-root>/apps/.../file.ts` |
+   | Starts with package name            | YES   | `apps/web/src/...`             |
+   | Starts with `./` or `../`           | YES   | `./src/lib/...`                |
+   | Just filename                       | YES   | `README.md`                    |
 
 3. **Use relative paths for ALL file operations**
 
@@ -69,7 +69,7 @@ Write({
 
 **Red flags** (you're about to fall into the trap):
 
-- Path starts with `/home/` or `/Users/`
+- Path starts with an absolute-root prefix
 - Path contains organisation/project name
 - Path length > 50 characters (suspiciously long)
 

package/templates/vendors/claude/.claude/skills/wu-lifecycle/SKILL.md.template

@@ -2,7 +2,7 @@
 name: wu-lifecycle
 description: Work Unit claim/block/done workflow automation. Use when claiming WUs, blocking/unblocking, running wu:prep + wu:done, or understanding WU state transitions.
 version: 2.2.0
-source: docs/04-operations/_frameworks/lumenflow/lumenflow-agent-capsule.md
+source: {{DOCS_OPERATIONS_PATH}}/_frameworks/lumenflow/lumenflow-agent-capsule.md
 source_sections: WU Lifecycle
 last_updated: {{DATE}}
 allowed-tools: Read, Bash, Grep
@@ -10,7 +10,7 @@ allowed-tools: Read, Bash, Grep
 
 # WU Lifecycle Skill
 
-**Source**: `docs/04-operations/_frameworks/lumenflow/lumenflow-agent-capsule.md` (canonical)
+**Source**: `{{DOCS_OPERATIONS_PATH}}/_frameworks/lumenflow/lumenflow-agent-capsule.md` (canonical)
 
 ## When to Use
 
@@ -116,4 +116,4 @@ pnpm wu:done --id WU-XXX --skip-gates --reason "Pre-existing" --fix-wu WU-YYY
 
 ---
 
-**Full spec**: [LumenFlow Agent Capsule](../../../docs/04-operations/_frameworks/lumenflow/lumenflow-agent-capsule.md)
+**Full spec**: [LumenFlow Agent Capsule](../../../{{DOCS_OPERATIONS_PATH}}/_frameworks/lumenflow/lumenflow-agent-capsule.md)