@tea-agent/loop-agent 0.41.1 → 0.42.0-next.10

package/skills/frontend-implementation/references/code-standards.md

@@ -1,33 +0,0 @@
-# Frontend Code Standards
-
-Discover rules from task constraints, `design-spec.md` source order, config, code,
-tests, manifests, and generated types. Regardless of knowledge-base results,
-applicable `openspec/schemas/`, `openspec/project-specs/`, and `ai_workspace/` rules are normative.
-Preferences are not rules, and docs do not override installed APIs without an
-explicit compatibility decision.
-
-## Discover And Cite
-
-- Find routing and server/client boundaries; state, forms, data/cache, and errors;
-  API/mock/UI/schema/test locations and naming; supported tests; dependency rules.
-
-Cite representative files/config for each convention. Describe conflicts instead of
-silently selecting one.
-
-## Plan And Implement
-
-- Map criteria to code and checks. Define placement, state ownership, request
-  lifecycle, validation/failures, API compatibility, mocks, and fixtures.
-- Trace fixtures to API evidence; label gaps. Prefer native mocks, then browser
-  interception for existing e2e, then a reversible request adapter/DI preview seam.
-- Real API stays default; mock activation is explicit, local/test-only,
-  non-production, and removable.
-- Reuse helpers/public APIs and preserve out-of-contract behavior. Keep rendering,
-  transitions, validation, and side effects testable; cover lifecycle races/bounds
-  when relevant. Update supported tests; stay in `writeSet`.
-
-## Prohibited
-
-- Do not relax checks, add unapproved dependencies, comment real requests, hardcode
-  fixtures in production UI, import test mocks into production, store fixture
-  secrets, equate mock evidence with real integration, or report unrun checks as verified.

package/skills/frontend-implementation/references/design-spec.md

@@ -1,56 +0,0 @@
-# Frontend Design And Component Specification
-
-## Required Source Sequence
-
-Knowledge base, OpenSpec, and `ai_workspace/` are parallel specification sources:
-
-1. Attempt the configured component/design knowledge-base query first when a
-   connector is available.
-2. Regardless of knowledge-base success/failure/timeout/no-match, also
-   recursively search `openspec/schemas/`, `openspec/project-specs/`, and
-   `ai_workspace/` for index files and relevant content.
-3. Treat relevant matches from both sources as the current project's
-   specification for this run.
-4. Only then use component source, tokens, stories, tests, and pages as
-   non-normative repository fallback.
-
-Never skip local OpenSpec or `ai_workspace/` for neighboring-code conventions,
-even when a knowledge-base query returned results. Report source conflicts instead
-of combining them. Explicit task requirements remain the contract.
-
-Connector format is TODO; attempt only an available connector, otherwise record
-`not-configured` and run the openspec fallback (never invent a connection).
-
-## openspec Fallback Procedure
-
-- Inspect `<repoRoot>/openspec/schemas/`, `<repoRoot>/openspec/project-specs/`,
-  and `<repoRoot>/ai_workspace/` when present; enumerate supported files recursively.
-- Read indexes first, then search names/content using task, route, component,
-  interaction, theme, token, and state terms.
-- Read matches in context; a filename-only hit is not a rule.
-- Record search terms, inspected/matched paths, headings or tight line ranges,
-  applied rules, and conflicts.
-- If both directories or relevant rules are absent, record that before using
-  repository fallback.
-
-## Retrieval Evidence
-
-Record source as `knowledge-base`, `openspec fallback`, `repository fallback`, or
-`unavailable`. Knowledge-base evidence includes query, source ID/version/time, rules,
-and conflicts. `openspec fallback` includes terms, paths/headings/lines, rules, and conflicts.
-
-## Rules To Retrieve Or Discover
-
-- Components, variants, props, composition, accessibility, deprecations, placement, forms, overlays, navigation, and state patterns.
-- Tokens, typography, color, layout, breakpoints, motion, focus/keyboard/contrast, exceptions, design debt, and forbidden patterns.
-
-## Gate Expectations
-
-- Reuse confirmed primitives unless a new pattern is authorized.
-- Define applicable states and responsive behavior before implementation.
-- Cite knowledge-base or openspec spec evidence for component/token choices;
-  label weaker repo fallback.
-- Make deviations and unresolved gaps explicit.
-- Contract `uiComponentChoices[]` per UI purpose: `specified` needs
-  `specReference {path,section,line}`; `new` needs null ref + rationale; never
-  silently replace a spec-defined component.

package/skills/frontend-implementation/references/node-contracts.md

