agentera 3.0.0-dev.7 → 3.0.0-dev.74

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

@@ -1,7 +1,7 @@
 ARTIFACTS:
   1:
     id: A1
-    artifact_id: todo
+    artifact: todo
     local_role: produces
     description: >-
       Open problems by severity. Research writes actionable findings here
@@ -9,16 +9,16 @@ ARTIFACTS:
       SF1-SF3. Build picks up changes automatically in its next cycle.
   2:
     id: A2
-    artifact_id: vision
+    artifact: vision
     local_role: produces
     description: >-
       Research may refine project direction with user confirmation when the
       analysis shifts thinking about the project's direction.
   3:
     id: A3
-    artifact_id: profile
+    artifact: profile
     local_role: consumes
     description: >-
-      Research reads this via the effective profile script to weight
-      applicability judgments. If missing, research proceeds without persona
-      grounding.
+      Research reads the profile via research_context.profile from the prime
+      context to weight applicability judgments. If missing, research proceeds
+      without persona grounding.

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

@@ -1,40 +1,16 @@
 TRIGGERS:
   1:
     id: T1
-    description: >-
-      Direct invocation by name or slash command. Matches when the user
-      explicitly requests research.
+    description: Research requests that analyze external sources, repositories, or approaches.
     priority: high
-    patterns:
-      - "research"
-      - "/research"
-    confidence_threshold: 55
   2:
     id: T2
-    description: >-
-      Applicability assessment requests. Matches when the user provides
-      an external URL and asks how it applies to their project or whether
-      they should adopt it.
-    priority: medium
-    patterns:
-      - "could I use this in"
-      - "how does this apply to my project"
-      - "is this relevant to"
-      - "what can I take from this"
-      - "should I adopt"
-    confidence_threshold: 45
+    description: Assess an external source's relevance, applicability, or adoption.
+    priority: high
   3:
     id: T3
-    description: >-
-      External resource review requests. Matches when the user wants
-      analysis of a library, repo, or approach for ideas and patterns.
-    priority: medium
-    patterns:
-      - "what do you think of this library"
-      - "review this repo for ideas"
-      - "anything worth stealing from"
-      - "how does this compare to what I'm doing"
-    confidence_threshold: 45
+    description: Review an external library, repository, or pattern for ideas.
+    priority: high
     disambiguates_against:
       - capability: audit
         hint: "research reviews external resources for ideas; audit reviews the local codebase for health"

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

@@ -1,63 +1,63 @@
 ARTIFACTS:
   1:
     id: A1
-    artifact_id: vision
+    artifact: vision
     local_role: consumes
     description: >-
       Status reads this for the briefing's project context.
   2:
     id: A2
-    artifact_id: decisions
+    artifact: decisions
     local_role: consumes
     description: >-
       Status reads this to identify unresolved decisions requiring follow-up.
   3:
     id: A3
-    artifact_id: plan
+    artifact: plan
     local_role: consumes
     description: >-
       Status reads this to identify the next executable task and plan progress.
   4:
     id: A4
-    artifact_id: progress
+    artifact: progress
     local_role: consumes
     description: >-
       Status reads this for the briefing's "what shipped" context.
   5:
     id: A5
-    artifact_id: todo
+    artifact: todo
     local_role: consumes
     description: >-
       Status reads this to identify high-severity open items for routing.
   6:
     id: A6
-    artifact_id: health
+    artifact: health
     local_role: consumes
     description: >-
       Status reads this for the health status line and attention items.
   7:
     id: A7
-    artifact_id: objective
+    artifact: objective
     local_role: consumes
     description: >-
       Status reads this to check for active optimization objectives.
   8:
     id: A8
-    artifact_id: experiments
+    artifact: experiments
     local_role: consumes
     description: >-
       Status reads this alongside the active optimization target to determine
       optimization status.
   9:
     id: A9
-    artifact_id: docs
+    artifact: docs
     local_role: consumes
     description: >-
       Status reads this first to resolve project-local artifact mappings before
       reading other artifacts.
   10:
     id: A10
