agentera 3.0.0-dev.4 → 3.0.0-dev.46

package/bundle/references/cli/routing-execution-vocabulary.yaml

@@ -1,281 +0,0 @@
-schema_version: agentera.routing_execution_vocabulary.v1
-status: active_authority
-purpose: >-
-  Define routing and execution vocabulary boundaries so request routing, next-action
-  recommendation, Orkestrera task assignment, worker launch, runtime support, and
-  worker-safety Git commits stay distinct without forcing mechanical renames of
-  shipped compatibility identifiers or historical evidence.
-sources:
-  prose:
-    - references/cli/vocabulary.md#routing-and-execution-vocabulary
-scope:
-  includes:
-    - Request-to-capability routing through the Agentera skill entry point.
-    - Hej and capability next-action recommendations that wait for confirmation.
-    - Orkestrera assignment of approved plan work to worker capabilities.
-    - Realisera and Optimera launch of runtime workers.
-    - Runtime subagent support mechanisms and compatibility identifiers.
-    - Git commit safety language before spawning isolated worker execution.
-  excludes:
-    - Broad current-prose replacement across capability instructions.
-    - Repository-wide ambiguous dispatcher/dispatch/router/conductor occurrence rejection.
-    - Capability instruction-file rename work.
-    - "`first_invocation_read` metadata or startup-read behavior."
-    - Objective state, decision satisfaction state, package publication, and installed app refreshes.
-compatibility_boundary: >-
-  Compatibility identifiers, code symbols, fixture names, literal paths, archived
-  plans, changelog/progress/decision history, and concrete runtime API names may
-  keep older dispatcher, dispatch, conductor, worktree dispatch, and pre-dispatch
-  wording when the spelling is the contract or historical evidence. New conceptual
-  prose should use the canonical concept terms below.
-canonical_concept_order:
-  - request_to_capability_routing
-  - next_action_recommendation
-  - orkestrera_task_assignment
-  - worker_launch
-  - runtime_subagent_support
-  - worker_safety_git_commit
-canonical_concepts:
-  request_to_capability_routing:
-    definition: >-
-      Agentera chooses the capability that should handle a user request, using
-      direct routes, primary route aliases, trigger schemas, disambiguation, or
-      fallback to hej.
-    preferred_terms:
-      - Agentera router
-      - request-to-capability routing
-      - route
-      - routing
-    forbidden_ambiguous_shortcuts:
-      - master dispatcher
-      - bare dispatch
-      - skill dispatcher
-      - conductor
-  next_action_recommendation:
-    definition: >-
-      A capability recommends a concrete next capability or action and waits for
-      user confirmation before state-changing work begins.
-    preferred_terms:
-      - suggest
-      - suggestion
-      - next-action recommendation
-      - suggested next action
-    forbidden_ambiguous_shortcuts:
-      - dispatch
-      - force
-      - chain
-      - conductor handoff
-  orkestrera_task_assignment:
-    definition: >-
-      Orkestrera assigns approved plan work to a worker capability during an
-      explicitly orchestrated flow; it evaluates the result instead of implementing
-      the task itself.
-    preferred_terms:
-      - delegate
-      - delegation
-      - Orkestrera task delegation
-      - assigned plan work
-    forbidden_ambiguous_shortcuts:
-      - conductor
-      - conductor protocol
-      - dispatch
-      - orchestrator implementation
-  worker_launch:
-    definition: >-
-      Realisera or Optimera starts a worker through the host runtime when an
-      implementation or measurement cycle needs isolated execution.
-    preferred_terms:
-      - spawn
-      - spawn worker
-      - worker spawn
-      - worker launch
-    forbidden_ambiguous_shortcuts:
-      - dispatch
-      - worktree dispatch
-      - subagent dispatch
-      - launch substrate
-  runtime_subagent_support:
-    definition: >-
-      Runtime-specific support that lets Agentera use a host's subagent surface,
-      descriptor model, or equivalent worker mechanism.
-    preferred_terms:
-      - subagent mechanism
-      - runtime subagent mechanism
-      - host subagent mechanism
-      - runtime worker mechanism
-    forbidden_ambiguous_shortcuts:
-      - runtime dispatch substrate
-      - dispatch substrate
-      - subagent dispatch
-      - adapter dispatch
-  worker_safety_git_commit:
-    definition: >-
-      The Git-only commit synchronization required before spawning isolated worker
-      execution so the worker starts from a coherent base.
-    preferred_terms:
-      - pre-spawn Git commit
-      - pre-spawn commit
-      - Git commit before spawning workers
-      - commit before worker spawn
-    forbidden_ambiguous_shortcuts:
-      - pre-dispatch commit
-      - pre-dispatch checkpoint commit
-      - pre-dispatch commit gate
-      - checkpoint before dispatch
-classification_order:
-  - canonical_concept
-  - compatibility_identifier
-  - code_identifier
-  - path_like_reference
-  - historical_record
-  - fixture_only
-  - generic_plain_language
-  - ambiguous_current_prose
-classification_rules:
-  canonical_concept:
-    meaning: Usage matches one of the canonical concepts and uses a preferred term.
-    action: Keep and prefer in new current prose.
-  compatibility_identifier:
-    meaning: The spelling is a shipped field, command flag, runtime group name, descriptor key, or parseable label.
-    action: Preserve until an explicit migration exists.
-  code_identifier:
-    meaning: The spelling is a Python, JavaScript, TOML, YAML, test, or API identifier consumed by code or runtime descriptors.
-    action: Preserve unless a code migration is explicitly in scope.
-  path_like_reference:
-    meaning: The occurrence is a literal file path, glob, manifest path, fixture path, archive path, or code path.
-    action: Preserve the concrete path spelling.
-  historical_record:
-    meaning: The occurrence is in changelog, progress, decision, archived plan, migration history, or release evidence.
-    action: Do not rewrite solely for vocabulary cleanup; qualify when current prose interprets it.
-  fixture_only:
-    meaning: The occurrence is test fixture input, expected compatibility output, stale-path data, or semantic-eval evidence.
-    action: Preserve when the test proves compatibility or rejection behavior.
-  generic_plain_language:
-    meaning: The occurrence is ordinary English unrelated to Agentera routing, recommendation, orchestration assignment, worker launch, runtime support, or Git safety.
-    action: Allowed, but prefer object-specific terms when risk is high.
-  ambiguous_current_prose:
-    meaning: The occurrence uses dispatcher, dispatch, router, conductor, worktree dispatch, runtime dispatch substrate, or pre-dispatch commit language as a conceptual shortcut in current prose.
-    action: Replace or qualify with the relevant canonical concept term.
-focused_scan:
-  allowed_classifications:
-    - canonical
-    - compatibility-preserved
-    - historical
-    - fixture-only
-    - code-identifier
-    - generic
-  paths:
-    - AGENTS.md
-    - references/cli/vocabulary.md
-    - references/adapters/runtime-feature-parity.md
-    - (retired maintainer measurement tool)
-    - skills/agentera/SKILL.md
-    - skills/agentera/references/contract.md
-    - skills/agentera/capabilities/realisera/instructions.md
-    - skills/agentera/capabilities/optimera/instructions.md
-    - skills/agentera/capabilities/orkestrera/instructions.md
-    - tests/test_skill_dispatch_contract.py
-    - tests/test_runtime_adapters.py
-    - tests/test_runtime_adapter_registry.py
-  allowed_occurrences:
-    - path: ^AGENTS\.md$
-      text: Agentera router routes incoming requests
-      classification: canonical
-      reason: AGENTS names the canonical request-to-capability routing term.
-    - path: ^references/cli/vocabulary\.md$
-      text: Agentera router|request-to-capability routing|suggest|delegate|spawn|subagent mechanism|pre-spawn Git commit
-      classification: canonical
-      reason: Vocabulary docs present the canonical routing and execution terms.
-    - path: ^references/cli/vocabulary\.md$
-      text: pre-dispatch commit gate|pre-dispatch checkpoint commit|Conductor protocol|orchestration loop|The loop is select, dispatch, evaluate, resolve, and log
-      classification: historical
-      reason: Decision 44 and glossary tables preserve deprecated wording as historical examples.
-    - path: ^references/cli/vocabulary\.md$
-      text: dispatching cycles|dispatcher rule governs hej and capability handoff prompts
-      classification: canonical
-      reason: Handoff guidance uses dispatch only for the Orkestrera-owned autonomous orchestration flow.
-    - path: ^references/cli/vocabulary\.md$
-      text: subagent_dispatch|fixture names
-      classification: compatibility-preserved
-      reason: Routing vocabulary docs preserve explicit compatibility identifiers and fixture terminology.
-    - path: ^references/adapters/runtime-feature-parity\.md$
-      text: prompt rewrite router|Subagent Dispatch|Dispatch surface|Capability dispatch|subagent dispatch
-      classification: compatibility-preserved
-      reason: Runtime parity docs name concrete host and compatibility surfaces around descriptor dispatch support.
-    - path: ^scripts/measure_token_payload\.py$
-      text: static dispatch payload|Agentera router
-      classification: historical
-      reason: The payload metric retains the historical dispatch-payload measurement name while listing canonical contents.
-    - path: ^skills/agentera/SKILL\.md$
-      text: '`dispatch`: invoke another capability autonomously|`chain`: dispatch multiple capabilities autonomously'
-      classification: canonical
-      reason: Agentera router guidance reserves dispatch and chain for explicitly owned orchestration flows.
-    - path: ^skills/agentera/references/contract\.md$
-      text: '\| hej \| \(router; reads artifacts but produces none\) \|'
-      classification: canonical
-      reason: The contract uses router for the hej request-routing role.
-    - path: ^skills/agentera/references/contract\.md$
-      text: Dispatch the skill via the eval mechanism capability
-      classification: generic
-      reason: Evaluation-gate prose uses dispatch as ordinary test-run invocation wording, not Agentera routing authority.
-    - path: ^skills/agentera/references/contract\.md$
-      text: checkpoint before worktree dispatch
-      classification: compatibility-preserved
-      reason: The contract preserves the parseable historical checkpoint commit message string.
-    - path: ^skills/agentera/capabilities/realisera/instructions\.md$
-      text: 'Step 5: Dispatch|checkpoint before worktree dispatch'
-      classification: compatibility-preserved
-      reason: Realisera preserves the current step heading and checkpoint commit message compatibility string.
-    - path: ^skills/agentera/capabilities/optimera/instructions\.md$
-      text: checkpoint before worktree dispatch
-      classification: compatibility-preserved
-      reason: Optimera preserves the current checkpoint commit message compatibility string.
-    - path: ^skills/agentera/capabilities/orkestrera/instructions\.md$
-      text: review pressure in dispatch|dispatch/evaluation context|`dispatch` and `chain` are autonomous orchestration verbs
-      classification: canonical
-      reason: Orkestrera capability prose uses dispatch for its explicitly owned orchestration loop.
-    - path: ^tests/test_skill_dispatch_contract\.py$
-      text: '`dispatch`: invoke another capability autonomously|`chain`: dispatch multiple capabilities autonomously|In orkestrera only, `dispatch` and `chain` are autonomous'
-      classification: fixture-only
-      reason: Skill dispatch contract tests assert the canonical Orkestrera dispatch reservation.
-    - path: ^tests/test_runtime_adapters\.py$
-      text: opencode bare-hej router|routeBareHejMessage|subagent_dispatch
-      classification: fixture-only
-      reason: Runtime adapter tests assert plugin routing helpers and compatibility identifier fixtures.
-    - path: ^tests/test_runtime_adapter_registry\.py$
-      text: subagent_dispatch
-      classification: code-identifier
-      reason: Runtime adapter registry tests preserve the shipped subagent_dispatch field name.
-compatibility_identifiers:
-  runtime_adapter:
-    - subagent_dispatch
-    - RuntimeAdapter.subagent_dispatch
-    - subagent_dispatch.supported
-    - subagent_dispatch.group
-  route_aliases:
-    - ROUTE_ALIASES
-    - primary_aliases
-  command_and_schema_surfaces:
-    - agentera validate descriptors
-    - descriptor_sources
-    - invocation_pattern
-code_identifiers:
-  - subagent_dispatch
-  - test_runtime_adapter_subagent_dispatch_metadata_is_complete
-  - test_cross_runtime_capability_subagent_dispatch_support
-historical_terms:
-  - pre-dispatch commit
-  - pre-dispatch checkpoint commit
-  - pre-dispatch commit gate
-  - worktree dispatch
-  - runtime dispatch substrate
-  - master dispatcher
-  - conductor protocol
-fixture_terms:
-  - subagent_dispatch fixture
-  - worktree dispatch fixture
-docs_delegation:
-  document: references/cli/vocabulary.md
-  required_anchor: Routing and execution vocabulary
-  authority_path: references/cli/routing-execution-vocabulary.yaml
-  must_not_duplicate_large_table: true

