@tea-agent/loop-agent 0.41.1-beta.0 → 0.42.0-next.1

package/docs/templates/frontend-implementation-dag.json

@@ -1,89 +0,0 @@
-{
-  "$schema": "./agent-dag.schema.json",
-  "version": 2,
-  "title": "Frontend implementation independent DAG template",
-  "objective": "Replace with the concrete, bounded frontend implementation objective for this DAG run.",
-  "successCriteria": [
-    "The contract covers every required user-visible behavior, state, and interaction.",
-    "The implementation is admitted only after a concrete, narrow writeSet is reviewed.",
-    "Static and behavior verification are recorded before final review.",
-    "The final closeout distinguishes passed, not-run, and residual-risk evidence."
-  ],
-  "globalConstraints": [
-    "This is a self-contained static template: do not generate, import, or merge a DAG from a runtime builder before execution.",
-    "Replace every REPLACE/WITH/... placeholder with concrete repository paths or deterministic commands before execution.",
-    "Do not commit runtime traces under .harness/dag-runs/.",
-    "Every node must explicitly declare its executor; defaults.executor is schema-only and not a runtime fallback.",
-    "Only frontend-implement-pi may write project files, and only inside its concrete writeSet.",
-    "Read-only nodes must not write root artifacts/**; root artifacts/ is not a per-node scratchpad.",
-    "Do not infer missing behavior, states, interactions, design decisions, or verification commands. Stop for an explicit task-contract revision instead.",
-    "Do not add dependencies unless they are already declared by the project contract."
-  ],
-  "defaults": {"executor":"pi","contextProfile":"slim","skills":["ai-engineering-context"],"writePolicy":"read-only"},
-  "skillsByRole": {
-    "planner":["loop-agent"], "scout":["ai-engineering-context"], "implementer":["verification-before-completion"], "reviewer":["requesting-code-review"], "verifier":["verification-before-completion","systematic-debugging"], "closeout":["loop-agent","verification-before-completion"]
-  },
-  "executorModels": {"pi":{"LOW":"gpt-5.3-codex-spark","MED":"gpt-5.5","HIGH":"gpt-5.5"}},
-  "tasks": [
-    {
-      "id":"frontend-contract-pi", "depends_on":[], "complexity":"MED", "executor":"pi", "role":"planner", "writePolicy":"read-only", "allowedPaths":["**"], "forbiddenPaths":[".harness/**","artifacts/**"],
-      "outputContract":"Plain Markdown frontend contract: required behavior, states, interactions, non-goals, concrete verification expectations, and unresolved gaps; no file writes.",
-      "subtask_prompt":"Read the task inputs. Produce a concise frontend contract that maps each required behavior, UI state, and interaction to observable outcomes. Identify missing or conflicting requirements as blockers; do not infer them and do not edit files."
-    },
-    {
-      "id":"frontend-scout-pi", "depends_on":["frontend-contract-pi"], "complexity":"LOW", "executor":"pi", "role":"scout", "writePolicy":"read-only", "allowedPaths":["REPLACE/WITH/FRONTEND/SOURCE/PATH/**","REPLACE/WITH/FRONTEND/TEST/PATH/**"], "forbiddenPaths":[".harness/**","artifacts/**"],
-      "outputContract":"Plain Markdown source and verification reconnaissance: relevant routes, components, styles, state patterns, focused tests, and risks; no file writes.",
-      "subtask_prompt":"Inspect only the declared frontend source and test paths. Report reusable component, styling, accessibility, state-management, and verification patterns that satisfy the contract. Do not edit files or broaden the allowed paths."
-    },
-    {
-      "id":"frontend-plan-pi", "depends_on":["frontend-scout-pi"], "complexity":"MED", "executor":"pi", "role":"planner", "writePolicy":"read-only", "allowedPaths":["REPLACE/WITH/FRONTEND/SOURCE/PATH/**","REPLACE/WITH/FRONTEND/TEST/PATH/**"], "forbiddenPaths":[".harness/**","artifacts/**"],
-      "outputContract":"Plain Markdown implementation plan: ordered changes, concrete target files, behavior/state/interaction coverage, and focused verification mapping; no file writes.",
-      "subtask_prompt":"Turn the contract and reconnaissance into a minimal implementation plan. Every target file and verification step must be concrete. Preserve existing design and accessibility conventions. If any behavior lacks a verifiable target, report it as blocked instead of guessing."
-    },
-    {
-      "id":"frontend-design-policy-shell", "depends_on":["frontend-plan-pi"], "complexity":"LOW", "executor":"shell", "role":"verifier", "writePolicy":"read-only", "allowedPaths":["REPLACE/WITH/FRONTEND/SOURCE/PATH/**","REPLACE/WITH/FRONTEND/TEST/PATH/**"], "forbiddenPaths":[".harness/**","artifacts/**"],
-      "outputContract":"Archived deterministic design-policy result proving the plan uses declared dependencies, concrete requirements, and approved design evidence; no worktree writes.",
-      "subtask_prompt":"Run the project-specific deterministic design-policy check selected for this task. It must reject missing requirement coverage, unauthorized dependencies, and unresolved design conflicts.",
-      "shell":{"commands":["REPLACE/WITH/DESIGN-POLICY/COMMAND"],"cwd":".","timeoutMs":300000}
-    },
-    {
-      "id":"frontend-design-review-pi", "depends_on":["frontend-design-policy-shell"], "complexity":"MED", "executor":"pi", "role":"reviewer", "writePolicy":"read-only", "allowedPaths":["REPLACE/WITH/FRONTEND/SOURCE/PATH/**","REPLACE/WITH/FRONTEND/TEST/PATH/**"], "forbiddenPaths":[".harness/**","artifacts/**"],
-      "outputContract":"Plain Markdown design review: approved plan or explicit blocking findings for behavior, state, interaction, design-system, and accessibility coverage; no file writes.",
-      "subtask_prompt":"Review the approved plan against the frontend contract and design-policy result. Reject missing visible states, interaction behavior, accessibility obligations, or unsupported design claims. Do not edit files."
-    },
-    {
-      "id":"frontend-writer-admission-shell", "depends_on":["frontend-design-review-pi"], "complexity":"LOW", "executor":"shell", "role":"verifier", "writePolicy":"read-only", "allowedPaths":["REPLACE/WITH/FRONTEND/TARGET/PATH/**"], "forbiddenPaths":[".harness/**","artifacts/**"],
-      "outputContract":"Archived deterministic writer-admission result with a concrete, narrow writeSet and pre-write baseline; no worktree writes.",
-      "subtask_prompt":"Run the project-specific writer-admission check. It must derive and record a concrete writeSet from the approved plan, reject broad paths and scope drift, and capture the pre-write baseline before authorizing the writer.",
-      "shell":{"commands":["REPLACE/WITH/WRITER-ADMISSION/COMMAND"],"cwd":".","timeoutMs":300000}
-    },
-    {
-      "id":"frontend-implement-pi", "depends_on":["frontend-writer-admission-shell"], "complexity":"HIGH", "executor":"pi", "role":"implementer", "toolProfile":"write", "writePolicy":"exclusive", "writeSet":["REPLACE/WITH/FRONTEND/TARGET/PATH/**"], "allowedPaths":["REPLACE/WITH/FRONTEND/TARGET/PATH/**"], "forbiddenPaths":[".harness/**","artifacts/**"],
-      "outputContract":"Implementation summary with changed files, contract coverage, focused checks run, and residual risks.",
-      "subtask_prompt":"Implement only the admitted frontend changes. Preserve established component, styling, accessibility, and state-management conventions. Cover every approved behavior, state, and interaction, then report changed files and focused verification. Do not broaden writeSet or add undeclared dependencies."
-    },
-    {
-      "id":"frontend-verify-shell", "depends_on":["frontend-implement-pi"], "complexity":"LOW", "executor":"shell", "role":"verifier", "writePolicy":"read-only", "allowedPaths":["REPLACE/WITH/FRONTEND/TARGET/PATH/**"], "forbiddenPaths":[".harness/**","artifacts/**"],
-      "outputContract":"Archived static and behavior verification output with command exit codes; no worktree writes.",
-      "subtask_prompt":"Run the contract-selected deterministic static and behavior verification commands. Record all exit codes. A failed required command is terminal for this DAG run; do not silently substitute a different command.",
-      "shell":{"preset":"loop-agent-standard-verify","cwd":".","timeoutMs":300000}
-    },
-    {
-      "id":"frontend-review-context-shell", "depends_on":["frontend-verify-shell"], "complexity":"LOW", "executor":"shell", "role":"verifier", "writePolicy":"read-only", "allowedPaths":["REPLACE/WITH/FRONTEND/TARGET/PATH/**"], "forbiddenPaths":[".harness/**","artifacts/**"],
-      "outputContract":"Archived deterministic final-review context: admitted writeSet, cumulative diff, and required verification evidence; no worktree writes.",
-      "subtask_prompt":"Run the project-specific review-context collector. It must bind the admitted writeSet, actual cumulative diff, and required verification results so final review cannot rely on summaries alone.",
-      "shell":{"commands":["REPLACE/WITH/REVIEW-CONTEXT/COMMAND"],"cwd":".","timeoutMs":300000}
-    },
-    {
-      "id":"frontend-review-pi", "depends_on":["frontend-review-context-shell"], "complexity":"MED", "executor":"pi", "role":"reviewer", "writePolicy":"read-only", "allowedPaths":["REPLACE/WITH/FRONTEND/TARGET/PATH/**"], "forbiddenPaths":[".harness/**","artifacts/**"],
-      "outputContract":"Plain Markdown final review: approved result or explicit findings for contract coverage, regression risk, accessibility, and verification gaps; no file writes.",
-      "subtask_prompt":"Review the actual diff and archived verification evidence against the frontend contract. Do not treat missing, weak, mock-only, or not-run evidence as passed. Report explicit residual risks; do not edit files."
-    },
-    {
-      "id":"frontend-closeout-shell", "depends_on":["frontend-review-pi"], "complexity":"LOW", "executor":"shell", "role":"closeout", "writePolicy":"read-only", "allowedPaths":["REPLACE/WITH/FRONTEND/TARGET/PATH/**"], "forbiddenPaths":[".harness/**","artifacts/**"],
-      "outputContract":"Archived deterministic closeout summarizing contract coverage, verification status, review findings, evidence gaps, and residual risks; no worktree writes.",
-      "subtask_prompt":"Run the project-specific deterministic closeout renderer. Preserve evidence status exactly: passed, failed, not-run, mock-backed, and baseline debt must never be promoted to a stronger result.",
-      "shell":{"commands":["REPLACE/WITH/CLOSEOUT/COMMAND"],"cwd":".","timeoutMs":300000}
-    }
-  ]
-}

