@fro.bot/systematic 2.7.1 → 2.7.3

package/agents/design/design-implementation-reviewer.md

@@ -1,7 +1,6 @@
 ---
 name: design-implementation-reviewer
 description: "Visually compares live UI implementation against Figma designs and provides detailed feedback on discrepancies. Use after writing or modifying HTML/CSS/React components to verify design fidelity."
-model: inherit
 ---
 
 You are an expert UI/UX implementation reviewer specializing in ensuring pixel-perfect fidelity between Figma designs and live implementations. You have deep expertise in visual design principles, CSS, responsive design, and cross-browser compatibility.

package/agents/design/design-iterator.md

@@ -2,7 +2,6 @@
 name: design-iterator
 description: "Iteratively refines UI design through N screenshot-analyze-improve cycles. Use PROACTIVELY when design changes aren't coming together after 1-2 attempts, or when user requests iterative refinement."
 color: violet
-model: inherit
 ---
 
 You are an expert UI/UX design iterator specializing in systematic, progressive refinement of web components. Your methodology combines visual analysis, competitor research, and incremental improvements to transform ordinary interfaces into polished, professional designs.

package/agents/design/figma-design-sync.md

@@ -1,7 +1,6 @@
 ---
 name: figma-design-sync
 description: "Detects and fixes visual differences between a web implementation and its Figma design. Use iteratively when syncing implementation to match Figma specs."
-model: inherit
 color: purple
 ---
 

package/agents/docs/ankane-readme-writer.md

@@ -2,7 +2,6 @@
 name: ankane-readme-writer
 description: "Creates or updates README files following Ankane-style template for Ruby gems. Use when writing gem documentation with imperative voice, concise prose, and standard section ordering."
 color: cyan
-model: inherit
 ---
 
 You are an expert Ruby gem documentation writer specializing in the Ankane-style README format. You have deep knowledge of Ruby ecosystem conventions and excel at creating clear, concise documentation that follows Andrew Kane's proven template structure.

package/agents/document-review/adversarial-document-reviewer.md

@@ -1,7 +1,6 @@
 ---
 name: adversarial-document-reviewer
 description: "Conditional document-review persona, selected when the document has >5 requirements or implementation units, makes significant architectural decisions, covers high-stakes domains, or proposes new abstractions. Challenges premises, surfaces unstated assumptions, and stress-tests decisions rather than evaluating document quality."
-model: inherit
 tools: Read, Grep, Glob, Bash
 ---
 

package/agents/document-review/coherence-reviewer.md

@@ -1,7 +1,6 @@
 ---
 name: coherence-reviewer
 description: "Reviews planning documents for internal consistency -- contradictions between sections, terminology drift, structural issues, and ambiguity where readers would diverge. Spawned by the document-review skill."
-model: inherit
 tools: Read, Grep, Glob, Bash
 ---
 

package/agents/document-review/design-lens-reviewer.md

@@ -1,7 +1,6 @@
 ---
 name: design-lens-reviewer
 description: "Reviews planning documents for missing design decisions -- information architecture, interaction states, user flows, and AI slop risk. Uses dimensional rating to identify gaps. Spawned by the document-review skill."
-model: inherit
 tools: Read, Grep, Glob, Bash
 ---
 

package/agents/document-review/feasibility-reviewer.md

@@ -1,7 +1,6 @@
 ---
 name: feasibility-reviewer
 description: "Evaluates whether proposed technical approaches in planning documents will survive contact with reality -- architecture conflicts, dependency gaps, migration risks, and implementability. Spawned by the document-review skill."
-model: inherit
 tools: Read, Grep, Glob, Bash
 ---
 

package/agents/document-review/product-lens-reviewer.md

@@ -1,7 +1,6 @@
 ---
 name: product-lens-reviewer
 description: "Reviews planning documents as a senior product leader -- challenges premise claims, assesses strategic consequences (trajectory, identity, adoption, opportunity cost), and surfaces goal-work misalignment. Domain-agnostic: users may be end users, developers, operators, or any audience. Spawned by the document-review skill."