-    artifact_id: design
+    artifact: design
     local_role: consumes
     description: >-
       Status reads this for project design status metadata (exists, stale, missing).
@@ -66,7 +66,8 @@ ARTIFACTS:
       artifact.
   11:
     id: A11
-    artifact_id: profile
+    artifact: profile
     local_role: consumes
     description: >-
-      Status reads this to report profile status (loaded/not found) in the briefing.
+      Status reports profile validity as valid, absent, or repair_needed and
+      keeps freshness separate without exposing profile paths or content.

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

@@ -1,64 +1,22 @@
 TRIGGERS:
   1:
     id: T1
-    description: >-
-      Direct invocation by name or slash command. Matches when the user
-      explicitly requests status.
+    description: Explicit status requests and orientation for the current project.
     priority: high
-    patterns:
-      - "status"
-      - "/status"
-    confidence_threshold: 60
-    borderline_band: 10
   2:
     id: T2
-    description: >-
-      Greetings and session-start signals. Matches casual greetings or
-      explicit session start requests.
-    priority: medium
-    patterns:
-      - "hello"
-      - "hi"
-      - "start"
-      - "begin"
-      - "getting started"
-      - "onboard me"
-    confidence_threshold: 40
+    description: Session-start requests seeking orientation before choosing work.
+    priority: high
   3:
     id: T3
-    description: >-
-      Status and orientation requests. Matches when the user wants to know
-      the current state of the project or get a briefing.
+    description: Current project state, briefing, attention, or progress requests.
     priority: medium
-    patterns:
-      - "status"
-      - "dashboard"
-      - "pulse"
-      - "brief"
-      - "brief me"
-      - "update me"
-      - "what needs attention"
-    confidence_threshold: 45
   4:
     id: T4
-    description: >-
-      Returning-to-project signals. Matches when the user resumes work
-      on a known project and wants to pick up where they left off.
-    priority: medium
-    patterns:
-      - "where were we"
-      - "catch me up"
-      - "what should I work on"
-      - "what's next"
-    confidence_threshold: 45
+    description: Resume-work and “what's next?” requests with no separate requested outcome.
+    priority: high
   5:
     id: T5
-    description: >-
-      Fallback. Status is the default capability when no other capability's
-      trigger patterns match. This entry documents the fallback behavior
-      defined in the routing layer routing logic.
-    patterns:
-      - "*"
+    description: Fallback orientation when no capability fits the request.
     fallback: true
     priority: low
-    confidence_threshold: 0

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

@@ -1,56 +1,56 @@
 ARTIFACTS:
   1:
     id: A1
-    artifact_id: vision
+    artifact: vision
     local_role: produces_and_consumes
     description: >-
       Vision writes and refines project direction, principles, personas,
       aspirations, and identity.
   2:
     id: A2
-    artifact_id: decisions
+    artifact: decisions
     local_role: consumes
     description: >-
       Vision reads this to detect shifted thinking during refine mode
       and to surface unresolved tensions with the vision.
   3:
     id: A3
-    artifact_id: progress
+    artifact: progress
     local_role: consumes
     description: >-
       Vision reads this during refine mode to understand what has been
       built since the vision was last updated.
   4:
     id: A4
-    artifact_id: health
+    artifact: health
     local_role: consumes
     description: >-
       Vision reads this to understand structural realities that
       constrain or inform the vision.
   5:
     id: A5
-    artifact_id: todo
+    artifact: todo
     local_role: consumes
     description: >-
       Vision reads this during refine mode to detect recurring problems
       that suggest the vision needs adjustment.
   6:
     id: A6
-    artifact_id: design
+    artifact: design
     local_role: consumes
     description: >-
       Vision reads this during codebase exploration to ensure the
       Identity section in project direction coheres with the visual system.
   7:
     id: A7
-    artifact_id: docs
+    artifact: docs
     local_role: consumes
     description: >-
       Vision reads this first to resolve project-local artifact mappings
       before accessing other artifacts.
   8:
     id: A8
-    artifact_id: profile
+    artifact: profile
     local_role: consumes
     description: >-
       Vision reads this to calibrate the vision conversation: high-confidence

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