package/bundle/references/meta/documentation-inventory.md

@@ -1,43 +0,0 @@
-# Documentation and file inventory
-
-Maintainer inventory of repository documentation, workpapers, and legacy surfaces.
-Authoritative Agentera docs live under `references/`, `skills/agentera/`, and root
-guides — not under `docs/`.
-
-**Last reviewed:** 2026-05-23
-
-## Authority stack
-
-| Layer | Location |
-| --- | --- |
-| Protocol | `skills/agentera/protocol.yaml` |
-| CLI vocabulary authorities | `references/cli/*.yaml` |
-| Vocabulary index (normalization, Decision 44) | `references/cli/vocabulary-index.yaml` |
-| Human vocabulary index | `references/cli/vocabulary.md` |
-| Benchmark contract | `references/analysis/startup-measurement-contract.yaml` |
-| Benchmark runbook | `references/analysis/benchmark.md` |
-| JSON surface budgets | `scripts/json_output_surface_manifest.yaml` |
-| Project drafts | `docs/` (gitignored except `docs/README.md`) |
-
-## `docs/` policy
-
-`docs/` is for **non-authoritative** local notes only. Nothing under `docs/` ships
-in the Agentera app bundle.
-
-## Archived workpapers
-
-| Archive path | Former location |
-| --- | --- |
-| `.agentera/archive/d47-app-home-vocabulary-inventory.md` | `docs/d47-app-home-vocabulary-inventory.md` |
-| `.agentera/archive/d58-json-output-surface-inventory.md` | `docs/d58-json-output-surface-inventory.md` |
-| `.agentera/archive/d59-json-output-budget-proposal.md` | `docs/d59-json-output-budget-proposal.md` |
-| `.agentera/archive/d59-json-output-closeout-measurements.md` | `docs/d59-json-output-closeout-measurements.md` |
-| `.agentera/archive/gap-analysis-2026-05-05.md` | `.agentera/gap-analysis-2026-05-05.md` |
-
-Live JSON enforcement uses `scripts/json_output_surface_manifest.yaml` only.
-
-## Remaining cleanup (see TODO.md)
-
-- Replace live `SPEC.md` references in `UPGRADE.md`, hooks, adapter docs, `contract.md`
-- Refresh or drop assertions against pre-migration characterization snapshots
-- Agentera 3.0: remove `skills/hej/` bridge and `references/v1-section-mapping.md`