package/docs/templates/spec-registry.schema.json

@@ -1,45 +0,0 @@
-{
-  "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "https://loop-agent.local/schemas/spec-registry.schema.json",
-  "title": "Frontend specification registry",
-  "type": "object",
-  "additionalProperties": false,
-  "required": ["version", "roots"],
-  "properties": {
-    "version": { "const": 1 },
-    "roots": {
-      "type": "array",
-      "maxItems": 32,
-      "items": {
-        "type": "object",
-        "additionalProperties": false,
-        "required": ["path"],
-        "properties": {
-          "path": {
-            "type": "string",
-            "minLength": 1,
-            "pattern": "^(?!/)(?!.*//)(?!.*\\\\)(?!.*(?:^|/)\\.{1,2}(?:/|$)).+$"
-          },
-          "scope": {
-            "type": "array",
-            "items": { "type": "string", "minLength": 1 },
-            "uniqueItems": true
-          },
-          "mode": { "enum": ["normative", "advisory"] },
-          "description": { "type": "string" }
-        }
-      }
-    },
-    "discovery": {
-      "type": "object",
-      "additionalProperties": false,
-      "properties": {
-        "enabled": { "type": "boolean", "default": true },
-        "maxDepth": { "type": "integer", "minimum": 0, "maximum": 8, "default": 3 },
-        "maxFiles": { "type": "integer", "minimum": 1, "maximum": 200, "default": 100 },
-        "maxBytes": { "type": "integer", "minimum": 1, "maximum": 10485760, "default": 1048576 },
-        "timeoutMs": { "type": "integer", "minimum": 1, "maximum": 10000, "default": 2000 }
-      }
-    }
-  }
-}

