agentera 3.0.0-dev.12 → 3.0.0-dev.14

package/bundle/references/artifacts/artifact-registry-interface-model.yaml

@@ -221,11 +221,11 @@ explicit_special_cases:
       placeholder: '{date}'
       meaning: archive date or archive-safe plan suffix
     docs_yaml_can_override_path: false
-  - artifact_id: optimera_harness
+  - artifact_id: optimize_harness
     display_name: harness
     artifact_type: local_harness
     scope: local_harness
-    default_path: .agentera/optimera/<name>/harness
+    default_path: .agentera/optimize/<name>/harness
     path_template:
       placeholder: <name>
       meaning: active objective directory name

package/bundle/references/cli/capability-instruction-contract.yaml

@@ -29,8 +29,8 @@ current_state:
     definition: >-
       The TypeScript module that exports the capability's behavioral
       instructions as a default-exported string constant. The runtime loads
-      the compiled .js path and serves the prose through the slim
-      `capability_context` capsule's `prose` field.
+      the compiled .js path and serves the instructions through the slim
+      `capability_context` capsule's `instructions` field.
   legacy_instruction_file:
     path: skills/agentera/capabilities/<name>/instructions.md
     status: historical_or_compatibility_evidence_only
@@ -57,8 +57,8 @@ current_state:
     current_behavior: >-
       `agentera prime --context <name> --format json` emits
       `capability_context` metadata including `first_invocation_read`
-      (value: `prime_context`, runtime_enforcement: true) and the full prose
-      in the `prose` field for supported capabilities. Historical
+      (value: `prime_context`, runtime_enforcement: true) and the full instructions
+      in the `instructions` field for supported capabilities. Historical
       `hej --capability-context` is removed in 3.0.
 first_invocation_read:
   field_status: runtime_enforced
@@ -66,21 +66,21 @@ first_invocation_read:
     Capability metadata declaring what instruction content an agent must
     read on the first invocation of that capability in a session. Decision
     65 collapses the legacy `full`/`compact_startup` distinction into a
-    single `prime_context` value because the CLI now owns the prose and
+    single `prime_context` value because the CLI now owns the instructions and
     the runtime can mechanically shell out to the prime command.
   allowed_values:
     prime_context:
       meaning: >-
         The first capability invocation must shell out to
         `agentera prime --context <name> --format json` and read the
-        returned `prose` field (the full Markdown body) before executing
+        returned `instructions` field (the full Markdown body) before executing
         capability-specific work.
       obligation: shell out to agentera prime --context <name> --format json
   default_rule: prime_context
   full_read_obligation: >-
     On initial capability invocation, shell out to
     `agentera prime --context <name> --format json` and read the
-    `capability_context.prose` field in full.
+    `capability_context.instructions` field in full.
 implementation_state:
   instructions_ts_modules: implemented
   validators_require_instructions_ts: true

package/bundle/references/cli/capability-instruction-structure.md

@@ -111,16 +111,16 @@ against D80 plus this reference doc.
 |---|---|---|---|---|---|---|---|
 | ⌂ status | Linear | 10,389 | Yes | Yes | Yes | None | Complete (D79) |
 | ⛥ vision | Mode-split | 16,667 | Yes | Yes | Yes | Has vision.yaml shape subsection; shared pre-write self-audit hoist (DRY between Create and Refine modes) | Complete (D81) |