package/bundle/references/v1-section-mapping.md

@@ -1,47 +0,0 @@
-# v1-to-v2 Section Mapping
-
-Maps every behavioral section in the 12 v1 SKILL.md files to the v2 capability schema groups.
-No unmappable content.
-
-## Mapping Table
-
-| v1 Section | v2 Target | Rationale |
-|---|---|---|
-| Frontmatter: `name`, `description` | `instructions.md` (header) + `TRIGGERS` group | Name is prose identity. Description is prose metadata. Trigger patterns extracted to TRIGGERS entries. |
-| Frontmatter: `spec_sections` | Dropped | SPEC.md dissolves into per-capability schemas (ROADMAP: "Spec dissolves into schemas"). No central spec to reference. |
-| `## State artifacts` (artifact list) | `ARTIFACTS` group | Each consumed/produced artifact becomes an ARTIFACTS entry with stable ID. |
-| `### Artifact path resolution` | `ARTIFACTS` group (path metadata) | Path resolution rules become path field metadata on artifact entries. |
-| `### Contract` (inlined values) | `VALIDATION` group + `protocol.yaml` | Inlined contract values (severity arrows, trend arrows, glyphs, token budgets) become shared protocol primitives referenced by VALIDATION entries. |
-| `references/contract.md` | `protocol.yaml` | Centralized contract reference replaced by shared protocol schema. |
-| `## Step N: ...` (workflow steps) | `instructions.md` | Behavioral instructions the agent reads. Steps remain prose. |
-| `## Brainstorm: ...` (sub-workflows) | `instructions.md` | Interactive sub-workflows are behavioral instructions. |
-| `## Personality` / `## Interaction rules` | `instructions.md` | Personality and interaction rules are agent-facing behavioral guidance. |
-| `## Safety rails` | `VALIDATION` group | Each safety rail becomes a VALIDATION entry with rule, severity, and checks. |
-| `## Exit signals` | `EXIT_CONDITIONS` group | Each exit signal becomes an EXIT_CONDITIONS entry with condition, description, and exit_code. |
-| `## Cross-skill integration` | `ARTIFACTS` group (cross-capability refs) + `instructions.md` | Cross-skill dependencies become ARTIFACTS entries with cross-capability ID references. Integration guidance stays in prose. |
-| `## Getting started` | `instructions.md` | First-run guidance is behavioral instruction. |
-| `references/templates/` | `instructions.md` (embedded or referenced) | Templates are part of the capability's behavioral instructions. |
-| `scripts/` (Python helpers) | Kept at repo level or capability-local | Scripts are tooling, not behavioral. Location unchanged for v2. |
-
-## Per-Skill Coverage
-
-Every section found in each v1 SKILL.md is covered by the mapping above. Verification:
-
-| Skill | Sections | All Mapped? |
-|---|---|---|
-| dokumentera | State artifacts, Contract, Conventions, Artifact Mapping, Index, Steps 0, First-run, Intent-first, Explore-and-generate, Update-and-verify, Safety rails, Exit signals, Cross-skill, Getting started | Yes |
-| hej | State artifacts, Contract, Steps 0-2 (Detect, Welcome, Briefing, Route), Safety rails, Exit signals, Cross-skill, Getting started | Yes |
-| inspektera | State artifacts, Contract, Audit template, Steps 1-7, Dimensions, Evidence, Confidence, Findings, Safety rails, Exit signals, Cross-skill, Getting started | Yes |
-| inspirera | Steps 1-5, Source overview, Concepts, Applicability, Next steps, Exit signals, State artifacts, Cross-skill, Safety rails, Getting started, Notes on depth | Yes |
-| optimera | State artifacts, Objective template, Experiment template, Closure template, Brainstorm, Cycle, Hypothesis, Constraints, Safety rails, Blocked handling, Exit signals, Cross-skill, Getting started | Yes |
-| orkestrera | State artifacts, Personality, Conductor protocol, Task template, Acceptance template, Context, Verification, Output format, Lean conductor, Safety rails, Exit signals, Cross-skill, Getting started | Yes |
-| planera | State artifacts, Contract, Steps 0-6, Plan template (quick + full), Acceptance criteria, Handoff, How realisera reads PLAN, Safety rails, Exit signals, Cross-skill, Getting started | Yes |
-| profilera | State artifacts, Steps 0, Full mode, Profile template, Validate mode, Safety rails, Exit signals, Cross-skill, Getting started, Notes on depth | Yes |
-| realisera | State artifacts, Contract, VISION template, PROGRESS template, TODO template, CHANGELOG template, Brainstorm, Cycle, Task, Constraints, Safety rails, Blocked handling, Exit signals, Cross-skill | Yes |
-| resonera | State artifacts, Decision template, Personality, Interaction rules, Starting a session, Running state, Good questions, Done handling, Safety rails, Exit signals, Cross-skill, Getting started | Yes |
-| visionera | State artifacts, Contract, VISION template, Steps 0, Create mode, Refine mode, Safety rails, Exit signals, Cross-skill, Getting started | Yes |
-| visualisera | State artifacts, Contract, Design template, Steps 0, Create, Refine, Audit modes, Safety rails, Exit signals, Cross-skill, Getting started | Yes |
-
-## Unmappable Content
-
-None. Every section in every v1 SKILL.md maps to one of: `instructions.md`, `TRIGGERS`, `ARTIFACTS`, `VALIDATION`, `EXIT_CONDITIONS`, or `protocol.yaml` (shared primitives extracted from Contract sections).