package/skills/frontend-bounded-implement/references/code-standards.md

@@ -1,19 +0,0 @@
-# Bounded Frontend Code Standards
-
-Apply the canonical contract and the conventions visible in target files and their
-direct local dependencies. Do not reopen task sources, OpenSpec, `ai_workspace`, or
-unrelated repository areas to discover new rules or redesign approved decisions.
-
-- Work test-first when behavior changes and preserve unrelated behavior.
-- Reuse existing public helpers, APIs, components, tokens, schemas, and test
-  patterns that are directly available from the bounded target surface.
-- Keep rendering, transitions, validation, request lifecycle, errors, and side
-  effects testable; cover relevant races and boundaries.
-- Keep real API behavior enabled by default. Mock activation must follow the
-  approved strategy, remain explicit and dev/test-only, and never import test mocks
-  into production code.
-- Trace fixtures to the approved API/schema evidence and never store secrets.
-- Do not add unapproved dependencies, relax lint/type/test/build configuration,
-  add `.skip`/`.only`, comment out real requests, or write outside `writeSet`.
-- Run only frozen focused checks and report their real status. Downstream shell
-  verification remains authoritative.

package/skills/frontend-contract/SKILL.md

@@ -1,23 +0,0 @@
----
-name: frontend-contract
-description: Use only for the read-only frontend requirement contract node.
-references:
-  - path: references/contract-protocol.md
-    required: true
-    maxChars: 4200
----
-
-# Frontend Contract
-
-Use task sources, explicit references, constraints, and the frozen source-fidelity
-ledger. Preserve canonical requirement IDs, source fragments, commands, paths, and
-language. Do not inspect implementation files or choose components, routes, Mock
-mechanisms, dependencies, or target code as requirement facts.
-
-Submit confirmed facts incrementally with the contract `record_*` tools and finish
-with exactly one `finalize_contract`. Start recording as soon as a requirement or
-constraint is confirmed; do not accumulate the whole contract in one response.
-
-Missing product semantics may be explicit assumptions only when they do not change
-observable behavior. Otherwise record a blocking question or a split proposal.
-This node is read-only.