-| ❈ discuss | Loop | 13,816 | Not audited | Not audited | Not audited | Has deliverable template; has Getting started to fold | Not audited |
-| ⬚ research | Linear | 12,251 | Not audited | Not audited | Not audited | Has deliverable template; has Notes on depth | Not audited |
-| ≡ plan | Mode-split | 14,800 | Not audited | Not audited | Not audited | Has light/normal/full modes; has How build reads PLAN.md | Not audited |
-| ⧉ build | Cycle | 20,662 | Not audited | Not audited | Not audited | Has Handling blocked work; no Getting started | Not audited |
-| ⎘ optimize | Cycle | 25,990 | Not audited | Not audited | Not audited | Has Handling blocked experiments | Not audited |
-| ⛶ audit | Linear | 31,313 | Not audited | Not audited | Not audited | Has finding taxonomy plus health.yaml write; Steps 1-7 | Not audited |
-| ▤ document | Mode-split | 21,779 | Not audited | Not audited | Not audited | Has closeout context startup; has docs.yaml shape | Not audited |
-| ♾ profile | Mode-split | 24,219 | Not audited | Not audited | Not audited | Has PROFILE.md template; has Notes on depth vs speed | Not audited |
-| ◰ design | Mode-split | 20,596 | Not audited | Not audited | Not audited | Has Colors/Typography domain content; has DESIGN.md format | Not audited |
-| ⎈ orchestrate | Multi-surface | 28,544 | Not audited | Not audited | Not audited | Has three surface templates; has Keeping the orchestrator lean | Not audited |
+| ❈ discuss | Loop | 12,045 | Yes | Yes | Yes | Has decisions.yaml shape subsection; Getting started folded into §6; loop shape named "The deliberation loop" (§3); fog-aware readiness check at Done; steering rules (breadth-first, ask-user-to-sketch); schema files use artifact-id labels not canonical filenames | Complete (D82) |
+| ⬚ research | Linear | 12,484 | Yes | Yes | Yes | Has deliverable template; has transferable concepts checkpoint between source reading and target exploration; runtime-agnostic tool references | Complete (D83) |
+| ≡ plan | Mode-split | 14,515 | Yes | Yes | Yes | Has skip/light/full modes; `unknowns:` and `rejected:` full-plan fields; `How build reads PLAN.md` removed (artifact read contract declared in §2 only); fog-check at handoff; replan trigger qualitative (surprises on one task alter downstream acceptance); Getting started folded into §6; YAML formats reordered intent-first | Complete (D84) |
+| ⧉ build | Cycle | 15,081 | Yes | Yes | Yes | Has Handling blocked work; vision bootstrap folded into Workflow phases; brainstorm cut to minimal fallback; subagent spawning table cut to brief pointer; self-audit folded into Log (8 steps); plan unknowns consumption; cycle boundary stated once; `/loop` replaced with explicit user request | Complete (D85) |
+| ⎘ optimize | Cycle | 20,622 | Yes | Yes | Yes | Has Handling blocked experiments; self-audit folded into Log (7 steps); subagent spawning table compressed (D85 propagation); benchmark context lean seam; experiments.yaml has context block; brainstorm stripped to 4 questions | Complete (D86) |
+| ⛶ audit | Linear | 18,401 | Yes | Yes | Yes | Has finding taxonomy plus health.yaml shape; has 3 agentera-specific dimension mechanics (Version health, Artifact freshness, Prose health); Getting started folded into §6; self-audit folded into Report (7→6 steps); subagent spawning compressed to brief pointer; evidence_context startup delegation (bespoke); decision satisfaction authority rule in Safety rails | Complete (D87) |
+| ▤ document | Mode-split | 14,886 | Yes | Yes | Yes | Has docs.yaml shape; closeout context lean pointer; Getting started folded into §6; self-audit folded into write steps; doc-prose enforcement compressed to lint+report; Step 0 mode detection folded into opening; decision satisfaction in Safety rails | Complete (D88) |
+| ♾ profile | Mode-split | 19,567 | Yes | Yes | Yes | Has PROFILE.md template flex section; coverage+extraction merged (6→4 Full steps); prediction validation folded into Generate + EX2 for <3/5; Validate V3+V4 merged (4→3); Getting started folded into §6; startup contract delegation | Complete (D89) |
+| ◰ design | Mode-split | 16,383 | Yes | Yes | Yes | Has DESIGN.md format subsection in State artifacts; self-audit folded into Write/Update steps; Step 0 folded into opening; Getting started folded into §6 | Complete (D90) |
+| ⎈ orchestrate | Multi-surface | 18,497 | Yes | Yes | Yes | Has staleness check in Step 0 (3 steps, self-contained); has loop stop condition in Exit signals; WARN eliminated from evaluation (PASS/FAIL only); test-suppression directive removed from delegation prompt; Keeping the orchestrator lean folded into Safety rails; subagent table compressed to brief pointer; Getting started folded into §6; decision satisfaction in Safety rails | Complete (D91) |
 
 ---
 