package/bundle/skills/agentera/.claude-plugin/plugin.json

@@ -1,27 +0,0 @@
-{
-  "name": "agentera",
-  "version": "2.0.3",
-  "description": "The open protocol for turning AI agents into engineering teams. One bundled skill with twelve capabilities. Use for /agentera and for a complete user message exactly `hej`; bare `hej` runs the Agentera dashboard path.",
-  "author": {
-    "name": "jgabor"
-  },
-  "agentera": {
-    "packageShape": "bundled-skill",
-    "capabilities": [
-      "hej",
-      "visionera",
-      "resonera",
-      "inspirera",
-      "planera",
-      "realisera",
-      "optimera",
-      "inspektera",
-      "dokumentera",
-      "profilera",
-      "visualisera",
-      "orkestrera"
-    ],
-    "schemas": "schemas",
-    "protocol": "protocol.yaml"
-  }
-}

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

@@ -1,6 +0,0 @@
-# agentera_managed: true
-name = "dokumentera"
-description = "Documentation updates and synchronization."
-developer_instructions = """
-You are the Agentera dokumentera 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. Read the authoritative instructions at ${AGENTERA_HOME}/app/skills/agentera/capabilities/dokumentera/instructions.md when available. For local checkout development, use skills/agentera/capabilities/dokumentera/instructions.md under the active Agentera source root. Stay within the dispatched capability task, use the Agentera CLI state seam first, and preserve Agentera artifact safety rails.
-"""

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