package/skills/frontend-contract/references/contract-protocol.md

@@ -1,34 +0,0 @@
-# Frontend Contract Protocol
-
-## Requirement fidelity
-
-- Use the frozen canonical requirement ID for every requirement. Never invent a
-  replacement REQ/BR/AC ID.
-- Bind every requirement to exactly the source fragment IDs supplied by the
-  source-fidelity ledger. Do not infer fragment IDs from prose.
-- Record observable outcomes, applicable UI states, runtime/environment constraints,
-  non-goals, risks, and verification expectations without choosing implementation.
-- Classify each requirement as `explicit`, `repository-resolvable`, `assumption`, or
-  `blocking`. Blocking facts name their owner and evidence.
-
-## Evidence and handoff
-
-- Register static, behavior, Mock, and real-integration evidence expectations as
-  required, optional, or not-applicable. The classification follows the source and
-  risk; it is not selected for model convenience.
-- Register a non-blocking frontend-test handoff for UI-visible or interactive work.
-- Preserve exact command labels and referenced paths. Do not invent evidence,
-  connector results, APIs, or verification commands.
-
-## OpenSpec selection
-
-When the frozen task exposes OpenSpec candidates, record only candidates actually
-used by the contract as `required` or `relevant`. Explicit required paths and task
-source citations remain required. Unmentioned candidates are irrelevant; do not
-enumerate or downgrade them.
-
-## Terminal
-
-Commit facts in small batches and call `finalize_contract` exactly once with
-`ready`, `ready-with-assumptions`, or `blocked`. If the task is too large for one
-bounded writer, record a split proposal instead of broadening the contract.

package/skills/frontend-plan/SKILL.md

@@ -1,26 +0,0 @@
----
-name: frontend-plan
-description: Use only for the tool-only frontend decision planning node.
-references:
-  - path: references/decision-contract.md
-    required: true
-    maxChars: 5200
-  - path: references/design-decisions.md
-    required: true
-    maxChars: 3400
----
-
-# Frontend Plan
-
-Plan only the delta between frozen Contract facts and the Scout target surface.
-Do not reread task sources, Contract/Scout prose, or target files, and do not repeat
-requirements or repository discovery.
-
-Commit the smallest necessary typed decisions through the plan `record_*` tools:
-requirement coverage, component/styling choices, applicable states and interactions,
-data/Mock strategy, deviations, and dependency policy. Process a bounded requirement
-slice and record facts immediately rather than reasoning over the whole task first.
-
-The runtime owns protected skeleton fields, path/command validation, materialization,
-and final schema checks. Finish with exactly one `finalize_plan`; return no Markdown
-narrative. Record a genuine evidence gap when frozen facts are insufficient.

package/skills/frontend-plan/references/decision-contract.md

@@ -1,37 +0,0 @@
-# Frontend Plan Decision Contract
-
-## Requirement-local decisions
-
-- Cover each frozen requirement exactly once and map it to Scout-confirmed
-  implementation paths and verification target IDs.
-- Record observable state and interaction behavior, including trigger and expected
-  behavior. IDs and paths alone are not behavioral coverage.
-- One behavior target may cover multiple related requirements when one observable
-  test behavior proves them together.
-- Every non-static verification target `id` is the stable machine trace token and
-  must later appear in a real `describe` / `it` / `test` title. There is no free-form
-  `symbol` field.
-- Static targets are for project-wide commands and are traced by file and command
-  only.
-
-## Global decisions
-
-Keep route/component placement, Mock/data strategy, and dependency/deviation policy
-as explicit global decisions rather than duplicating them across each requirement.
-Use only frozen command labels and Scout-confirmed paths.
-
-For Mock/API, keep the real request path enabled by default. Select only a strategy
-allowed by the frozen task capability. Active Mock requires deterministic Mock-backed
-verification and production-default-off activation. `not-needed` requires positive
-real/no-remote evidence or records a real-integration gap.
-
-Add dependencies only when authorized. Record unsupported dependency, path, API,
-design, or verification needs as blocking evidence gaps; never invent a command or
-widen the write set.
-
-## Runtime-owned fields and terminal
-
-The runtime owns `schemaVersion`, `sourceBinding`, risk, canonical target files,
-aliases, command allowlisting, path containment, and final validation. Submit only
-editable decision facts, then call `finalize_plan` exactly once. The deterministic
-design policy materializes the canonical implementation contract.

