agentera 3.0.0-dev.5 → 3.0.0-dev.7

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

@@ -0,0 +1,6 @@
+# agentera_managed: true
+name = "orchestrate"
+description = "Multi-cycle orchestration over active plans."
+developer_instructions = """
+You are the Agentera orchestrate capability subagent. You have full file write, file edit, and shell execution tools available — use them to implement code changes, run tests, and commit results. Run `agentera prime --context orchestrate --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.
+"""

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

@@ -0,0 +1,6 @@
+# agentera_managed: true
+name = "plan"
+description = "Planning with acceptance criteria."
+developer_instructions = """
+You are the Agentera plan capability subagent. You have file write and file edit tools available to create or update files, but shell execution is disabled — do not attempt to run command line tools or scripts. Run `agentera prime --context plan --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.
+"""

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

@@ -0,0 +1,6 @@
+# agentera_managed: true
+name = "profile"
+description = "Decision profiling and preference memory."
+developer_instructions = """
+You are the Agentera profile capability subagent. You have full file write, file edit, and shell execution tools available — use them to implement code changes, run tests, and commit results. Run `agentera prime --context profile --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.
+"""

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

@@ -0,0 +1,6 @@
+# agentera_managed: true
+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.
+"""

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

@@ -0,0 +1,6 @@
+# agentera_managed: true
+name = "status"
+description = "Agentera orientation and routing dashboard."
+developer_instructions = """
+You are the Agentera status capability subagent. You are a read-only agent — do not write files or execute shell commands. Run `agentera prime --context status --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.
+"""

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

@@ -0,0 +1,6 @@
+# agentera_managed: true
+name = "vision"
+description = "Define and refine project direction."
+developer_instructions = """
+You are the Agentera vision capability subagent. You have file write and file edit tools available to create or update files, but shell execution is disabled — do not attempt to run command line tools or scripts. Run `agentera prime --context vision --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.
+"""

package/bundle/skills/agentera/capabilities/{inspektera → audit}/schemas/artifacts.yaml

@@ -5,16 +5,16 @@ ARTIFACTS:
     local_role: produces_and_consumes
     description: >-
       Codebase health assessment with findings, dimension grades, and trajectory.
-      Inspektera writes audit entries with per-dimension grades, findings with
+      Audit writes audit entries with per-dimension grades, findings with
       severity and confidence scores, trend comparisons, and de facto
-      architecture patterns. During evaluation startup, Inspektera consumes health
+      architecture patterns. During evaluation startup, Audit consumes health
       state through CLI `evidence_context` before raw health artifact fallback.
   2:
     id: A2
     artifact_id: vision
     local_role: consumes
     description: >-
-      Inspektera treats vision state as protected during evidence-context startup;
+      Audit treats vision state as protected during evidence-context startup;
       missing or not-checked vision caveats from CLI `evidence_context` are preserved
       instead of forcing a raw vision read.
   3:
@@ -22,7 +22,7 @@ ARTIFACTS:
     artifact_id: decisions
     local_role: consumes
     description: >-
-      Inspektera consumes decision caveats through CLI `evidence_context` and the
+      Audit consumes decision caveats through CLI `evidence_context` and the
       listed `agentera decisions --format json` fallback before raw decisions artifact fallback.
       Compacted decision caveats must be preserved rather than reconstructed.
   4:
@@ -30,7 +30,7 @@ ARTIFACTS:
     artifact_id: todo
     local_role: produces_and_consumes
     description: >-
-      Inspektera reads this to avoid re-reporting known issues and writes to it
+      Audit reads this to avoid re-reporting known issues and writes to it
       with user confirmation when filing
       critical and warning findings. During evaluation startup, known TODO state is
       consumed through CLI `evidence_context` before raw TODO artifact fallback.
@@ -39,14 +39,14 @@ ARTIFACTS:
     artifact_id: progress
     local_role: consumes
     description: >-
-      Inspektera consumes latest progress verification and progress caveats through
+      Audit consumes latest progress verification and progress caveats through
       CLI `evidence_context` before raw progress artifact fallback.
   6:
     id: A6
     artifact_id: plan
     local_role: consumes
     description: >-
-      Inspektera consumes evaluation target and plan criteria through CLI
+      Audit consumes evaluation target and plan criteria through CLI
       `evidence_context` before raw plan artifact fallback. The plan's Created date
       still provides the artifact-current-state baseline when that state is needed.
   7:
@@ -54,7 +54,7 @@ ARTIFACTS:
     artifact_id: design
     local_role: consumes
     description: >-
-      Inspektera treats design state as optional during evidence-context startup;
+      Audit treats design state as optional during evidence-context startup;
       missing design caveats from CLI `evidence_context` are preserved before any raw
       design artifact fallback.
   8:
@@ -62,7 +62,7 @@ ARTIFACTS:
     artifact_id: docs
     local_role: consumes
     description: >-
-      Inspektera reads this first to resolve project-local artifact mappings
+      Audit reads this first to resolve project-local artifact mappings
       and checks the versioning convention for the version health dimension. During
       evaluation startup, docs state and version-boundary caveats are consumed through
       CLI `evidence_context` before raw docs artifact fallback.
@@ -71,6 +71,6 @@ ARTIFACTS:
     artifact_id: profile
     local_role: consumes
     description: >-
-      Inspektera consumes profile status and stale-profile caveats through CLI
+      Audit consumes profile status and stale-profile caveats through CLI
       `evidence_context`; stale or missing profile state is preserved as a caveat and
       is not approval to refresh profile state or read profile directly during startup.

package/bundle/skills/agentera/capabilities/{inspektera → audit}/schemas/triggers.yaml

@@ -3,11 +3,15 @@ TRIGGERS:
     id: T1
     description: >-
       Direct invocation by name or slash command. Matches when the user
-      explicitly requests inspektera.
+      explicitly requests audit.
     priority: high
     patterns:
-      - "inspektera"
-      - "/inspektera"
+      - "audit"
+      - "/audit"
+    confidence_threshold: 60
+    borderline_band: 10
+    patterns_regex:
+      - "\\b/audit\\b"
   2:
     id: T2
     description: >-
@@ -26,13 +30,18 @@ TRIGGERS:
       - "pattern audit"
       - "dependency check"
       - "test coverage audit"
+    confidence_threshold: 55
   3:
     id: T3
     description: >-
-      Implicit trigger after extended realisera activity. Matches when
-      realisera has run 5+ cycles without a health check and the system
+      Implicit trigger after extended build activity. Matches when
+      build has run 5+ cycles without a health check and the system
       detects an overdue audit.
     priority: medium
     patterns:
       - "health check overdue"
-      - "audit after realisera"
+      - "audit after build"
+    confidence_threshold: 50
+    disambiguates_against:
+      - capability: build
+        hint: "audit checks codebase health after build activity; build continues development"

package/bundle/skills/agentera/capabilities/{inspektera → audit}/schemas/validation.yaml

@@ -3,8 +3,8 @@ VALIDATION:
     id: V1
     rule: read_only_codebase
     description: >-
-      Inspektera MUST NOT modify any source code files. It is a read-only
-      assessment capability. Other capabilities fix what inspektera finds.
+      Audit MUST NOT modify any source code files. It is a read-only
+      assessment capability. Other capabilities fix what audit finds.
     severity: critical
     checks:
       - "No source code files are modified during audit"
@@ -53,8 +53,8 @@ VALIDATION:
     id: V6
     rule: exit_marker_required
     description: >-
-      Every inspektera invocation MUST emit an exit marker. The marker uses
-      the canonical glyph ⛶ (SG3) in the format ⛶ inspektera · <status>
+      Every audit invocation MUST emit an exit marker. The marker uses
+      the canonical glyph ⛶ (SG3) in the format ⛶ audit · <status>
       where status is one of EX1-EX4.
     severity: critical
     checks:
@@ -65,8 +65,8 @@ VALIDATION:
     id: V7
     rule: evidence_context_first
     description: >-
-      Inspektera evaluation startup MUST begin with `agentera prime --context
-      inspektera --format json` and use complete CLI `evidence_context` before
+      Audit evaluation startup MUST begin with `agentera prime --context
+      audit --format json` and use complete CLI `evidence_context` before
       raw plan, progress, docs, health, TODO, or decisions artifacts.
     severity: critical
     checks:
@@ -77,7 +77,7 @@ VALIDATION:
     rule: evidence_context_fallback_before_raw
     description: >-
       When evidence_context is absent, incomplete, or caveated for needed state,
-      Inspektera MUST run listed existing CLI fallback commands before any last-resort
+      Audit MUST run listed existing CLI fallback commands before any last-resort
       raw artifact read.
     severity: critical
     checks:
@@ -88,7 +88,7 @@ VALIDATION:
     id: V9
     rule: evidence_context_caveats_preserved
     description: >-
-      Inspektera reports MUST preserve evidence_context caveats for stale app/profile
+      Audit reports MUST preserve evidence_context caveats for stale app/profile
       state, compacted decisions, protected-state boundaries, unavailable version or
       publication evidence, manual-check states, and residual risks instead of hiding,
       flattening, or reconstructing them.
@@ -101,7 +101,7 @@ VALIDATION:
     id: V10
     rule: satisfaction_authority_boundary
     description: >-
-      When Inspektera touches decision satisfaction, it may report provisional
+      When Audit touches decision satisfaction, it may report provisional
       satisfaction with evidence but MUST NOT user-confirm satisfaction. Missing,
       compacted, open, provisional, or review-needed satisfaction state remains a
       caveat and review pressure; automation must not reconstruct hidden outcomes

package/bundle/skills/agentera/capabilities/{realisera → build}/schemas/artifacts.yaml

@@ -4,7 +4,7 @@ ARTIFACTS:
     artifact_id: vision
     local_role: produces_and_consumes
     description: >-
-      Realisera consumes this through CLI execution_context caveats or explicit
+      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).
   2:
@@ -12,7 +12,7 @@ ARTIFACTS:
     artifact_id: todo
     local_role: produces_and_consumes
     description: >-
-      Realisera consumes TODO state from execution_context and included hej state
+      Build consumes TODO state from execution_context and included status state
       before direct reads, then writes newly discovered issues and resolved
       entries. Severity classified per protocol SI1-SI4.
   3:
@@ -20,7 +20,7 @@ ARTIFACTS:
     artifact_id: changelog
     local_role: produces_and_consumes
     description: >-
-      Realisera consumes changelog boundary from execution_context or the listed
+      Build consumes changelog boundary from execution_context or the listed
       CLI fallback before direct reads. It appends public change entries under
       [Unreleased] based on commit type and promotes on version bumps.
   4:
@@ -28,7 +28,7 @@ ARTIFACTS:
     artifact_id: progress
     local_role: produces_and_consumes
     description: >-
-      Operational cycle log. Realisera consumes latest progress evidence from
+      Operational cycle log. Build consumes latest progress evidence from
       execution_context first, then appends one entry per cycle with mandatory
       Verified field. Compacted by applying schema COMPACTION rules.
   5:
@@ -36,7 +36,7 @@ ARTIFACTS:
     artifact_id: health
     local_role: consumes
     description: >-
-      Realisera consumes health state from execution_context and included hej
+      Build consumes health state from execution_context and included status
       state before direct reads, focusing on critical and degraded findings for
       work selection.
   6:
@@ -44,7 +44,7 @@ ARTIFACTS:
     artifact_id: decisions
     local_role: consumes
     description: >-
-      Realisera consumes decision caveats and fallback commands from
+      Build consumes decision caveats and fallback commands from
       execution_context first. Firm (DL1) entries are constraints and exploratory
       (DL3) entries are uncertain foundations during work selection.
   7:
@@ -52,7 +52,7 @@ ARTIFACTS:
     artifact_id: plan
     local_role: produces_and_consumes
     description: >-
-      Realisera consumes selected task, acceptance criteria, dependencies,
+      Build consumes selected task, acceptance criteria, dependencies,
       constraints, and source contract metadata from CLI execution_context before
       direct plan reads, then updates task status and surprises during execution.
   8:
@@ -60,7 +60,7 @@ ARTIFACTS:
     artifact_id: profile
     local_role: consumes
     description: >-
-      Realisera consumes hej profile summary first. Missing or stale profile state
+      Build consumes status profile summary first. Missing or stale profile state
       is a caveat and does not authorize profile refresh or direct profile reads
       during normal startup.
   9:
@@ -68,13 +68,13 @@ ARTIFACTS:
     artifact_id: docs
     local_role: consumes
     description: >-
-      Realisera consumes artifact mappings and docs caveats from execution_context
-      and included hej docs state before direct docs reads.
+      Build consumes artifact mappings and docs caveats from execution_context
+      and included status docs state before direct docs reads.
   10:
     id: A10
     artifact_id: design
     local_role: consumes
     description: >-
-      Realisera treats design state missing from execution_context as a caveat or
+      Build treats design state missing from execution_context as a caveat or
       fallback-only need, and reads it only when building user-facing features
       after listed CLI fallbacks are exhausted.

package/bundle/skills/agentera/capabilities/{realisera → build}/schemas/triggers.yaml

@@ -3,11 +3,13 @@ TRIGGERS:
     id: T1
     description: >-
       Direct invocation by name or slash command. Matches when the user
-      explicitly requests realisera for autonomous development.
+      explicitly requests build for autonomous development.
     priority: high
     patterns:
-      - "realisera"
-      - "/realisera"
+      - "build"
+      - "/build"
+    confidence_threshold: 60
+    borderline_band: 10
   2:
     id: T2
     description: >-
@@ -19,6 +21,7 @@ TRIGGERS:
       - "evolve the project"
       - "develop autonomously"
       - "build the next feature"
+    confidence_threshold: 50
   3:
     id: T3
     description: >-
@@ -29,6 +32,7 @@ TRIGGERS:
       - "keep building"
       - "start building"
       - "work on the project"
+    confidence_threshold: 50
   4:
     id: T4
     description: >-
@@ -37,3 +41,9 @@ TRIGGERS:
     priority: medium
     patterns:
       - "refine the vision"
+    confidence_threshold: 50
+    disambiguates_against:
+      - capability: vision
+        hint: "build implements code after vision work; vision defines direction"
+    patterns_regex:
+      - "\\brefine\\s+the\\s+vision\\b"

package/bundle/skills/agentera/capabilities/{realisera → build}/schemas/validation.yaml

@@ -14,7 +14,7 @@ VALIDATION:
     id: V2
     rule: one_cycle_per_invocation
     description: >-
-      Realisera executes exactly one cycle per invocation. After logging (Step 9),
+      Build executes exactly one cycle per invocation. After logging (Step 9),
       the capability MUST stop. Multiple cycles require separate invocations or
       /loop.
     severity: critical
@@ -24,7 +24,7 @@ VALIDATION:
     id: V3
     rule: no_remote_push
     description: >-
-      Realisera MUST NEVER push to any remote repository. All commits are local
+      Build MUST NEVER push to any remote repository. All commits are local
       only. Remote operations require explicit user instruction outside this
       capability.
     severity: critical
@@ -43,7 +43,7 @@ VALIDATION:
     id: V5
     rule: consecutive_failure_guard
     description: >-
-      If the last 3 PROGRESS.md entries all record failed cycles, realisera
+      If the last 3 PROGRESS.md 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
@@ -64,7 +64,7 @@ VALIDATION:
     id: V7
     rule: execution_context_first
     description: >-
-      Realisera startup SHOULD begin from `agentera prime --context realisera
+      Build startup SHOULD begin from `agentera prime --context build
       --format json` and consume complete execution_context
       state before direct reads of plan, progress, TODO, docs, health,
       decisions, changelog, vision, profile, or design artifacts.
@@ -76,7 +76,7 @@ VALIDATION:
     id: V8
     rule: fallback_before_raw
     description: >-
-      When execution_context is incomplete or caveated, Realisera MUST run listed
+      When execution_context is incomplete or caveated, Build MUST run listed
       CLI fallback commands before any last-resort raw artifact diagnostic and
       MUST preserve caveats in cycle reporting.
     severity: critical
@@ -93,12 +93,12 @@ VALIDATION:
     severity: critical
     checks:
       - "No protected state mutation during context generation"
-      - "No unsupported `agentera realisera` or `agentera build` command introduced"
+      - "No unsupported `agentera build` or `agentera build` command introduced"
   10:
     id: V10
     rule: satisfaction_authority_boundary
     description: >-
-      When Realisera touches decision satisfaction, it may mark provisional
+      When Build touches decision satisfaction, it may mark provisional
       satisfaction with evidence but MUST NOT user-confirm satisfaction. Missing,
       compacted, open, provisional, or review-needed satisfaction state remains a
       caveat and review pressure; automation must not reconstruct hidden outcomes

package/bundle/skills/agentera/capabilities/{visualisera → design}/schemas/artifacts.yaml

@@ -5,40 +5,40 @@ ARTIFACTS:
     local_role: produces_and_consumes
     description: >-
       Visual identity system with design tokens, typography, colors,
-      spacing, constraints, and component contracts. Visualisera writes and
+      spacing, constraints, and component contracts. Design writes and
       reads agent-readable YAML token blocks with HTML comment markers.
   2:
     id: A2
     artifact_id: vision
     local_role: consumes
     description: >-
-      Visualisera reads the Identity section to propose visual tokens
+      Design reads the Identity section to propose visual tokens
       coherent with the declared verbal personality.
   3:
     id: A3
     artifact_id: progress
     local_role: consumes
     description: >-
-      Visualisera reads this during refine mode to identify UI work and
+      Design reads this during refine mode to identify UI work and
       inline design decisions since the design system was written.
   4:
     id: A4
     artifact_id: todo
     local_role: produces_and_consumes
     description: >-
-      Visualisera reads this to check for design-related issues and files
+      Design reads this to check for design-related issues and files
       code drift findings here during audit mode.
   5:
     id: A5
     artifact_id: docs
     local_role: consumes
     description: >-
-      Visualisera reads this first to resolve project-local artifact mappings
+      Design reads this first to resolve project-local artifact mappings
       before accessing other artifacts.
   6:
     id: A6
     artifact_id: profile
     local_role: consumes
     description: >-
-      Visualisera reads aesthetic preferences from the profile as defaults
+      Design reads aesthetic preferences from the profile as defaults
       during the create conversation.

package/bundle/skills/agentera/capabilities/{visualisera → design}/schemas/triggers.yaml

@@ -3,11 +3,15 @@ TRIGGERS:
     id: T1
     description: >-
       Direct invocation by name or slash command. Matches when the user
-      explicitly requests visualisera.
+      explicitly requests design.
     priority: high
     patterns:
-      - "visualisera"
-      - "/visualisera"
+      - "design"
+      - "/design"
+    confidence_threshold: 60
+    borderline_band: 10
+    patterns_regex:
+      - "\\b/design\\b"
   2:
     id: T2
     description: >-
@@ -21,6 +25,7 @@ TRIGGERS:
       - "visual identity"
       - "define the aesthetic"
       - "set up design system"
+    confidence_threshold: 50
   3:
     id: T3
     description: >-
@@ -31,3 +36,10 @@ TRIGGERS:
       - "audit design"
       - "refine design system"
       - "update DESIGN.md"
+    confidence_threshold: 50
+    disambiguates_against:
+      - capability: audit
+        hint: "design here is about visual identity, not codebase auditing"
+    patterns_regex:
+      - "\\baudit\\s+design\\b"
+      - "update\\s+DESIGN\\.md"

package/bundle/skills/agentera/capabilities/{visualisera → design}/schemas/validation.yaml

@@ -50,12 +50,12 @@ VALIDATION:
     id: V5
     rule: no_code_modification
     description: >-
-      Visualisera MUST NOT modify code files. It writes DESIGN.md only.
-      Realisera implements the design system in code. The separation
+      Design MUST NOT modify code files. It writes DESIGN.md only.
+      Build implements the design system in code. The separation
       of declaration and implementation is fundamental.
     severity: critical
     checks:
-      - "No code files modified during visualisera invocation"
+      - "No code files modified during design invocation"
   6:
     id: V6
     rule: codebase_exploration_required
@@ -70,8 +70,8 @@ VALIDATION:
     id: V7
     rule: exit_marker_required
     description: >-
-      Every visualisera invocation MUST emit an exit marker using the
-      canonical glyph ◰ (SG11) in the format ◰ visualisera · <status>
+      Every design invocation MUST emit an exit marker using the
+      canonical glyph ◰ (SG11) in the format ◰ design · <status>
       where status is one of EX1-EX4.
     severity: critical
     checks:

package/bundle/skills/agentera/capabilities/{resonera → discuss}/schemas/artifacts.yaml

@@ -4,7 +4,7 @@ ARTIFACTS:
     artifact_id: decisions
     local_role: produces_and_consumes
     description: >-
-      Reasoning trail with confidence labels. Resonera reads existing decisions
+      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
@@ -15,7 +15,7 @@ ARTIFACTS:
     artifact_id: vision
     local_role: produces_and_consumes
     description: >-
-      Resonera may update project direction only with explicit user
+      Discuss may update project direction only with explicit user
       confirmation when a decision feeds into project direction. Read for
       context during deliberation.
   3:
@@ -23,25 +23,25 @@ ARTIFACTS:
     artifact_id: todo
     local_role: produces_and_consumes
     description: >-
-      Resonera may add tech debt items surfaced during deliberation only with
+      Discuss may add tech debt items surfaced during deliberation only with
       explicit user confirmation. Severity per protocol SI1-SI4.
   4:
     id: A4
     artifact_id: objective
     local_role: produces_and_consumes
     description: >-
-      Resonera may write optimization decisions only with explicit user
+      Discuss may write optimization decisions only with explicit user
       confirmation when a decision feeds into what to optimize.
   5:
     id: A5
     artifact_id: profile
     local_role: consumes
     description: >-
-      Resonera reads this at session start to acknowledge high-confidence
+      Discuss reads this at session start to acknowledge high-confidence
       entries and avoid re-deliberating settled ground.
   6:
     id: A6
     artifact_id: docs
     local_role: consumes
     description: >-
-      Resonera reads this first to resolve project-local artifact mappings.
+      Discuss reads this first to resolve project-local artifact mappings.

package/bundle/skills/agentera/capabilities/{resonera → discuss}/schemas/triggers.yaml

@@ -3,11 +3,13 @@ TRIGGERS:
     id: T1
     description: >-
       Direct invocation by name or slash command. Matches when the user
-      explicitly requests resonera for structured deliberation.
+      explicitly requests discuss for structured deliberation.
     priority: high
     patterns:
-      - "resonera"
-      - "/resonera"
+      - "discuss"
+      - "/discuss"
+    confidence_threshold: 60
+    borderline_band: 10
   2:
     id: T2
     description: >-
@@ -23,6 +25,7 @@ TRIGGERS:
       - "what are the tradeoffs"
       - "brainstorm"
       - "rubber duck"
+    confidence_threshold: 50
   3:
     id: T3
     description: >-
@@ -34,6 +37,7 @@ TRIGGERS:
       - "I'm torn between"
       - "what's the right approach"
       - "let's reason about"
+    confidence_threshold: 50
   4:
     id: T4
     description: >-
@@ -44,3 +48,7 @@ TRIGGERS:
       - "scope this out"
       - "before I build this"
       - "talk me through"
+    confidence_threshold: 50
+    disambiguates_against:
+      - capability: plan
+        hint: "discuss explores options before committing; plan structures committed work"

package/bundle/skills/agentera/capabilities/{resonera → discuss}/schemas/validation.yaml

@@ -3,7 +3,7 @@ VALIDATION:
     id: V1
     rule: one_question_per_turn
     description: >-
-      Resonera MUST ask exactly one question per turn. Compound questions
+      Discuss MUST ask exactly one question per turn. Compound questions
       are not allowed. Every question MUST include a Done option.
     severity: critical
     checks:
@@ -13,7 +13,7 @@ VALIDATION:
     id: V2
     rule: user_approval_for_artifact_writes
     description: >-
-      Resonera MUST NOT modify VISION.md, OBJECTIVE.md, or TODO.md without
+      Discuss MUST NOT modify VISION.md, OBJECTIVE.md, or TODO.md without
       explicit user confirmation. Present drafts and get approval.
     severity: critical
     checks:
@@ -43,7 +43,7 @@ VALIDATION:
     id: V5
     rule: no_implementation
     description: >-
-      Resonera MUST NOT skip to implementation. It deliberates; other
+      Discuss MUST NOT skip to implementation. It deliberates; other
       capabilities build. If the user wants to build, route to the
       appropriate capability.
     severity: critical
@@ -64,7 +64,7 @@ VALIDATION:
     id: V7
     rule: satisfaction_authority_boundary
     description: >-
-      When Resonera touches decision satisfaction, it may capture provisional
+      When Discuss touches decision satisfaction, it may capture provisional
       satisfaction with evidence but MUST NOT user-confirm satisfaction unless the
       user explicitly confirms it. Missing, compacted, open, provisional, or
       review-needed satisfaction state remains a caveat and review pressure;