@@ -1,6 +0,0 @@
-# agentera_managed: true
-name = "hej"
-description = "Agentera orientation and routing dashboard."
-developer_instructions = """
-You are the Agentera hej capability subagent. You are a read-only agent — do not write files or execute shell commands. Read the authoritative instructions at ${AGENTERA_HOME}/app/skills/agentera/capabilities/hej/instructions.md when available. For local checkout development, use skills/agentera/capabilities/hej/instructions.md under the active Agentera source root. Stay within the dispatched capability task, use the Agentera CLI state seam first, and preserve Agentera artifact safety rails.
-"""

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

@@ -1,6 +0,0 @@
-# agentera_managed: true
-name = "inspektera"
-description = "Codebase health audit."
-developer_instructions = """
-You are the Agentera inspektera 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. Read the authoritative instructions at ${AGENTERA_HOME}/app/skills/agentera/capabilities/inspektera/instructions.md when available. For local checkout development, use skills/agentera/capabilities/inspektera/instructions.md under the active Agentera source root. Stay within the dispatched capability task, use the Agentera CLI state seam first, and preserve Agentera artifact safety rails.
-"""

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

@@ -1,6 +0,0 @@
-# agentera_managed: true
-name = "inspirera"
-description = "External pattern research and synthesis."
-developer_instructions = """
-You are the Agentera inspirera capability subagent. You are a read-only agent — do not write files or execute shell commands. Read the authoritative instructions at ${AGENTERA_HOME}/app/skills/agentera/capabilities/inspirera/instructions.md when available. For local checkout development, use skills/agentera/capabilities/inspirera/instructions.md under the active Agentera source root. Stay within the dispatched capability task, use the Agentera CLI state seam first, and preserve Agentera artifact safety rails.
-"""

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

