agentera 3.0.0-dev.3 → 3.0.0-dev.31

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

@@ -0,0 +1,84 @@
+ARTIFACTS:
+  1:
+    id: A1
+    artifact: health
+    local_role: produces_and_consumes
+    description: >-
+      Codebase health assessment with findings, dimension grades, and trajectory.
+      Audit writes audit entries with per-dimension grades, findings with
+      severity and confidence scores, trend comparisons, and de facto
+      architecture patterns. During evaluation startup, Audit consumes health
+      state through CLI `evidence_context`, then bounded `agentera state health
+       list --limit 20 --format json` and exact `state health get --id ID`.
+      Raw health reads are diagnostic-only for corruption or CLI-defect investigation.
+  2:
+    id: A2
+    artifact: vision
+    local_role: consumes
+    description: >-
+      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:
+    id: A3
+    artifact: decisions
+    local_role: consumes
+    description: >-
+      Audit consumes decision caveats through CLI `evidence_context`, then
+      bounded `agentera state decisions list --limit 20 --format json` discovery
+       and exact `state decisions get --id ID` retrieval. Raw decision reads
+      are diagnostic-only for corruption or CLI-defect investigation. Compacted
+      decision caveats must be preserved rather than reconstructed.
+  4:
+    id: A4
+    artifact: todo
+    local_role: produces_and_consumes
+    description: >-
+      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`; raw TODO reads are diagnostic-only
+      for corruption or CLI-defect investigation.
+  5:
+    id: A5
+    artifact: progress
+    local_role: consumes
+    description: >-
+      Audit consumes latest progress verification and progress caveats through
+      CLI `evidence_context`, then bounded `agentera state progress list --limit
+       20 --format json` discovery and exact `state progress get --id ID`
+      retrieval. Raw progress reads are diagnostic-only for corruption or
+      CLI-defect investigation.
+  6:
+    id: A6
+    artifact: plan
+    local_role: consumes
+    description: >-
+      Audit consumes evaluation target and plan criteria through CLI
+      `evidence_context` before any diagnostic-only raw plan read. The plan's Created date
+      still provides the artifact-current-state baseline when that state is needed.
+  7:
+    id: A7
+    artifact: design
+    local_role: consumes
+    description: >-
+      Audit treats design state as optional during evidence-context startup;
+      missing design caveats from CLI `evidence_context` are preserved before any
+      diagnostic-only raw design read.
+  8:
+    id: A8
+    artifact: docs
+    local_role: consumes
+    description: >-
+      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 any diagnostic-only raw docs read.
+  9:
+    id: A9
+    artifact: profile
+    local_role: consumes
+    description: >-
+      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/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/triggers.yaml

@@ -0,0 +1,25 @@
+TRIGGERS:
+  1:
+    id: T1
+    description: Audit local codebase health, architecture, quality, or technical debt.
+    priority: high
+  2:
+    id: T2
+    description: Review the local repository's code, architecture, dependencies, or structural health.
+    priority: high
+    disambiguates_against:
+      - capability: research
+        hint: "audit reviews this local codebase; research analyzes an external source or repository"
+      - capability: document
+        hint: "audit owns code and architecture health; document owns documentation maintenance and docs audits"
+      - capability: design
+        hint: "audit owns code and architecture health; design owns visual identity and design-system review"
+      - capability: optimize
+        hint: "audit assesses local health; optimize improves an existing system against a measurable target"
+  3:
+    id: T3
+    description: Review local health after implementation activity reveals a need for assessment.
+    priority: medium
+    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"
@@ -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 returned by the bounded
+      decisions entity view 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"
@@ -53,8 +54,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,30 +66,30 @@ 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
-      raw plan, progress, docs, health, TODO, or decisions artifacts.
+       Audit evaluation startup MUST begin with `agentera prime --context
+       audit --format json` and use complete CLI `evidence_context` before
+       bounded state list/get contracts for plan, progress, docs, health, TODO,
+       or decisions. Raw artifact access is diagnostic-only.
     severity: critical
     checks:
-      - "Evidence context is requested through prime --context before raw artifacts"
-      - "Complete evidence_context is used for evaluation target, criteria, evidence, caveats, and residual risks"
+       - "Evidence context is requested through prime --context before bounded state list/get"
   8:
     id: V8
     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
-      raw artifact read.
+       Audit MUST run listed bounded CLI fallback commands before any
+       diagnostic-only raw artifact read.
     severity: critical
     checks:
-      - "evidence_context.fallback_commands are attempted before raw artifact reads"
-      - "capability_context.state.fallback_commands is used when evidence_context is unavailable"
-      - "Raw artifact reads are last-resort diagnostics, not normal evaluation startup"
+       - "evidence_context.fallback_commands are attempted before diagnostic-only raw reads"
+       - "capability_context.state.fallback_commands is used when evidence_context is unavailable"
+       - "Raw artifact reads are diagnostic-only, not normal evaluation startup"
   9:
     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 +102,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/build/schemas/artifacts.yaml

@@ -0,0 +1,85 @@
+ARTIFACTS:
+  1:
+    id: A1
+    artifact: vision
+    local_role: produces_and_consumes
+    description: >-
+      Build consumes this through CLI execution_context caveats or explicit
+      fallback state when available, and never modifies it during cycles. Created
+      during vision bootstrap.
+  2:
+    id: A2
+    artifact: todo
+    local_role: produces_and_consumes
+    description: >-
+      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:
+    id: A3
+    artifact: changelog
+    local_role: produces_and_consumes
+    description: >-
+      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:
+    id: A4
+    artifact: progress
+    local_role: produces_and_consumes
+    description: >-
+      Operational cycle log. Build consumes latest progress evidence from
+      execution_context first, then bounded `agentera state progress list --limit
+       20 --format json` discovery or exact `state progress get --id ID`
+      retrieval, and appends one entry per cycle with mandatory Verified field.
+      Compacted by applying schema COMPACTION rules.
+  5:
+    id: A5
+    artifact: health
+    local_role: consumes
+    description: >-
+      Build consumes health state from execution_context and included status
+      state before bounded `agentera state health list --limit 20 --format json`
+       discovery or exact `state health get --id ID` retrieval, focusing on
+      critical and degraded findings for work selection. Raw reads are
+      diagnostic-only for corruption or CLI-defect investigation.
+  6:
+    id: A6
+    artifact: decisions
+    local_role: consumes
+    description: >-
+      Build consumes decision caveats and bounded list/get fallback commands from
+      execution_context first. Firm (DL1) entries are constraints and exploratory
+      (DL3) entries are uncertain foundations during work selection. Raw reads are
+      diagnostic-only for corruption or CLI-defect investigation.
+  7:
+    id: A7
+    artifact: plan
+    local_role: produces_and_consumes
+    description: >-
+      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:
+    id: A8
+    artifact: profile
+    local_role: consumes
+    description: >-
+      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:
+    id: A9
+    artifact: docs
+    local_role: consumes
+    description: >-
+      Build consumes artifact mappings and docs caveats from execution_context
+      and included status docs state before direct docs reads.
+  10:
+    id: A10
+    artifact: design
+    local_role: consumes
+    description: >-
+      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/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/triggers.yaml

@@ -0,0 +1,27 @@
+TRIGGERS:
+  1:
+    id: T1
+    description: A scoped implementation task or one verified development cycle.
+    priority: high
+  2:
+    id: T2
+    description: Implement one requested feature, fix, or bounded development task.
+    priority: high
+    disambiguates_against:
+      - capability: vision
+        hint: "build implements code; vision defines or refines project direction"
+      - capability: profile
+        hint: "build implements a software task; profile builds a reusable decision profile"
+      - capability: orchestrate
+        hint: "build completes one task or cycle; orchestrate runs an entire plan or multiple tasks"
+  3:
+    id: T3
+    description: Start or continue a single concrete implementation task.
+    priority: medium
+  4:
+    id: T4
+    description: Implement a scoped task after its plan or requirements are established.
+    priority: medium
+    disambiguates_against:
+      - capability: plan
+        hint: "build implements an established task; plan structures work before implementation"

package/bundle/skills/agentera/capabilities/{realisera → 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 entity record 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,17 +14,17 @@ 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 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"
+      - "Only one progress entity is appended per invocation"
   3:
     id: V3
     rule: no_remote_push
     description: >-
-      Realisera 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, realisera
+      If the last 3 bounded progress records all report 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
@@ -53,18 +53,18 @@ VALIDATION:
     id: V6
     rule: artifact_path_resolution
     description: >-
-      Before reading or writing any artifact, check .agentera/docs.yaml for path
-      overrides. If absent, use the default layout (TODO.md, CHANGELOG.md,
-      and DESIGN.md at root; canonical VISION.md at .agentera/vision.yaml;
-      other agent-facing artifacts as YAML in .agentera/).
+      Entity state MUST use exact/list CLI reads and typed writers discovered by
+      `agentera state <artifact> explain`. Check .agentera/docs.yaml only for
+      intentional singleton path overrides.
     severity: warning
     checks:
-      - "DOCS.md checked before artifact access"
+      - "Entity files are not read or edited directly"
+      - "docs.yaml checked before singleton artifact access"
   7:
     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` 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