-model: inherit
 tools: Read, Grep, Glob, Bash
 ---
 

package/agents/document-review/scope-guardian-reviewer.md

@@ -1,7 +1,6 @@
 ---
 name: scope-guardian-reviewer
 description: "Reviews planning documents for scope alignment and unjustified complexity -- challenges unnecessary abstractions, premature frameworks, and scope that exceeds stated goals. Spawned by the document-review skill."
-model: inherit
 tools: Read, Grep, Glob, Bash
 ---
 

package/agents/document-review/security-lens-reviewer.md

@@ -1,7 +1,6 @@
 ---
 name: security-lens-reviewer
 description: "Evaluates planning documents for security gaps at the plan level -- auth/authz assumptions, data exposure risks, API surface vulnerabilities, and missing threat model elements. Spawned by the document-review skill."
-model: inherit
 tools: Read, Grep, Glob, Bash
 ---
 

package/agents/research/best-practices-researcher.md

@@ -1,7 +1,6 @@
 ---
 name: best-practices-researcher
 description: "Researches and synthesizes external best practices, documentation, and examples for any technology or framework. Use when you need industry standards, community conventions, or implementation guidance."
-model: inherit
 ---
 
 **Note: The current year is 2026.** Use this when searching for recent documentation and best practices.

package/agents/research/framework-docs-researcher.md

@@ -1,7 +1,6 @@
 ---
 name: framework-docs-researcher
 description: "Gathers comprehensive documentation and best practices for frameworks, libraries, or dependencies. Use when you need official docs, version-specific constraints, or implementation patterns."
-model: inherit
 ---
 
 **Note: The current year is 2026.** Use this when searching for recent documentation and version information.

package/agents/research/git-history-analyzer.md

@@ -1,7 +1,6 @@
 ---
 name: git-history-analyzer
 description: "Performs archaeological analysis of git history to trace code evolution, identify contributors, and understand why code patterns exist. Use when you need historical context for code changes."
-model: inherit
 ---
 
 **Note: The current year is 2026.** Use this when interpreting commit dates and recent changes.

package/agents/research/issue-intelligence-analyst.md

@@ -1,7 +1,6 @@
 ---
 name: issue-intelligence-analyst
 description: "Fetches and analyzes GitHub issues to surface recurring themes, pain patterns, and severity trends. Use when understanding a project's issue landscape, analyzing bug patterns for ideation, or summarizing what users are reporting."
-model: inherit
 ---
 
 **Note: The current year is 2026.** Use this when evaluating issue recency and trends.

package/agents/research/learnings-researcher.md

@@ -1,7 +1,6 @@
 ---
 name: learnings-researcher
 description: "Searches docs/solutions/ for relevant past solutions by frontmatter metadata. Use before implementing features or fixing problems to surface institutional knowledge and prevent repeated mistakes."
-model: inherit
 ---
 
 You are an expert institutional knowledge researcher specializing in efficiently surfacing relevant documented solutions from the team's knowledge base. Your mission is to find and distill applicable learnings before new work begins, preventing repeated mistakes and leveraging proven patterns.

package/agents/research/repo-research-analyst.md

@@ -1,7 +1,6 @@
 ---
 name: repo-research-analyst
 description: "Conducts thorough research on repository structure, documentation, conventions, and implementation patterns. Use when onboarding to a new codebase or understanding project conventions."
-model: inherit
 ---
 
 **Note: The current year is 2026.** Use this when searching for recent documentation and patterns.

package/agents/research/slack-researcher.md

@@ -1,7 +1,6 @@
 ---
 name: slack-researcher
 description: "Searches Slack for organizational context. Use when the user explicitly asks. Requires a Slack MCP server."
-model: inherit
 ---
 **Note: The current year is 2026.** Use this when assessing the recency of Slack discussions.
 

package/agents/review/adversarial-reviewer.md

@@ -1,7 +1,6 @@
 ---
 name: adversarial-reviewer
 description: Conditional code-review persona, selected when the diff is large (>=50 changed lines) or touches high-risk domains like auth, payments, data mutations, or external APIs. Actively constructs failure scenarios to break the implementation rather than checking against known patterns.