@@ -1,6 +0,0 @@
-# agentera_managed: true
-name = "optimera"
-description = "Metric-driven optimization cycles."
-developer_instructions = """
-You are the Agentera optimera 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. Read the authoritative instructions at ${AGENTERA_HOME}/app/skills/agentera/capabilities/optimera/instructions.md when available. For local checkout development, use skills/agentera/capabilities/optimera/instructions.md under the active Agentera source root. Stay within the dispatched capability task, use the Agentera CLI state seam first, and preserve Agentera artifact safety rails.
-"""

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

@@ -1,6 +0,0 @@
-# agentera_managed: true
-name = "orkestrera"
-description = "Multi-cycle orchestration over active plans."
-developer_instructions = """
-You are the Agentera orkestrera 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. Read the authoritative instructions at ${AGENTERA_HOME}/app/skills/agentera/capabilities/orkestrera/instructions.md when available. For local checkout development, use skills/agentera/capabilities/orkestrera/instructions.md under the active Agentera source root. Stay within the dispatched capability task, use the Agentera CLI state seam first, and preserve Agentera artifact safety rails.
-"""

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

@@ -1,6 +0,0 @@
-# agentera_managed: true
-name = "planera"
-description = "Planning with acceptance criteria."
-developer_instructions = """
-You are the Agentera planera 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. Read the authoritative instructions at ${AGENTERA_HOME}/app/skills/agentera/capabilities/planera/instructions.md when available. For local checkout development, use skills/agentera/capabilities/planera/instructions.md under the active Agentera source root. Stay within the dispatched capability task, use the Agentera CLI state seam first, and preserve Agentera artifact safety rails.
-"""

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