package/bundle/references/cli/vocabulary.md

@@ -221,7 +221,7 @@ ambiguous-term sweep remain separate follow-up work.
 
 Canonical artifact IDs include `vision`, `decisions`, `plan`, `progress`,
 `todo`, `health`, `docs`, `design`, `profile`, `objective`, `experiments`,
-`changelog`, `session`, `plan_archive`, `optimera_harness`, and
+`changelog`, `session`, `plan_archive`, `optimize_harness`, and
 `semantic_fixture`.
 
 ## Status, severity, confidence, and exits

package/bundle/skills/agentera/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: agentera
 description: >
-  One agent, one CLI, many capabilities. Per-capability prose lives in
+  One agent, one CLI, many capabilities. Per-capability instructions live in
   `packages/cli/src/capabilities/<name>/instructions.ts` and the runtime serves
   it through `agentera prime --context <name> --format json`. Use this skill
   for /agentera and Agentera capability requests; bare `/agentera` runs the
@@ -26,7 +26,7 @@ capabilities:
 # agentera
 
 One agent, one CLI, many capabilities. The CLI is the routing brain — it owns
-project memory, capability prose, routing judgment, and the worker-spec contract.
+project memory, capability instructions, routing judgment, and the worker-spec contract.
 The host agent learns one contract: the CLI.
 
 ---