-model: inherit
 tools: Read, Grep, Glob, Bash
 color: red
 

package/agents/review/agent-native-reviewer.md

@@ -1,7 +1,6 @@
 ---
 name: agent-native-reviewer
 description: "Reviews code to ensure agent-native parity -- any action a user can take, an agent can also take. Use after adding UI features, agent tools, or system prompts."
-model: inherit
 color: cyan
 tools: Read, Grep, Glob, Bash
 ---

package/agents/review/api-contract-reviewer.md

@@ -1,7 +1,6 @@
 ---
 name: api-contract-reviewer
 description: Conditional code-review persona, selected when the diff touches API routes, request/response types, serialization, versioning, or exported type signatures. Reviews code for breaking contract changes.
-model: inherit
 tools: Read, Grep, Glob, Bash
 color: blue
 mode: subagent

package/agents/review/architecture-strategist.md

@@ -1,7 +1,6 @@
 ---
 name: architecture-strategist
 description: "Analyzes code changes from an architectural perspective for pattern compliance and design integrity. Use when reviewing PRs, adding services, or evaluating structural refactors."
-model: inherit
 tools: Read, Grep, Glob, Bash
 ---
 

package/agents/review/cli-agent-readiness-reviewer.md

@@ -1,7 +1,6 @@
 ---
 name: cli-agent-readiness-reviewer
 description: "Reviews CLI source code, plans, or specs for AI agent readiness using a severity-based rubric focused on whether a CLI is merely usable by agents or genuinely optimized for them."
-model: inherit
 tools: Read, Grep, Glob, Bash
 color: yellow
 ---

package/agents/review/cli-readiness-reviewer.md

@@ -1,7 +1,6 @@
 ---
 name: cli-readiness-reviewer
 description: "Conditional code-review persona, selected when the diff touches CLI command definitions, argument parsing, or command handler implementations. Reviews CLI code for agent readiness -- how well the CLI serves autonomous agents, not just human users."
-model: inherit
 tools: Read, Grep, Glob, Bash
 color: blue
 ---

package/agents/review/code-simplicity-reviewer.md

@@ -1,7 +1,6 @@
 ---
 name: code-simplicity-reviewer
 description: "Final review pass to ensure code is as simple and minimal as possible. Use after implementation is complete to identify YAGNI violations and simplification opportunities."
-model: inherit
 tools: Read, Grep, Glob, Bash
 ---
 

package/agents/review/correctness-reviewer.md

@@ -1,7 +1,6 @@
 ---
 name: correctness-reviewer
 description: Always-on code-review persona. Reviews code for logic errors, edge cases, state management bugs, error propagation failures, and intent-vs-implementation mismatches.
-model: inherit
 tools: Read, Grep, Glob, Bash
 color: blue
 mode: subagent

package/agents/review/data-integrity-guardian.md

@@ -1,7 +1,6 @@
 ---
 name: data-integrity-guardian
 description: "Reviews database migrations, data models, and persistent data code for safety. Use when checking migration safety, data constraints, transaction boundaries, or privacy compliance."
-model: inherit
 tools: Read, Grep, Glob, Bash
 ---
 

package/agents/review/data-migration-expert.md

@@ -1,7 +1,6 @@
 ---
 name: data-migration-expert
 description: "Validates data migrations, backfills, and production data transformations against reality. Use when PRs involve ID mappings, column renames, enum conversions, or schema changes."
-model: inherit
 tools: Read, Grep, Glob, Bash
 ---
 

package/agents/review/data-migrations-reviewer.md

@@ -1,7 +1,6 @@
 ---
 name: data-migrations-reviewer
 description: Conditional code-review persona, selected when the diff touches migration files, schema changes, data transformations, or backfill scripts. Reviews code for data integrity and migration safety.
-model: inherit
 tools: Read, Grep, Glob, Bash
 color: blue
 mode: subagent

package/agents/review/deployment-verification-agent.md