@@ -3,9 +3,9 @@ EXIT_CONDITIONS:
     id: E1
     condition: complete
     description: >-
-      VISION.md was written (Create/Replace mode) or updated (Refine mode)
-      with explicit user approval. The vision is ambitious, concrete, and
-      structured to sustain autonomous development.
+      The vision artifact was written (Create/Replace mode) or updated
+      (Refine mode) with explicit user approval. The vision is ambitious,
+      concrete, and structured to sustain autonomous development.
     exit_signal: complete
   2:
     id: E2
@@ -14,14 +14,15 @@ EXIT_CONDITIONS:
       The vision was produced but with weaknesses worth surfacing: the user
       settled for a less ambitious or less specific vision than pushed for,
       key sections (personas, principles, direction) are thin due to limited
-      conversation depth, or the vision has unresolved tensions with existing
-      DECISIONS.md entries.
+      conversation depth, or the vision has unresolved tensions with
+      existing decision entries.
     exit_signal: flagged
   3:
     id: E3
     condition: stuck
     description: >-
-      Cannot write VISION.md because the user declined to approve the draft
+      Cannot write the vision artifact because the user declined to approve
+      the draft
       and no actionable revision direction was given, or codebase exploration
       failed in a way that would make the vision unreliable.
     exit_signal: stuck

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

@@ -1,55 +1,23 @@
 TRIGGERS:
   1:
     id: T1
-    description: >-
-      Direct invocation by name or slash command. Matches when the user
-      explicitly requests vision.
+    description: Requests to define or refine the project's vision and direction.
     priority: high
-    patterns:
-      - "vision"
-      - "/vision"
-    confidence_threshold: 60
-    borderline_band: 10
   2:
     id: T2
-    description: >-
-      Vision creation requests. Matches when the user wants to define or
-      create a project vision or north star direction.
-    priority: medium
-    patterns:
-      - "create a vision"
-      - "write VISION.md"
-      - "define the direction"
-      - "set the north star"
-      - "dream bigger"
-    confidence_threshold: 50
+    description: Define a new north star, product direction, or desired future.
+    priority: high
   3:
     id: T3
-    description: >-
-      Vision refinement requests. Matches when the user wants to evolve
-      or rethink an existing vision.
-    priority: medium
-    patterns:
-      - "rethink the vision"
-      - "refine the vision"
-      - "update VISION.md"
-    confidence_threshold: 50
+    description: Refine, rethink, or update an existing vision or north star.
+    priority: high
     disambiguates_against:
       - capability: build
         hint: "vision refines existing project direction; build implements code"
-    patterns_regex:
-      - "\\brefine\\s+the\\s+vision\\b"
-      - "update\\s+VISION\\.md"
   4:
     id: T4
-    description: >-
-      Project bootstrap. Matches when the user wants to bootstrap a new
-      project identity or define what a project should become.
-    priority: medium
-    patterns:
-      - "bootstrap the project"
-      - "what should this project become"
-    confidence_threshold: 50
+    description: Establish a new project's identity or decide what it should become.
+    priority: high
     disambiguates_against:
       - capability: plan
         hint: "vision defines what a project should become; plan structures the work"

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

@@ -3,8 +3,8 @@ VALIDATION:
     id: V1
     rule: user_approval_required
     description: >-
-      VISION.md MUST NOT be written or modified without explicit user
-      approval. Present drafts and get confirmation before writing.
+      The vision artifact MUST NOT be written or modified without explicit
+      user approval. Present drafts and get confirmation before writing.
       This applies to both Create and Refine modes.
     severity: critical
     checks:
@@ -14,12 +14,12 @@ VALIDATION:
     id: V2
     rule: no_realisera_modification
     description: >-
-      VISION.md MUST NOT be modified during a build execution cycle.
-      Vision changes happen only in dedicated vision sessions. This
-      prevents vision drift during autonomous development.
+      The vision artifact MUST NOT be modified during a build execution
+      cycle. Vision changes happen only in dedicated vision sessions.
+      This prevents vision drift during autonomous development.
     severity: critical
     checks:
-      - "VISION.md not written during build cycle"
+      - "Vision artifact not written during build cycle"
   3:
     id: V3
     rule: inspirational_tone
@@ -29,7 +29,7 @@ VALIDATION:
       should inspire and guide, not specify.
     severity: warning
     checks:
-      - "VISION.md is aspirational, not prescriptive"
+      - "The vision artifact is aspirational, not prescriptive"
   4:
     id: V4
     rule: codebase_exploration_required
@@ -51,15 +51,13 @@ VALIDATION:
     checks:
       - "Vision contains specific direction"
       - "Vision contains actionable principles"
-  6:
-    id: V6
-    rule: principle_brevity
-    description: >-
-      Each principle in VISION.md MUST be ≤20 words. Principles are
-      decision guides, not essays. Brevity forces clarity.
-    severity: warning
-    checks:
-      - "Each principle ≤ 20 words"
+  # V6 (principle_brevity) retired per Decision 81: linter does not enforce word
+  # count on principle descriptions; the live vision artifact violates the limit
+  # intentionally (principles carry rationale, not just labels). The
+  # MUST-state-tradeoff / SHOULD-name-prevention / MUST-NOT-name-implementations
+  # rules in capability instructions and the lint abstraction/filler checks
+  # cover principle quality holistically. ID gap (V6 → V7) preserved to avoid
+  # breaking external references to V7.
   7:
     id: V7
     rule: exit_marker_required

package/bundle/skills/agentera/capability_schema_contract.yaml

@@ -48,8 +48,9 @@ ENTRY_SCHEMA:
       type: string
       required: false
       description: >-
-        Advisory relevance-precedence hint the LLM host reads alongside the
-        entry description. Required for all TRIGGERS entries.
+        Advisory relevance-precedence hint a host reads alongside the entry
+        description only after deterministic routing returns semantic_required.
+        Required for all TRIGGERS entries.
         Valid values: high, medium, low.
     deprecated:
       type: boolean
@@ -79,7 +80,7 @@ DIRECTORY_REQUIREMENTS:
       TypeScript module that exports the capability's behavioral instructions
       as a default-exported string constant. The runtime loads it via the
       compiled .js path and surfaces the prose through
-      `agentera prime --context <name> --format json`.
+      `npx -y agentera@next prime --context <name> --format json`.
   schemas_directory:
     path: schemas
     type: directory
@@ -136,32 +137,34 @@ FIELD_RULES:
         - medium
         - low
       description: >-
-        Relevance-precedence hint the LLM host reads when ordering
-        candidate capabilities for a request. See
+        Relevance-precedence hint a host reads when ordering capability intent
+        after deterministic abstention. See
         references/cli/routing-model.md for routing semantics.
 
 TRIGGER_ENRICHMENT:
   description: >-
-    Optional trigger-entry intent-documentation fields. Every field is
-    OPTIONAL: a triggers.yaml entry that omits all enriched fields remains
-    valid. The LLM host consumes description and disambiguates_against at
-    runtime; confidence_threshold, borderline_band, and patterns_regex are
-    retained as shape-validated documentation so triggers.yaml files that
-    carry them still validate.
+    Optional trigger-entry fields. Every field is OPTIONAL: a triggers.yaml
+    entry that omits all enriched fields remains valid. A host consumes
+    disambiguates_against as semantic-phase intent documentation only after
+    deterministic abstention. patterns,
+    confidence_threshold, borderline_band, and patterns_regex are legacy
+    compatibility fields: they remain shape-validated only and never enter the
+    active semantic trigger model.
   spec: references/cli/trigger-schema-enrichment.md
-  contract_defaults:
-    # Default values for optional enriched fields.
-    confidence_threshold: 50
-    borderline_band: 15
   fields:
+    patterns:
+      type: list_of_strings
+      required: false
+      description: >-
+        Legacy matcher strings retained only so existing trigger files load and
+        validate. They are never matched or returned by the active model.
     confidence_threshold:
       type: integer
       required: false
       min: 0
       max: 100
-      default: 50
       description: >-