package/skills/frontend-plan/references/design-decisions.md

@@ -1,17 +0,0 @@
-# Frontend Design Decisions
-
-Use only design evidence already committed by Scout and frozen selections from
-Contract. Do not search specification roots or nearby code from Plan.
-
-- Reuse confirmed components, variants, tokens, helpers, and state patterns unless
-  the task authorizes a new pattern.
-- Record `uiComponentChoices` per UI purpose. `purpose` is the stable coverage key
-  matching an interaction or UI state; behavior remains in the corresponding
-  expected behavior and rationale.
-- `specified` requires an exact bound OpenSpec reference. `reuse-existing` identifies
-  the proven existing component/path. Task-mandated `new` choices bind the frozen
-  source requirement/fragment so the runtime can derive the PRD citation.
-- Define applicable success, loading, empty, error, permission, disabled, boundary,
-  responsive, and accessibility behavior; use not-applicable only with a reason.
-- Record styling strategy, deviations, conflicts, and unresolved gaps explicitly.
-  Never silently replace a spec-defined component or claim unread evidence.

package/skills/frontend-scout/SKILL.md

@@ -1,25 +0,0 @@
----
-name: frontend-scout
-description: Use only for read-only frontend target-surface and design-evidence scouting.
-references:
-  - path: references/scout-evidence.md
-    required: true
-    maxChars: 4200
-  - path: references/design-evidence.md
-    required: true
-    maxChars: 3600
----
-
-# Frontend Scout
-
-Inspect only enough repository evidence to prove the target surface and applicable
-design rules. Separate facts, inferences, and unresolved gaps. Reuse the frozen
-capability context and contract selections before running bounded task-term searches.
-
-Submit findings incrementally through `record_target_surface` and
-`record_design_evidence`. A complete surface names proven entrypoints, routes or
-mounts, implementation paths, test paths, data sources, and any allowed-path
-conflicts. If ownership remains unresolved, commit `completeness=blocked` with the
-specific gaps rather than guessing.
-
-This node is read-only and does not make plan decisions.

package/skills/frontend-scout/references/design-evidence.md

@@ -1,16 +0,0 @@
-# Frontend Design Evidence
-
-Use the generation-frozen component/design capability context and cited candidate
-set. When a connector is available, query the configured knowledge base; regardless
-of its result, inspect relevant frozen OpenSpec or `ai_workspace` candidates. Search
-local specification roots only for unresolved task terms and never recursively read
-all supported files.
-
-Record evidence as `knowledge-base`, `openspec fallback`, `repository fallback`, or
-`unavailable`. Include query/search terms, paths, headings or tight line ranges,
-applied rules, and conflicts. Filename-only and unread search matches are not rules.
-
-Look for components, variants, composition, tokens, layout, responsive behavior,
-accessibility, state patterns, data/Mock conventions, deprecations, exceptions, and
-forbidden patterns. Explicit task requirements remain authoritative; report source
-conflicts instead of merging them silently.

package/skills/frontend-scout/references/scout-evidence.md

@@ -1,23 +0,0 @@
-# Frontend Scout Evidence
-
-## Target surface
-
-Prove the current frontend stack and the files that own the requested behavior:
-
-- entrypoint, route or mount;
-- page/component/style implementation paths;
-- state and data/API/Mock flow;
-- supported scripts and test entrypoints;
-- reusable components, tokens, helpers, fixtures, and assets;
-- paths discovered outside task `allowedPaths`;
-- unresolved ownership or missing evidence.
-
-Use repository-relative POSIX paths. A search hit, lockfile, fixture, or filename is
-not proof by itself. Read the relevant surrounding code or configuration and report
-the exact evidence. Do not recursively inspect unrelated directories.
-
-## Completeness
-
-Commit `complete` only when the target surface is sufficiently proven for Plan to
-reuse without repository discovery. Otherwise commit `blocked` and list every
-unresolved path or ownership question. Do not shift discovery work into Plan.