@@ -1,44 +1,44 @@
 ARTIFACTS:
   1:
     id: A1
-    artifact_id: design
+    artifact: design
     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
+    artifact: 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
+    artifact: 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
+    artifact: 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
+    artifact: 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
+    artifact: 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/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/triggers.yaml

@@ -0,0 +1,16 @@
+TRIGGERS:
+  1:
+    id: T1
+    description: Define, maintain, or assess visual identity and a design system.
+    priority: high
+  2:
+    id: T2
+    description: Create a visual identity, design system, design tokens, or aesthetic direction.
+    priority: high
+  3:
+    id: T3
+    description: Refine, update, or audit a visual design system, including “audit the design system”.
+    priority: high
+    disambiguates_against:
+      - capability: audit
+        hint: "design here is about visual identity, not codebase auditing"

package/bundle/skills/agentera/capabilities/{visualisera → 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
@@ -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/discuss/schemas/artifacts.yaml

@@ -0,0 +1,49 @@
+ARTIFACTS:
+  1:
+    id: A1
+    artifact: decisions
+    local_role: produces_and_consumes
+    description: >-
+      Reasoning trail with confidence labels. Discuss reads existing decisions
+      through bounded `agentera state decisions list --limit 20 --format json`
+       discovery plus exact `agentera state decisions get --id ID --format json`
+      retrieval 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: vision
+    local_role: produces_and_consumes
+    description: >-
+      Discuss may update project direction only with explicit user
+      confirmation when a decision feeds into project direction. Read for
+      context during deliberation.
+  3:
+    id: A3
+    artifact: todo
+    local_role: produces_and_consumes
+    description: >-
+      Discuss may add tech debt items surfaced during deliberation only with
+      explicit user confirmation. Severity per protocol SI1-SI4.
+  4:
+    id: A4
+    artifact: objective
+    local_role: produces_and_consumes
+    description: >-
+      Discuss may write optimization decisions only with explicit user
+      confirmation when a decision feeds into what to optimize.
+  5:
+    id: A5
+    artifact: profile
+    local_role: consumes
+    description: >-
+      Discuss reads this at session start to acknowledge high-confidence
+      entries and avoid re-deliberating settled ground.
+  6:
+    id: A6
+    artifact: docs
+    local_role: consumes
+    description: >-
+      Discuss reads this first to resolve project-local artifact mappings.

package/bundle/skills/agentera/capabilities/{resonera → 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