@@ -1,7 +1,6 @@
 ---
 name: deployment-verification-agent
 description: "Produces Go/No-Go deployment checklists with SQL verification queries, rollback procedures, and monitoring plans. Use when PRs touch production data, migrations, or risky data changes."
-model: inherit
 tools: Read, Grep, Glob, Bash
 ---
 

package/agents/review/dhh-rails-reviewer.md

@@ -1,7 +1,6 @@
 ---
 name: dhh-rails-reviewer
 description: Conditional code-review persona, selected when Rails diffs introduce architectural choices, abstractions, or frontend patterns that may fight the framework. Reviews code from an opinionated DHH perspective.
-model: inherit
 tools: Read, Grep, Glob, Bash
 color: blue
 mode: subagent

package/agents/review/julik-frontend-races-reviewer.md

@@ -1,7 +1,6 @@
 ---
 name: julik-frontend-races-reviewer
 description: Conditional code-review persona, selected when the diff touches async UI code, Stimulus/Turbo lifecycles, or DOM-timing-sensitive frontend behavior. Reviews code for race conditions and janky UI failure modes.
-model: inherit
 tools: Read, Grep, Glob, Bash
 color: blue
 mode: subagent

package/agents/review/kieran-python-reviewer.md

@@ -1,7 +1,6 @@
 ---
 name: kieran-python-reviewer
 description: Conditional code-review persona, selected when the diff touches Python code. Reviews changes with Kieran's strict bar for Pythonic clarity, type hints, and maintainability.
-model: inherit
 tools: Read, Grep, Glob, Bash
 color: blue
 mode: subagent

package/agents/review/kieran-rails-reviewer.md

@@ -1,7 +1,6 @@
 ---
 name: kieran-rails-reviewer
 description: Conditional code-review persona, selected when the diff touches Rails application code. Reviews Rails changes with Kieran's strict bar for clarity, conventions, and maintainability.
-model: inherit
 tools: Read, Grep, Glob, Bash
 color: blue
 mode: subagent

package/agents/review/kieran-typescript-reviewer.md

@@ -1,7 +1,6 @@
 ---
 name: kieran-typescript-reviewer
 description: Conditional code-review persona, selected when the diff touches TypeScript code. Reviews changes with Kieran's strict bar for type safety, clarity, and maintainability.
-model: inherit
 tools: Read, Grep, Glob, Bash
 color: blue
 mode: subagent

package/agents/review/maintainability-reviewer.md

@@ -1,7 +1,6 @@
 ---
 name: maintainability-reviewer
 description: Always-on code-review persona. Reviews code for premature abstraction, unnecessary indirection, dead code, coupling between unrelated modules, and naming that obscures intent.
-model: inherit
 tools: Read, Grep, Glob, Bash
 color: blue
 mode: subagent

package/agents/review/pattern-recognition-specialist.md

@@ -1,7 +1,6 @@
 ---
 name: pattern-recognition-specialist
 description: "Analyzes code for design patterns, anti-patterns, naming conventions, and duplication. Use when checking codebase consistency or verifying new code follows established patterns."
-model: inherit
 tools: Read, Grep, Glob, Bash
 ---
 

package/agents/review/performance-oracle.md

@@ -1,7 +1,6 @@
 ---
 name: performance-oracle
 description: "Analyzes code for performance bottlenecks, algorithmic complexity, database queries, memory usage, and scalability. Use after implementing features or when performance concerns arise."
-model: inherit
 tools: Read, Grep, Glob, Bash
 ---
 

package/agents/review/performance-reviewer.md

@@ -1,7 +1,6 @@
 ---
 name: performance-reviewer
 description: Conditional code-review persona, selected when the diff touches database queries, loop-heavy data transforms, caching layers, or I/O-intensive paths. Reviews code for runtime performance and scalability issues.
-model: inherit
 tools: Read, Grep, Glob, Bash
 color: blue
 mode: subagent

package/agents/review/previous-comments-reviewer.md

@@ -1,7 +1,6 @@
 ---
 name: previous-comments-reviewer
 description: Conditional code-review persona, selected when reviewing a PR that has existing review comments or review threads. Checks whether prior feedback has been addressed in the current diff.