-        Optional integer 0-100. Not consumed by the LLM host; retained so
+        Legacy integer 0-100. Not consumed by the LLM host; retained so
         triggers.yaml files carrying the field still validate. A non-integer
         or value outside 0..100 fails V7 validation with the valid range
         and the offending entry ID.
@@ -170,25 +173,21 @@ TRIGGER_ENRICHMENT:
       required: false
       min: 0
       max: 100
-      default: 15
       description: >-
-        Optional integer 0-100. Not consumed by the LLM host; retained so
+        Legacy integer 0-100. Not consumed by the LLM host; retained so
         triggers.yaml files carrying the field still validate. A non-integer
         or value outside 0..100 fails V7 validation.
     patterns_regex:
       type: list_of_strings
       required: false
-      default: []
       each_must_be_valid_regex: true
       description: >-
-        Optional list of regex strings. Not consumed by the LLM host;
-        retained so triggers.yaml files carrying the field still validate.
-        The loader compiles each entry during validation; a compile failure
-        fails V7 validation naming the offending entry and pattern.
+        Legacy list of regex strings. Not consumed by the LLM host; retained
+        so triggers.yaml files carrying the field still validate. The loader
+        syntax-validates each entry but never returns a RegExp or matches it.
     disambiguates_against:
       type: list_of_mappings
       required: false
-      default: []
       description: >-
         Declares which other capabilities this trigger's intent could be
         confused with, with a hint the LLM host consults when a request could
@@ -282,7 +281,7 @@ ROUTE_ALIASES:
   canonical_name_precedence: true
   cli_boundary: >-
     Slash routes and state commands are distinct: `/agentera plan` routes to
-    the plan capability, while `agentera state plan` remains the
+    the plan capability, while `agentera state plan list` remains the
     state-oriented CLI command for reading plan state. Do not add capability or
     alias commands to the CLI.
   primary_aliases:
@@ -410,7 +409,7 @@ ARTIFACTS:
       Behavioral instructions the agent reads. TypeScript module that exports
       a default-exported string constant. The runtime loads it via the
       compiled .js path and serves the prose through
-      `agentera prime --context <name> --format json`.
+      `npx -y agentera@next prime --context <name> --format json`.
     produces: false
     consumes: true
   4:
@@ -497,13 +496,14 @@ VALIDATION:
     description: >-
       Trigger entries MAY carry the optional intent-documentation fields
       defined in TRIGGER_ENRICHMENT. Enrichment is opt-in per entry;
-      triggers omitting every enriched field remain valid.
-      confidence_threshold, borderline_band, and patterns_regex are
-      retained as shape-validated documentation; disambiguates_against
-      is consumed by the LLM host at runtime. Validating an entry with
-      enriched fields fails when the rules below are violated.
+      triggers omitting every enriched field remain valid. patterns,
+      confidence_threshold, borderline_band, and patterns_regex are legacy
+      compatibility fields only; disambiguates_against is consumed by the
+      LLM host at runtime. Validating an entry with enriched fields fails
+      when the rules below are violated.
     severity: error
     checks:
+      - "patterns, when present, is a list of strings"
       - "confidence_threshold, when present, is an integer in 0..100"
       - "borderline_band, when present, is an integer in 0..100"
       - "patterns_regex entries are strings that compile as regular expressions"

package/bundle/skills/agentera/protocol.yaml

@@ -432,8 +432,8 @@ PHASES:
   2:
     id: PH2
     value: deliberate
-    capabilities: [discuss]
-    purpose: "Reason through decisions before committing to a direction"
+    capabilities: [discuss, research]
+    purpose: "Reason through decisions or external evidence before committing to a direction"
     valid_successors: [plan, build, envision]
     terminal: false
     self_transition: false
@@ -448,8 +448,8 @@ PHASES:
   4:
     id: PH4
     value: build
-    capabilities: [build, optimize, document, design]
-    purpose: "Implement, optimize, document, or design"
+    capabilities: [build, optimize, document, profile, design]
+    purpose: "Implement, optimize, document, profile, or design"
     valid_successors: [build, audit, plan]
     terminal: true
     self_transition: true