@@ -47,7 +47,7 @@ For capability-specific startup context:
 npx -y agentera prime --context <capability> --format json
 ```
 
-This returns the capability's prose, declared read/write needs, artifact
+This returns the capability's instructions, declared read/write needs, artifact
 inventory, included/missing state, and fallback commands. Use it before
 reading the instructions module directly.
 
@@ -65,10 +65,10 @@ The CLI routes. The host agent follows.
 
 | Request shape | Route |
 |---|---|
-| Bare `/agentera` | 1. Run `agentera prime --format json` for state data + inlined rendering contract. 2. Follow `source_contract.capability_context.prose` for dashboard template, field rules, and exit marker. 3. Render the dashboard from the state data per the prose. 4. Follow `next_action` to suggest the next capability. |
-| `/agentera <capability-name>` | Run `agentera prime --context <capability> --format json`. Follow the capability's prose and contract. |
+| Bare `/agentera` | 1. Run `agentera prime --format json` for state data. 2. Run the `fetch_command` from `source_contract.capability_context` to get rendering instructions. 3. Follow `capability_context.instructions` for dashboard template, field rules, and exit marker. 4. Render the dashboard from the state data per the instructions. 5. Follow `next_action` to suggest the next capability. |
+| `/agentera <capability-name>` | Run `agentera prime --context <capability> --format json`. Follow the capability's instructions and contract. |
 | `/agentera <capability-name> <topic>` | Same as above; pass `<topic>` as the user's instruction to the capability. |
-| Natural language | Run `agentera prime --format json`. Follow the inlined status prose to render the briefing. Use `next_action.capability` to suggest the matching capability. If no high-confidence match, present a disambiguation prompt. |
+| Natural language | Run `agentera prime --format json`. Run the `fetch_command` from `source_contract.capability_context` for rendering instructions. Use `next_action.capability` to suggest the matching capability. If no high-confidence match, present a disambiguation prompt. |
 
 Capability names are the routing identity: `status`, `vision`, `discuss`,
 `research`, `plan`, `build`, `optimize`, `audit`, `document`, `profile`,
@@ -98,11 +98,11 @@ Capability handoffs use glyph plus canonical name (e.g. `⧉ build`, `≡ plan`)
 
 The prime dashboard rendering contract — template, field-by-field rules, output
 budget, attention-item ordering, exit marker — is owned by the status capability
-prose. Bare `agentera prime --format json` inlines this prose in
-`source_contract.capability_context.prose` (source: `inlined_for_layer_1`);
-follow it for layout, inclusion/exclusion rules, and the mandatory
-`⌂ status · <status>` exit marker. Ask for confirmation before invoking a
-state-changing downstream capability.
+instructions. Bare `agentera prime --format json` returns a pointer at
+`source_contract.capability_context` with a `fetch_command` to retrieve them;
+run it, then follow `capability_context.instructions` for layout,
+inclusion/exclusion rules, and the mandatory `⌂ status · <status>` exit marker.
+Ask for confirmation before invoking a state-changing downstream capability.
 
 The first response in a fresh interaction delivers the brief and a free-form
 continuation prompt, not a native question menu — unless the user explicitly

package/bundle/skills/agentera/agents/research.toml

@@ -2,5 +2,5 @@
 name = "research"
 description = "External pattern research and synthesis."
 developer_instructions = """
-You are the Agentera research capability subagent. You are a read-only agent — do not write files or execute shell commands. Run `agentera prime --context research --format json` to fetch the authoritative instructions as a JSON capsule (the `prose` field carries the full Markdown body). Stay within the dispatched capability task, use the Agentera CLI state seam first, and preserve Agentera artifact safety rails.
+You are the Agentera research capability subagent. You are a read-only agent — do not write files or execute shell commands. Run `agentera prime --context research --format json` to fetch the authoritative instructions as a JSON capsule (the `instructions` field carries the full Markdown body). Stay within the dispatched capability task, use the Agentera CLI state seam first, and preserve Agentera artifact safety rails.
 """

package/bundle/skills/agentera/capabilities/audit/schemas/exit.yaml

@@ -4,8 +4,8 @@ EXIT_CONDITIONS:
     condition: complete
     description: >-
       All selected audit dimensions were assessed, findings were synthesized,
-      grades were assigned, HEALTH.md was updated, and the user was presented
-      with actionable results.
+      grades were assigned, the health artifact was updated, and the user was
+      presented with actionable results.
     exit_signal: complete
   2:
     id: E2

package/bundle/skills/agentera/capabilities/audit/schemas/validation.yaml

@@ -24,9 +24,10 @@ VALIDATION:
     id: V3
     rule: decisions_respected
     description: >-
-      Findings that contradict deliberate decisions documented in DECISIONS.md
-      MUST be discarded or downgraded to info (SF3). A deliberate decision is
-      not a finding; it is an implementation of that decision.
+      Findings that contradict deliberate decisions documented in
+      .agentera/decisions.yaml MUST be discarded or downgraded to info
+      (SF3). A deliberate decision is not a finding; it is an
+      implementation of that decision.
     severity: critical
     checks:
       - "No finding contradicts a known deliberate decision"

package/bundle/skills/agentera/capabilities/build/schemas/artifacts.yaml

@@ -6,7 +6,7 @@ ARTIFACTS:
     description: >-
       Build consumes this through CLI execution_context caveats or explicit
       fallback state when available, and never modifies it during cycles. Created
-      during brainstorm (bootstrap or user-requested refinement).
+      during vision bootstrap.
   2:
     id: A2
     artifact_id: todo

package/bundle/skills/agentera/capabilities/build/schemas/exit.yaml

@@ -5,7 +5,7 @@ EXIT_CONDITIONS:
     description: >-
       One full cycle completed. Work was selected, implemented, verified
       against the project's test/build suite, committed with a conventional
-      message, and PROGRESS.md and TODO.md were updated.
+      message, and progress.yaml and TODO.md were updated.
     exit_signal: complete
   2:
     id: E2
@@ -14,14 +14,14 @@ EXIT_CONDITIONS:
       The cycle completed but with notable issues. Possible causes:
       verification passed but with warnings, the committed work is narrower
       than intended due to scope reduction, or discoveries logged in
-      PROGRESS.md suggest the next cycle may face blockers.
+      progress.yaml suggest the next cycle may face blockers.
     exit_signal: flagged
   3:
     id: E3
     condition: stuck
     description: >-
       Cannot complete a cycle because VISION.md does not exist and the
-      brainstorm cannot proceed without the user, every available work item
+      vision bootstrap cannot proceed without the user, every available work item
       is blocked, or the verification suite is broken and cannot be fixed
       within the cycle's scope.
     exit_signal: stuck

package/bundle/skills/agentera/capabilities/build/schemas/validation.yaml

@@ -3,7 +3,7 @@ VALIDATION:
     id: V1
     rule: verified_field_mandatory
     description: >-
-      Every PROGRESS.md cycle entry MUST have a verified field. The field
+      Every progress.yaml cycle entry MUST have a verified field. The field
       carries either observed output from the primary entrypoint, an allowlisted
       N/A tag, or a free-form rationale of at least 8 words.
     severity: critical
@@ -14,9 +14,9 @@ VALIDATION:
     id: V2
     rule: one_cycle_per_invocation
     description: >-
-      Build executes exactly one cycle per invocation. After logging (Step 9),
+      Build executes exactly one cycle per invocation. After logging (Step 8),
       the capability MUST stop. Multiple cycles require separate invocations or
-      /loop.
+      an explicit user request.
     severity: critical
     checks:
       - "Only one cycle entry appended to PROGRESS.md per invocation"
@@ -24,7 +24,7 @@ VALIDATION:
     id: V3
     rule: no_remote_push
     description: >-
-      Build MUST NEVER push to any remote repository. All commits are local
+      Build MUST NOT push to any remote repository. All commits are local
       only. Remote operations require explicit user instruction outside this
       capability.
     severity: critical
@@ -35,7 +35,7 @@ VALIDATION:
     rule: vision_readonly_during_cycle
     description: >-
       The canonical vision artifact MUST NOT be modified during a cycle. It may only be written
-      during a brainstorm session (bootstrap or user-requested refinement).
+      during a vision bootstrap.
     severity: critical
     checks:
       - "Vision artifact not modified outside brainstorm"
@@ -43,7 +43,7 @@ VALIDATION:
     id: V5
     rule: consecutive_failure_guard
     description: >-
-      If the last 3 PROGRESS.md entries all record failed cycles, build
+      If the last 3 progress.yaml entries all record failed cycles, build
       MUST stop and surface the pattern to the user. Do not attempt a 4th
       consecutive cycle on the same failing problem.
     severity: critical
@@ -59,7 +59,7 @@ VALIDATION:
       other agent-facing artifacts as YAML in .agentera/).
     severity: warning
     checks:
-      - "DOCS.md checked before artifact access"
+      - "docs.yaml checked before artifact access"
   7:
     id: V7
     rule: execution_context_first
@@ -93,7 +93,7 @@ VALIDATION:
     severity: critical
     checks:
       - "No protected state mutation during context generation"
-      - "No unsupported `agentera build` or `agentera build` command introduced"
+      - "No unsupported `agentera build` command introduced"
   10:
     id: V10
     rule: satisfaction_authority_boundary

package/bundle/skills/agentera/capabilities/design/schemas/exit.yaml

@@ -4,16 +4,16 @@ EXIT_CONDITIONS:
     condition: complete
     description: >-
       DESIGN.md was written (Create/Replace mode), updated (Refine mode),
-      or audited with findings reported (Audit mode). Validation script
-      ran without errors, and all changes had explicit user approval.
+      or audited with findings reported (Audit mode). agentera check lint
+      --artifact design passed, and all changes had explicit user approval.
     exit_signal: complete
   2:
     id: E2
     condition: flagged
     description: >-
       The design system was produced or audited but with issues worth
-      surfacing. Possible causes: validation passed with advisory warnings,
-      the design drifts from VISION.md Identity, or audit findings were
+      surfacing. Possible causes: lint passed with advisory warnings,
+      the design drifts from vision Identity, or audit findings were
       neither fixed nor filed.
     exit_signal: flagged
   3:
@@ -21,7 +21,7 @@ EXIT_CONDITIONS:
     condition: stuck
     description: >-
       Cannot write DESIGN.md because the user declined to approve the
-      draft, the validation script reports unresolvable errors, or the
+      draft, agentera check lint reports unresolvable errors, or the
       project's UI stack is inaccessible.
     exit_signal: stuck
   4:

package/bundle/skills/agentera/capabilities/design/schemas/validation.yaml

@@ -14,13 +14,13 @@ VALIDATION:
     id: V2
     rule: vision_identity_coherence
     description: >-
-      Design tokens MUST NOT conflict with VISION.md Identity. If the
+      Design tokens MUST NOT conflict with vision Identity. If the
       verbal identity says "warm and approachable" and the user wants a
       cold brutalist palette, the tension MUST be surfaced explicitly
       for the user to resolve.
     severity: critical
     checks:
-      - "Design tokens cohere with VISION.md Identity"
+      - "Design tokens cohere with vision Identity"
       - "Tensions surfaced when detected"
   3:
     id: V3

package/bundle/skills/agentera/capabilities/discuss/schemas/artifacts.yaml

@@ -5,11 +5,12 @@ ARTIFACTS:
     local_role: produces_and_consumes
     description: >-
       Reasoning trail with confidence labels. Discuss reads existing decisions
-      through `agentera decisions --format json` and its source_contract to avoid
-      re-deliberation, and writes new decision entries with confidence (DL1
-      firm, DL2 provisional, DL3 exploratory). Compact older entries by applying
-      schema COMPACTION rules; incomplete compacted entries are caveated context,
-      not a reason for historical reconstruction during normal deliberation.
+      through `agentera state decisions --format json` and its source_contract
+      to avoid re-deliberation, and writes new decision entries with confidence
+      (DL1 firm, DL2 provisional, DL3 exploratory). Compact older entries by
+      applying schema COMPACTION rules; incomplete compacted entries are
+      caveated context, not a reason for historical reconstruction during
+      normal deliberation.
   2:
     id: A2
     artifact_id: vision

package/bundle/skills/agentera/capabilities/discuss/schemas/exit.yaml

@@ -4,7 +4,7 @@ EXIT_CONDITIONS:
     condition: complete
     description: >-
       Deliberation reached a conclusion the user chose to act on; any
-      requested artifacts (DECISIONS.md, VISION.md, OBJECTIVE.md, TODO.md)
+      requested artifacts (decisions, vision, objective, todo)
       were written with user approval, and the decision confidence level
       was captured.
     exit_signal: complete
@@ -15,7 +15,7 @@ EXIT_CONDITIONS:
       Deliberation concluded but the decision remains unresolved or
       provisional: the user wrapped up without a clear choice, significant
       tensions could not be resolved, or the conclusion contradicts prior
-      decisions in DECISIONS.md without explicit acknowledgment.
+      decisions without explicit acknowledgment.
     exit_signal: flagged
   3:
     id: E3

package/bundle/skills/agentera/capabilities/discuss/schemas/validation.yaml

@@ -13,16 +13,17 @@ VALIDATION:
     id: V2
     rule: user_approval_for_artifact_writes
     description: >-
-      Discuss MUST NOT modify VISION.md, OBJECTIVE.md, or TODO.md without
-      explicit user confirmation. Present drafts and get approval.
+      Discuss MUST NOT modify vision, objective, or todo artifacts (the
+      protected_write_boundaries) without explicit user confirmation. Present
+      drafts and get approval.
     severity: critical
     checks:
-      - "User confirmation obtained before writing to VISION.md, OBJECTIVE.md, or TODO.md"
+      - "User confirmation obtained before writing to vision, objective, or todo artifacts"
   3:
     id: V3
     rule: decision_confidence_required
     description: >-
-      Every DECISIONS.md entry MUST have a Confidence field with one of the
+      Every decision entry MUST have a Confidence field with one of the
       protocol-defined labels: firm (DL1), provisional (DL2), or
       exploratory (DL3).
     severity: critical
@@ -33,7 +34,7 @@ VALIDATION:
     id: V4
     rule: preserved_decision_fields
     description: >-
-      DECISIONS.md entries MUST preserve the canonical top-level fields:
+      Decision entries MUST preserve the canonical top-level fields:
       Question, Context, Alternatives, Choice, Reasoning, Confidence,
       Feeds into. Win conditions stay inside Alternatives bullets.
     severity: critical

package/bundle/skills/agentera/capabilities/document/schemas/triggers.yaml

@@ -22,7 +22,6 @@ TRIGGERS:
       - "write docs"
       - "document this"
       - "create README"
-      - "write CLAUDE.md"
       - "write AGENTS.md"
       - "docs first"
       - "document before building"

package/bundle/skills/agentera/capabilities/optimize/schemas/artifacts.yaml

@@ -10,7 +10,7 @@ ARTIFACTS:
       canonical closure.
   2:
     id: A2
-    artifact_id: optimera_harness
+    artifact_id: optimize_harness
     local_role: produces
     description: >-
       Eval script that measures the metric and outputs structured JSON. Written

package/bundle/skills/agentera/capabilities/optimize/schemas/exit.yaml

@@ -5,7 +5,7 @@ EXIT_CONDITIONS:
     description: >-
       One experiment completed the full cycle: hypothesis formulated,
       implementation dispatched, regression check passed, metric measured,
-      decision made (kept or discarded), and EXPERIMENTS.md updated.
+      decision made (kept or discarded), and experiments.yaml updated.
     exit_signal: complete
   2:
     id: E2
@@ -20,7 +20,7 @@ EXIT_CONDITIONS:
     id: E3
     condition: stuck
     description: >-
-      Cannot proceed because OBJECTIVE.md is missing and the brainstorm cannot
+      Cannot proceed because objective.yaml is missing and the brainstorm cannot
       be completed without user input, the eval harness is broken and cannot
       be repaired without user approval, or the regression check infrastructure
       is unavailable.

package/bundle/skills/agentera/capabilities/optimize/schemas/validation.yaml

@@ -24,12 +24,12 @@ VALIDATION:
     id: V3
     rule: objective_readonly_during_cycle
     description: >-
-      OBJECTIVE.md MUST NOT be modified during a cycle except for canonical
+      objective.yaml MUST NOT be modified during a cycle except for canonical
       closure when the target is met. Other edits only happen during
       brainstorm or refine.
     severity: critical
     checks:
-      - "OBJECTIVE.md only modified for closure during cycle"
+      - "objective.yaml only modified for closure during cycle"
   4:
     id: V4
     rule: one_experiment_per_invocation

package/bundle/skills/agentera/capabilities/orchestrate/schemas/exit.yaml

@@ -3,7 +3,7 @@ EXIT_CONDITIONS:
     id: E1
     condition: complete
     description: >-
-      All PLAN.md tasks are complete, the health check passed, and the
+      All plan tasks are complete, the health check passed, and the
       orchestration session concluded with all planned work finished.
     exit_signal: complete
   2:
@@ -18,7 +18,7 @@ EXIT_CONDITIONS:
     id: E3
     condition: stuck
     description: >-
-      Cannot proceed. PLAN.md has circular dependencies preventing any task
+      Cannot proceed. The plan has circular dependencies preventing any task
       from becoming eligible, no target capabilities are available to
       delegate, or file access prevents reading or updating artifacts.
       The exit marker explains what is blocking progress.
@@ -27,8 +27,9 @@ EXIT_CONDITIONS:
     id: E4
     condition: waiting
     description: >-
-      No PLAN.md exists and the bootstrap chain cannot proceed because
-      VISION.md is absent and the user has not confirmed how to create one,
-      or a dispatched capability returned waiting status requiring user input.
-      The waiting bullet identifies the specific decision needed.
+      No plan exists and the bootstrap chain cannot proceed because the
+      vision artifact is absent and the user has not confirmed how to
+      create one, or a dispatched capability returned waiting status
+      requiring user input. The waiting bullet identifies the specific
+      decision needed.
     exit_signal: waiting