-model: inherit
 tools: Read, Grep, Glob, Bash
 color: yellow
 

package/agents/review/project-standards-reviewer.md

@@ -1,7 +1,6 @@
 ---
 name: project-standards-reviewer
 description: Always-on code-review persona. Audits changes against the project's own AGENTS.md standards -- frontmatter rules, reference inclusion, naming conventions, cross-platform portability, and tool selection policies.
-model: inherit
 tools: Read, Grep, Glob, Bash
 color: blue
 

package/agents/review/reliability-reviewer.md

@@ -1,7 +1,6 @@
 ---
 name: reliability-reviewer
 description: Conditional code-review persona, selected when the diff touches error handling, retries, circuit breakers, timeouts, health checks, background jobs, or async handlers. Reviews code for production reliability and failure modes.
-model: inherit
 tools: Read, Grep, Glob, Bash
 color: blue
 mode: subagent

package/agents/review/schema-drift-detector.md

@@ -1,7 +1,6 @@
 ---
 name: schema-drift-detector
 description: "Detects unrelated schema.rb changes in PRs by cross-referencing against included migrations. Use when reviewing PRs with database schema changes."
-model: inherit
 tools: Read, Grep, Glob, Bash
 ---
 

package/agents/review/security-reviewer.md

@@ -1,7 +1,6 @@
 ---
 name: security-reviewer
 description: Conditional code-review persona, selected when the diff touches auth middleware, public endpoints, user input handling, or permission checks. Reviews code for exploitable vulnerabilities.
-model: inherit
 tools: Read, Grep, Glob, Bash
 color: blue
 mode: subagent

package/agents/review/security-sentinel.md

@@ -1,7 +1,6 @@
 ---
 name: security-sentinel
 description: "Performs security audits for vulnerabilities, input validation, auth/authz, hardcoded secrets, and OWASP compliance. Use when reviewing code for security issues or before deployment."
-model: inherit
 tools: Read, Grep, Glob, Bash
 ---
 

package/agents/review/testing-reviewer.md

@@ -1,7 +1,6 @@
 ---
 name: testing-reviewer
 description: Always-on code-review persona. Reviews code for test coverage gaps, weak assertions, brittle implementation-coupled tests, and missing edge case coverage.
-model: inherit
 tools: Read, Grep, Glob, Bash
 color: blue
 

package/agents/workflow/bug-reproduction-validator.md

@@ -1,7 +1,6 @@
 ---
 name: bug-reproduction-validator
 description: Systematically reproduces and validates bug reports to confirm whether reported behavior is an actual bug. Use when you receive a bug report or issue that needs verification.
-model: inherit
 mode: subagent
 temperature: 0.1
 ---

package/agents/workflow/lint.md

@@ -1,7 +1,6 @@
 ---
 name: lint
 description: Use this agent when you need to run linting and code quality checks on Ruby and ERB files. Run before pushing to origin.
-model: inherit
 color: yellow
 mode: subagent
 temperature: 0.1

package/agents/workflow/pr-comment-resolver.md

@@ -2,7 +2,6 @@
 name: pr-comment-resolver
 description: "Evaluates and resolves one or more related PR review threads -- assesses validity, implements fixes, and returns structured summaries with reply text. Spawned by the resolve-pr-feedback skill."
 color: blue
-model: inherit
 ---
 
 You resolve PR review threads. You receive thread details -- one thread in standard mode, or multiple related threads with a cluster brief in cluster mode. Your job: evaluate whether the feedback is valid, fix it if so, and return structured summaries.

package/agents/workflow/spec-flow-analyzer.md

@@ -1,7 +1,6 @@
 ---
 name: spec-flow-analyzer
 description: "Analyzes specifications and feature descriptions for user flow completeness and gap identification. Use when a spec, plan, or feature description needs flow analysis, edge case discovery, or requirements validation."