@@ -1,31 +0,0 @@
-# Frontend Node Contracts
-
-Pre-write nodes are read-only. Preserve IDs, labels, commands, language, required headings.
-
-## Core nodes
-
-- **`frontend-contract-pi`**: `Scope`, `Non-goals`, `Acceptance Criteria`, `UI States`, `Target Runtime Environment`, `Risks`, `Verification Expectations`; no guessed requirements.
-- **`frontend-scout-pi`**: routes, components, tokens, data/API/Mock, scripts, tests, assets; fact vs inference vs gap. Search+read `openspec/schemas/`, `openspec/project-specs/`, `ai_workspace/` first. Output stack, styling, conventions, state/data, test entry points, reuse, risks.
-- **`frontend-plan-pi` + conditional design loop**: AC → observable `expectedOutcome`; interactions → `trigger`+`expectedBehavior`; include steps, in-bound files, UI states, reuse, deps, Mock/API, frozen verify entrypoints and integration gaps. DAG freezes a protected skeleton (`schemaVersion`, `sourceBinding`, `riskLevel`, `targets.files`, `mockApi.productionDefaultOff`). Model returns a **JSON-only** editable RFC 7386 patch (`frontend-implementation-contract-plan-patch-v1`) plus one `openspec-citations` block. Runtime compiles canonical `frontend-implementation-contract-v1` and archives raw/extracted/normalized/validation candidates; unresolved optional symbols are dropped and audited. No plan prose; gate renders plan.md. IDs+paths ≠ behavior semantics. Applicable UI states need behavior/implementation/verification; non-applicable states need reasons. Active Mock needs frozen commands; `auto` without confirmed capability/command → `not-needed`; `required` without command → generation-time blocked. Only `request-revision` runs revision+final review; small-risk gets one review.
-  - `uiComponentChoices[]` (optional): `{purpose, component, decision, specReference, rationale}`; `specified` needs `specReference{path,section,line}`; `new` needs null ref+rationale.
-- **`frontend-prewrite-gate-shell`**: sole write authorization. Resolve effective plan (revised if revision ran, else original) + review; require exact pass; retain every REQ/BR/AC id; enforce Mock policy; validate schema/source binding+writeSet containment; materialize `contracts/frontend-implementation-contract.json` from the **single** fenced contract block (multiple candidates fail closed `invalid-output`). Fallback only when conditional primary absent; malformed primary fails closed. Generation-time blocked Mock yields one blocking shell node, no writer.
-  - `verificationTarget.commandLabel` must be a **frozen command label** from `verifyEvidence.commandLabels`; others fail closed (`invalid-output`). Empty frozen set (no `run.json`) skips check.
-  - `mockApi.strategy !== "not-needed"` fails closed when `mockCommandLabels` empty (`no authorized Mock verification commands`).
-  - OpenSpec policy: `task.json.frontendOpenspec.policy` (default `cited`); candidates = `requiredReadPaths` ∪ task-source citations; effective plan must append one fenced `openspec-citations` block (one JSON `{"path","section","line"}` per line). Candidates non-empty but block missing/unparseable → `openspec-citation-block-unparseable`; candidate not cited → `openspec-not-cited`; cited path without read event → `openspec-citation-not-read` (anti-fabrication). Empty candidates skip enforcement. `scan-strict` keeps full-read semantics (`openspec-not-read`); both modes keep `candidate-missing-drift`.
-  - Component conformance: missing `uiComponentChoices` (frozen bucket non-empty + UI-visible work) → `component-choices-missing`; bad/uncited `specReference.path` → `component-spec-reference-invalid` / `component-spec-not-cited`.
-  - revisionPatch mode: revision output is an RFC 7386 merge-patch delta applied on the original canonical contract node (`planFallbackFromNodeIds[0]`); protected skeleton paths remain immutable. Legacy DAGs keep full-contract semantics. Size guard: canonical serialization >64KB → `retryable-invalid` + `contract-too-large`.
-- **`frontend-implement-pi`**: sole regular exclusive writer; uses `frontend-bounded-implement` (not this skill). Stay in `writeSet`; real requests default-on. Atomic handler/intercept/adapter with tests. Stop on forbidden paths/guesses. First line `IMPLEMENTATION_OUTCOME: changed|already-satisfied|blocked`; runtime checks against attributed diff. Optional mock-verify when frozen; static+behavior always; behavior must prove page consumption. `not-needed` keeps real integration pending unless real backend has fresh evidence.
-
-## Contract / trace / stages (M1–M2)
-
-- `frontend-verify-assess-shell` runs Mock/static/behavior groups, binds `verificationTargets` to command labels+evidence, writes `frontend-verification-trace.json`+`frontend-repair-assessment.json`; browser/visual stay `not-run`.
-- `frontend-review-context-shell` captures real diff; combines contract, effective trace, repair assessment, diff into `contracts/frontend-review-context.json`.
-- Implement stages: (1) contract confirm (2) tests sync (3) component/UI (4) API/Mock (5) frozen checks (6) diff cleanup. Summary: Contract Ref, Changed Files, Requirements, UI States, Tests, Verification Attempts, Deviations, Residual Risks.
-
-## Repair (M3)
-
-Only `eligible=true` runs `frontend-repair-pi` (same writeSet; no re-spec; max 1 attempt) + `frontend-reverify-shell`. No-failure skips both. Non-repairable contract/path/dependency/credential/deploy/spec-unclear failures fail closed.
-
-## Risk & capability (M4–M6)
-
-Deterministic risk, no model; high-risk beats small; supervised never small. Standard/high-risk: 15 top-level nodes; small: 13 (omits revision + final review). Capability seed injects adapters; openspec specs and task sources outrank adapter guidance. A11y: static/component tools only when present; Browser a11y always not-run.