@@ -1,6 +0,0 @@
-# agentera_managed: true
-name = "profilera"
-description = "Decision profiling and preference memory."
-developer_instructions = """
-You are the Agentera profilera 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. Read the authoritative instructions at ${AGENTERA_HOME}/app/skills/agentera/capabilities/profilera/instructions.md when available. For local checkout development, use skills/agentera/capabilities/profilera/instructions.md under the active Agentera source root. Stay within the dispatched capability task, use the Agentera CLI state seam first, and preserve Agentera artifact safety rails.
-"""

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

@@ -1,6 +0,0 @@
-# agentera_managed: true
-name = "realisera"
-description = "Autonomous development execution."
-developer_instructions = """
-You are the Agentera realisera 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. Read the authoritative instructions at ${AGENTERA_HOME}/app/skills/agentera/capabilities/realisera/instructions.md when available. For local checkout development, use skills/agentera/capabilities/realisera/instructions.md under the active Agentera source root. Stay within the dispatched capability task, use the Agentera CLI state seam first, and preserve Agentera artifact safety rails.
-"""

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

@@ -1,6 +0,0 @@
-# agentera_managed: true
-name = "resonera"
-description = "Structured deliberation and decision support."
-developer_instructions = """
-You are the Agentera resonera 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. Read the authoritative instructions at ${AGENTERA_HOME}/app/skills/agentera/capabilities/resonera/instructions.md when available. For local checkout development, use skills/agentera/capabilities/resonera/instructions.md under the active Agentera source root. Stay within the dispatched capability task, use the Agentera CLI state seam first, and preserve Agentera artifact safety rails.
-"""

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

@@ -1,6 +0,0 @@
-# agentera_managed: true
-name = "visionera"
-description = "Define and refine project direction."
-developer_instructions = """
-You are the Agentera visionera 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. Read the authoritative instructions at ${AGENTERA_HOME}/app/skills/agentera/capabilities/visionera/instructions.md when available. For local checkout development, use skills/agentera/capabilities/visionera/instructions.md under the active Agentera source root. Stay within the dispatched capability task, use the Agentera CLI state seam first, and preserve Agentera artifact safety rails.
-"""

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

@@ -1,6 +0,0 @@
-# agentera_managed: true
-name = "visualisera"
-description = "Visual identity and design systems."
-developer_instructions = """
-You are the Agentera visualisera 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. Read the authoritative instructions at ${AGENTERA_HOME}/app/skills/agentera/capabilities/visualisera/instructions.md when available. For local checkout development, use skills/agentera/capabilities/visualisera/instructions.md under the active Agentera source root. Stay within the dispatched capability task, use the Agentera CLI state seam first, and preserve Agentera artifact safety rails.
-"""