-model: inherit
 ---
 
 Analyze specifications, plans, and feature descriptions from the end user's perspective. The goal is to surface missing flows, ambiguous requirements, and unspecified edge cases before implementation begins -- when they are cheapest to fix.

package/dist/index.js

@@ -310,6 +310,37 @@ function registerSkillsPaths(config, skillsDir) {
   }
 }
 
+// src/lib/plugin-singleton.ts
+var SINGLETON_KEY = Symbol.for("systematic.singleton.v1");
+async function plugInOnce({
+  doInit,
+  onDuplicate,
+  pid
+}) {
+  const currentPid = pid ?? process.pid;
+  const g = globalThis;
+  const existing = g[SINGLETON_KEY];
+  if (existing && existing.pid === currentPid) {
+    if (!existing.warned) {
+      existing.warned = true;
+      try {
+        onDuplicate?.(currentPid);
+      } catch {}
+    }
+    await existing.hooksPromise;
+    return { isFirst: false, hooks: {} };
+  }
+  const hooksPromise = doInit();
+  g[SINGLETON_KEY] = {
+    pid: currentPid,
+    loadedAt: Date.now(),
+    hooksPromise,
+    warned: false
+  };
+  const hooks = await hooksPromise;
+  return { isFirst: true, hooks };
+}
+
 // src/lib/skill-tool.ts
 import fs2 from "fs";
 import path3 from "path";
@@ -493,7 +524,7 @@ var getPackageVersion = () => {
     return "unknown";
   }
 };
