agentera 3.0.0-dev.5 → 3.0.0-dev.51

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

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

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

@@ -1,58 +0,0 @@
-TRIGGERS:
-  1:
-    id: T1
-    description: >-
-      Direct invocation by name or slash command. Matches when the user
-      explicitly requests hej.
-    priority: high
-    patterns:
-      - "hej"
-      - "/hej"
-  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"
-  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.
-    priority: medium
-    patterns:
-      - "status"
-      - "dashboard"
-      - "pulse"
-      - "brief"
-      - "brief me"
-      - "update me"
-      - "what needs attention"
-  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"
-  5:
-    id: T5
-    description: >-
-      Fallback. Hej 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:
-      - "*"
-    fallback: true
-    priority: low

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

@@ -1,76 +0,0 @@
-ARTIFACTS:
-  1:
-    id: A1
-    artifact_id: health
-    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
-      severity and confidence scores, trend comparisons, and de facto
-      architecture patterns. During evaluation startup, Inspektera 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;
-      missing or not-checked vision caveats from CLI `evidence_context` are preserved
-      instead of forcing a raw vision read.
-  3:
-    id: A3
-    artifact_id: decisions
-    local_role: consumes
-    description: >-
-      Inspektera 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:
-    id: A4
-    artifact_id: todo
-    local_role: produces_and_consumes
-    description: >-
-      Inspektera 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.
-  5:
-    id: A5
-    artifact_id: progress
-    local_role: consumes
-    description: >-
-      Inspektera 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
-      `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:
-    id: A7
-    artifact_id: design
-    local_role: consumes
-    description: >-
-      Inspektera 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:
-    id: A8
-    artifact_id: docs
-    local_role: consumes
-    description: >-
-      Inspektera 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.
-  9:
-    id: A9
-    artifact_id: profile
-    local_role: consumes
-    description: >-
-      Inspektera 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/schemas/triggers.yaml

@@ -1,38 +0,0 @@
-TRIGGERS:
-  1:
-    id: T1
-    description: >-
-      Direct invocation by name or slash command. Matches when the user
-      explicitly requests inspektera.
-    priority: high
-    patterns:
-      - "inspektera"
-      - "/inspektera"
-  2:
-    id: T2
-    description: >-
-      Audit and codebase health requests. Matches when the user wants to
-      assess codebase health, architecture quality, or structural integrity.
-    priority: medium
-    patterns:
-      - "audit the codebase"
-      - "check code health"
-      - "architecture review"
-      - "find technical debt"
-      - "assess code quality"
-      - "how healthy is this codebase"
-      - "what needs fixing"
-      - "structural review"
-      - "pattern audit"
-      - "dependency check"
-      - "test coverage audit"
-  3:
-    id: T3
-    description: >-
-      Implicit trigger after extended realisera activity. Matches when
-      realisera has run 5+ cycles without a health check and the system
-      detects an overdue audit.
-    priority: medium
-    patterns:
-      - "health check overdue"
-      - "audit after realisera"

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

@@ -1,24 +0,0 @@
-ARTIFACTS:
-  1:
-    id: A1
-    artifact_id: todo
-    local_role: produces
-    description: >-
-      Open problems by severity. Inspirera writes actionable findings here
-      (with user confirmation), classifying each by severity per protocol
-      SF1-SF3. Realisera picks up changes automatically in its next cycle.
-  2:
-    id: A2
-    artifact_id: vision
-    local_role: produces
-    description: >-
-      Inspirera may refine project direction with user confirmation when the
-      analysis shifts thinking about the project's direction.
-  3:
-    id: A3
-    artifact_id: profile
-    local_role: consumes
-    description: >-
-      Inspirera reads this via the effective profile script to weight
-      applicability judgments. If missing, inspirera proceeds without persona
-      grounding.

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

@@ -1,34 +0,0 @@
-TRIGGERS:
-  1:
-    id: T1
-    description: >-
-      Direct invocation by name or slash command. Matches when the user
-      explicitly requests inspirera.
-    priority: high
-    patterns:
-      - "inspirera"
-      - "/inspirera"
-  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"
-  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"

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

@@ -1,39 +0,0 @@
-TRIGGERS:
-  1:
-    id: T1
-    description: >-
-      Direct invocation by name or slash command. Matches when the user
-      explicitly requests optimera.
-    priority: high
-    patterns:
-      - "optimera"
-      - "/optimera"
-  2:
-    id: T2
-    description: >-
-      Metric-driven optimization requests. Matches when the user wants to
-      improve a concrete, quantifiable property of their codebase.
-    priority: medium
-    patterns:
-      - "optimize"
-      - "improve performance"
-      - "reduce latency"
-      - "increase test coverage"
-      - "lower bundle size"
-      - "speed up"
-      - "make faster"
-      - "make smaller"
-      - "get the score up"
-      - "hit the target"
-      - "improve the metric"
-  3:
-    id: T3
-    description: >-
-      Iterative experimentation requests. Matches when the user wants to
-      run experiments, benchmark, or iterate on a measurable objective.
-    priority: medium
-    patterns:
-      - "benchmark and iterate"
-      - "run experiments"
-      - "tune"
-      - "experiment until"

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

@@ -1,64 +0,0 @@
-ARTIFACTS:
-  1:
-    id: A1
-    artifact_id: plan
-    local_role: produces_and_consumes
-    description: >-
-      Orkestrera consumes plan task queue state through
-      `agentera prime --context orkestrera --format json` before raw
-      artifact access, then updates status (pending -> complete/blocked) only
-      when resolving a task.
-  2:
-    id: A2
-    artifact_id: progress
-    local_role: consumes
-    description: >-
-      Orkestrera consumes progress verification state from the returned
-      orchestration context first, then routine CLI fallback output before any
-      last-resort raw artifact read for the Step 3 presence check.
-  3:
-    id: A3
-    artifact_id: health
-    local_role: consumes
-    description: >-
-      Orkestrera consumes returned health state first after plan completion to
-      decide whether to start a new plan cycle; raw reads are last-resort after
-      listed CLI fallbacks.
-  4:
-    id: A4
-    artifact_id: todo
-    local_role: produces
-    description: >-
-      Orkestrera consumes TODO caveats from CLI startup context and writes
-      blocked task logging only when a task exhausts its retry budget.
-  5:
-    id: A5
-    artifact_id: decisions
-    local_role: consumes
-    description: >-
-      Orkestrera consumes included decision context or the listed
-      `agentera decisions --format json` fallback before raw access, preserving
-      firm constraints, exploratory uncertainties, and compacted-entry caveats.
-  6:
-    id: A6
-    artifact_id: vision
-    local_role: consumes
-    description: >-
-      Orkestrera consumes returned vision state or missing-state caveats during
-      bootstrap when chaining inspirera for vision-gap analysis.
-  7:
-    id: A7
-    artifact_id: profile
-    local_role: consumes
-    description: >-
-      Orkestrera consumes returned profile status and caveats first for persona
-      context. If missing or stale, it proceeds without refreshing profile
-      state and preserves the caveat.
-  8:
-    id: A8
-    artifact_id: docs
-    local_role: consumes
-    description: >-
-      Orkestrera uses docs mapping from CLI startup context first to resolve
-      project-local artifact mappings before any last-resort raw artifact read
-      or artifact write.

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

@@ -1,42 +0,0 @@
-TRIGGERS:
-  1:
-    id: T1
-    description: >-
-      Direct invocation by name or slash command. Matches when the user
-      explicitly requests orkestrera.
-    priority: high
-    patterns:
-      - "orkestrera"
-      - "/orkestrera"
-  2:
-    id: T2
-    description: >-
-      Multi-cycle execution signals. Matches when the user wants to execute
-      an entire plan autonomously or run tasks through evaluation gating.
-    priority: medium
-    patterns:
-      - "run the plan"
-      - "execute the plan"
-      - "run all tasks"
-      - "keep going until done"
-      - "run through the plan"
-      - "build everything"
-  3:
-    id: T3
-    description: >-
-      Orchestration and delegation signals. Matches when the user wants to
-      chain multiple capabilities, delegate work, or coordinate multi-step
-      execution.
-    priority: medium
-    patterns:
-      - "orchestrate"
-      - "orchestrate skills"
-      - "multi-cycle"
-  4:
-    id: T4
-    description: >-
-      Autonomous plan execution signals. Matches when the user wants
-      evaluated, plan-driven development without manual intervention.
-    priority: medium
-    patterns:
-      - "autonomous plan execution"

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

@@ -1,120 +0,0 @@
-VALIDATION:
-  1:
-    id: V1
-    rule: never_read_source
-    description: >-
-      Orkestrera MUST NEVER read implementation source code. It dispatches
-      capabilities; it does not implement. Artifact files (PLAN.md, HEALTH.md,
-      DECISIONS.md, PROGRESS.md, etc.) are not source code and are expected
-      to be read. This rule verifies the prose explicitly states the
-      source-code read prohibition.
-    severity: critical
-    checks:
-      - "orkestrera prose (packages/cli/src/capabilities/orkestrera/instructions.ts) contains NEVER read implementation source code"
-  2:
-    id: V2
-    rule: evaluation_gate_required
-    description: >-
-      Every completed task MUST be verified by inspektera before being marked
-      complete. The orchestrator MUST NOT skip evaluation. This rule verifies
-      the prose contains the never-skip-evaluation safety rail.
-    severity: critical
-    checks:
-      - "orkestrera prose contains NEVER skip evaluation"
-  3:
-    id: V3
-    rule: retry_budget_enforced
-    description: >-
-      No task may be retried more than 2 times. After the second failure,
-      the task must be marked blocked. This rule verifies the retry budget
-      is stated in the prose and safety rails.
-    severity: critical
-    checks:
-      - "orkestrera prose contains retry budget of 2"
-  4:
-    id: V4
-    rule: exit_marker_required
-    description: >-
-      Every orkestrera invocation MUST emit an exit marker. The marker uses
-      the canonical glyph ⎈ (SG12) in the format ⎈ orkestrera · <status>
-      where status is one of EX1-EX4.
-    severity: critical
-    checks:
-      - "orkestrera prose contains exit marker with glyph ⎈ (SG12)"
-      - "orkestrera prose references exit signals EX1-EX4"
-  5:
-    id: V5
-    rule: orchestrator_read_only_artifacts
-    description: >-
-      The orchestrator reads artifacts and updates PLAN.md task statuses and
-      TODO.md blocked entries. It does NOT write to PROGRESS.md, CHANGELOG.md,
-      or any other capability-owned artifact. This rule verifies the
-      artifacts schema reflects this constraint.
-    severity: warning
-    checks:
-      - "PROGRESS.md is consumes only (not produces)"
-      - "HEALTH.md is consumes only (not produces)"
-      - "DECISIONS.md is consumes only (not produces)"
-      - "VISION.md is consumes only (not produces)"
-  6:
-    id: V6
-    rule: orchestration_context_first
-    description: >-
-      Orkestrera startup and evaluation MUST use
-      `agentera prime --context orkestrera --format json` and the
-      returned orchestration context before raw plan, progress, health, TODO,
-      or decisions artifact reads.
-    severity: critical
-    checks:
-      - "orkestrera prose contains agentera prime --context orkestrera --format json"
-      - "orkestrera prose contains Use the returned `orchestration_context` before raw plan, progress, health, TODO, or decisions artifacts"
-      - "orkestrera prose contains If `source_contract.complete_for_orchestration_context` is true, do not read raw plan, progress, health, TODO, or decisions artifacts"
-  7:
-    id: V7
-    rule: cli_fallback_before_raw_read
-    description: >-
-      When orchestration context is incomplete, Orkestrera MUST run listed
-      routine CLI fallback commands before any last-resort raw artifact read.
-    severity: critical
-    checks:
-      - "orkestrera prose contains run the listed routine CLI fallback commands"
-      - "orkestrera prose contains Read a raw artifact only as a last-resort diagnostic"
-  8:
-    id: V8
-    rule: caveats_preserved_for_evaluation
-    description: >-
-      Orkestrera MUST preserve compacted-decision, stale health/profile/app,
-      missing-state, and retry-state provenance caveats when handing a task to
-      inspektera.
-    severity: critical
-    checks:
-      - "orkestrera prose contains compacted decision caveats"
-      - "orkestrera prose contains stale health/profile/app caveats"
-      - "orkestrera prose contains retry-state provenance"
-  9:
-    id: V9
-    rule: satisfaction_authority_boundary
-    description: >-
-      When Orkestrera touches decision satisfaction, it may pass through or request
-      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 or claim it proved user intent.
-    severity: critical
-    checks:
-      - "Provisional satisfaction requires evidence"
-      - "Only the user confirms final satisfaction"
-      - "Missing or compacted satisfaction caveats are preserved"
-  10:
-    id: V10
-    rule: inspektera_citation_required
-    description: >-
-      Orkestrera Step 3 Surface 2 inspektera delegation MUST require a
-      citation: <file>:<line> (or not-applicable: <reason>) for every WARN and
-      FAIL finding, and require verify_command for WARN rows with file:line
-      citations. Authority: references/cli/capability-instruction-contract.yaml#evaluator_handoff.
-    severity: critical
-    checks:
-      - "orkestrera prose contains citation: `<file>:<line>` OR `not-applicable: <reason>`"
-      - "orkestrera prose contains verify_command"
-      - "orkestrera prose contains evaluator_handoff.output_requirements"

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

@@ -1,62 +0,0 @@
-ARTIFACTS:
-  1:
-    id: A1
-    artifact_id: plan
-    local_role: produces_and_consumes
-    description: >-
-      Active plan with tasks, dependencies, and behavioral acceptance criteria.
-      Planera writes this during the planning session and may read existing
-      plan context before replacing or refining it.
-  2:
-    id: A2
-    artifact_id: plan_archive
-    local_role: produces
-    description: >-
-      Created when a plan is fully
-      executed or explicitly discarded by the user. Preserved for historical
-      reference.
-  3:
-    id: A3
-    artifact_id: vision
-    local_role: consumes
-    description: >-
-      Planera reads this during Orient to understand project direction and
-      align the plan with the vision.
-  4:
-    id: A4
-    artifact_id: decisions
-    local_role: consumes
-    description: >-
-      Planera reads firm (DL1) entries only as hard constraints for planning.
-  5:
-    id: A5
-    artifact_id: todo
-    local_role: consumes
-    description: >-
-      Planera reads this to identify related known
-      issues that the plan should address.
-  6:
-    id: A6
-    artifact_id: health
-    local_role: consumes
-    description: >-
-      Planera reads this to factor structural issues into the plan.
-  7:
-    id: A7
-    artifact_id: progress
-    local_role: consumes
-    description: >-
-      Planera reads this to understand what was built recently.
-  8:
-    id: A8
-    artifact_id: profile
-    local_role: consumes
-    description: >-
-      Planera reads this to calibrate planning depth and pattern preferences.
-  9:
-    id: A9
-    artifact_id: docs
-    local_role: consumes
-    description: >-
-      Planera reads this first to resolve project-local artifact mappings and
-      reads the versioning block for version bump task generation.

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

@@ -1,34 +0,0 @@
-TRIGGERS:
-  1:
-    id: T1
-    description: >-
-      Direct invocation by name or slash command. Matches when the user
-      explicitly requests planera for structured planning.
-    priority: high
-    patterns:
-      - "planera"
-      - "/planera"
-  2:
-    id: T2
-    description: >-
-      Planning requests. Matches when the user wants to create a plan,
-      break work down, or specify requirements before building.
-    priority: medium
-    patterns:
-      - "plan this"
-      - "write a plan"
-      - "break this down"
-      - "decompose this"
-      - "spec this out"
-      - "plan before building"
-  3:
-    id: T3
-    description: >-
-      Architectural planning signals. Matches when the user is asking how
-      to approach building something or when the work is too large for a
-      single development cycle.
-    priority: medium
-    patterns:
-      - "how should we build this"
-      - "multi-step feature"
-      - "this is too big for one cycle"