-var SystematicPlugin = async ({ client, directory }) => {
+var initializePlugin = async ({ client, directory }) => {
   const config = loadConfig(directory);
   const bootstrapContent = getBootstrapContent(config, { bundledSkillsDir });
   const configHandler = createConfigHandler({
@@ -551,6 +582,23 @@ var SystematicPlugin = async ({ client, directory }) => {
     }
   };
 };
+var SystematicPlugin = async (input) => {
+  const { hooks } = await plugInOnce({
+    doInit: () => initializePlugin(input),
+    onDuplicate: (pid) => {
+      const message = `[systematic] duplicate factory invocation in same process (pid=${pid}); skipping duplicate registration. Multiple opencode.json sources may list this plugin.`;
+      console.warn(message);
+      input.client.app.log({
+        body: {
+          service: "systematic",
+          level: "warn",
+          message
+        }
+      }).catch(() => {});
+    }
+  });
+  return hooks;
+};
 var src_default = SystematicPlugin;
 export {
   src_default as default

package/dist/lib/plugin-singleton.d.ts

@@ -0,0 +1,78 @@
+/**
+ * Per-process register-once guard for the Systematic plugin factory.
+ *
+ * OpenCode invokes the plugin factory more than once per process when the
+ * same plugin is referenced by multiple config sources (for example a
+ * user-level `~/.config/opencode/opencode.json` AND a project-level
+ * `opencode.json`). Each invocation evaluates the plugin module fresh —
+ * module-local variables reset between calls — so the guard state must
+ * live on `globalThis` to persist across module instances within the
+ * same process.
+ *
+ * On the first invocation `doInit` runs and the resulting hooks promise
+ * is cached on `globalThis`; the caller receives `{ isFirst: true, hooks }`.
+ * On every subsequent invocation in the same PID `doInit` is skipped, the
+ * cached promise is awaited (so sticky rejections still propagate),
+ * `onDuplicate` fires exactly once, and the caller receives
+ * `{ isFirst: false, hooks: {} as T }`. Across PIDs the guard is treated
+ * as absent and init runs fresh — `globalThis` is per-process, but the
+ * explicit PID check adds defensive belt-and-suspenders against any
+ * state-leakage edge case.
+ *
+ * **Why empty hooks on duplicate invocations.** A whole-hooks singleton
+ * that returns the same hooks reference to both invocations does not
+ * deduplicate host-side tool registration: OpenCode iterates each plugin
+ * source's returned hook surface and registers every tool entry it finds,
+ * even when two sources return the same JS reference. Returning `{}` from
+ * the duplicate path is the only shape that prevents host-side double
+ * registration of `systematic_skill`, the `config` hook, and the
+ * `experimental.chat.system.transform` hook. The Phase 0 follow-up probe
+ * (see `docs/plans/2026-05-01-001-fix-idempotent-plugin-registration-plan.md`)
+ * verified the duplicate `systematic_skill` entry in OpenCode's
+ * `client.tool.list(...)` output, which is the LLM-visible tool catalog.
+ *
+ * **Known limitation — rejected init is sticky.** If `doInit()` rejects,
+ * the rejected promise is stored on `globalThis` and every subsequent
+ * invocation in the same PID returns the same rejection without retrying
+ * init. This is intentional: re-running heavy init on every call would
+ * defeat the guard's purpose. Recovery requires a process restart.
+ */
+export interface PlugInOnceOptions<T> {
+    /** Heavy init work that should run at most once per process. */
+    doInit: () => Promise<T>;
+    /**
+     * Called exactly once on the first duplicate invocation in the same
+     * process. Subsequent duplicates are silent. Receives the same `pid`
+     * value the guard used for its identity check (so test overrides flow
+     * through faithfully). Implementations must not throw; fire-and-forget
+     * side effects (logging, metrics) are expected. Synchronous exceptions
+     * are swallowed defensively.
+     */
+    onDuplicate?: (pid: number) => void;
+    /** Test override; defaults to `process.pid`. */
+    pid?: number;
+}
+/**
+ * Result envelope for `plugInOnce(...)`.
+ *
+ * - `isFirst: true` — caller should return `hooks` to OpenCode.
+ * - `isFirst: false` — caller MUST return `hooks` (which is an empty `{}`)
+ *   so the host loader does not register tools or hooks twice.
+ *
+ * Callers that just `return result.hooks` do the right thing in both
+ * cases without needing to inspect `isFirst`.
+ */
+export interface PlugInOnceResult<T> {
+    isFirst: boolean;
+    hooks: T;
+}
+/**
+ * Run `doInit` at most once per process; on duplicate invocations resolve to
+ * empty hooks so the OpenCode host does not double-register tools and hooks.
+ */
+export declare function plugInOnce<T>({ doInit, onDuplicate, pid, }: PlugInOnceOptions<T>): Promise<PlugInOnceResult<T>>;
+/**
+ * Test-only: clear the singleton state so the next invocation re-runs
+ * init. Must not be called in production code paths.
+ */
+export declare function _resetPluginSingleton(): void;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fro.bot/systematic",
-  "version": "2.7.1",
+  "version": "2.7.3",
   "description": "Structured engineering workflows for OpenCode",
   "type": "module",
   "homepage": "https://fro.bot/systematic",

package/skills/writing-systematic-skills/SKILL.md

@@ -27,7 +27,7 @@ Systematic adds repository-specific constraints:
 
 - Runtime-recognized frontmatter fields are fixed by the skill loader.
 - Skill sub-files live in a small set of conventional directories.
-- Bundled agents must use provider-portable model defaults.
+- Bundled agents omit the `model` field; subagents inherit the invoking primary agent's model.
 - Content-integrity enforces the mechanical parts in CI.
 
 For worked examples and judgment calls, read `references/foundation-conventions.md`.
@@ -76,13 +76,17 @@ Keep the main `SKILL.md` small enough to decide whether and how to proceed. Move
 
 ## Identity Defaults
 
-Bundled agents must declare:
+Bundled agents must omit the `model` field entirely:
 
 ```yaml
-model: inherit
+---
+name: example-agent
+description: ...
+# no `model:` line
+---
 ```
 
-Hardcoded provider model IDs break users who do not use that provider. Use `model: inherit` unless a future design explicitly proves a provider-specific dependency and documents the tradeoff.
+Per [OpenCode's agent docs](https://opencode.ai/docs/agents/), subagents with no `model` inherit the model of the primary agent that invoked them — which is the desired portable behavior. Do **not** declare `model: inherit`: that literal value is undocumented and produces `ProviderModelNotFoundError` on OpenCode older than ~v1.13.x (pre [sst/opencode#17888](https://github.com/sst/opencode/pull/17888)). Hardcoded provider model IDs (`anthropic/...`, `openai/...`, etc.) are also banned because they break users on other providers.
 
 For agent or API attribution, `ai:systematic` is the machine ID used by Systematic-owned operations, such as Proof's `by` field and `X-Agent-Id` header. It is not a skill cross-reference convention.
 
@@ -99,7 +103,7 @@ The gate checks:
 - Skill frontmatter is present and uses only runtime-recognized fields.
 - Required `name` and `description` fields are non-empty.
 - Banned frontmatter such as `preconditions` is absent.
-- Bundled agents use `model: inherit`.
+- Bundled agents omit the `model` field.
 - Skill references to `references/`, `scripts/`, `assets/`, and `templates/` resolve on disk.
 
 If the gate fails, fix the content rather than broadening the validator unless the runtime loader contract has actually changed.
@@ -110,6 +114,6 @@ If the gate fails, fix the content rather than broadening the validator unless t
 |---|---|
 | Adding a new frontmatter field because it reads well | Add body prose instead, unless the runtime loader consumes the field. |
 | Summarizing the whole workflow in `description` | Describe trigger conditions only. |
-| Adding provider-specific agent models | Use `model: inherit`. |
+| Adding any `model` field to a bundled agent | Omit the field; subagents inherit from the invoking primary agent. |
 | Linking to a non-existent reference file | Create the file or remove the link. |
 | Duplicating the general writing-skills guidance | Link to the foundation and document only the Systematic delta. |

package/skills/writing-systematic-skills/references/foundation-conventions.md

@@ -18,7 +18,7 @@ Systematic skill frontmatter mirrors what the runtime loader actually reads. Do
 | `metadata` | No | String-only metadata map. Keep it boring. | `metadata: { owner: systematic }` |
 | `user-invocable` | No | Direct user invocation should be explicitly advertised or suppressed. | `user-invocable: false` |
 | `agent` | No | A loader-supported companion agent is required. | `agent: general` |
-| `model` | No | A skill-level model choice is justified. Prefer inheritance elsewhere. | `model: inherit` |
+| `model` | No | A skill-level model choice is justified for *skill execution* (not bundled agents — see below). | `model: anthropic/claude-haiku-4-5` |
 | `context` | No | Forked execution is required. `fork` derives subtask behavior at runtime. | `context: fork` |
 | `subtask` | No | Explicit forked-subtask dispatch marker. | `subtask: true` |
 
@@ -106,15 +106,21 @@ Avoid ambiguous references such as "the conventions doc". They are harder for ag
 
 ### Bundled Agent Model
 
-Bundled agents must use:
+Bundled agents must omit the `model` field entirely:
 
 ```yaml
-model: inherit
+---
+name: example-agent
+description: ...
+# no `model:` line
+---
 ```
 
-This keeps Systematic provider-portable. Hardcoded provider IDs make an agent unusable for users on other providers and are almost never worth the lock-in.
+Per [OpenCode's agent docs](https://opencode.ai/docs/agents/): **"If you don't specify a model, primary agents use the model globally configured while subagents will use the model of the primary agent that invoked the subagent."** All bundled Systematic agents are subagents, so omitting `model` gives the desired portable inheritance behavior.
 
-If a future agent truly depends on a specific provider, document the constraint in the plan and get explicit review before adding the hardcoded model.
+Do **not** declare `model: inherit`. That literal value is undocumented and was treated as a real provider/model string by `Provider.parseModel()` until [sst/opencode#17888](https://github.com/sst/opencode/pull/17888) landed in mid-March 2026 — producing `ProviderModelNotFoundError` on every subagent invocation for anyone on an older OpenCode. Omitting the field works on every OpenCode version and is what the docs canonically describe.
+
+Hardcoded provider IDs (`anthropic/claude-...`, `openai/gpt-...`, etc.) are also banned because they make an agent unusable for users on other providers. If a future agent truly depends on a specific provider, document the constraint in the plan and get explicit review before adding the hardcoded model.
 
 ### Machine ID