Skip to content

Releases

v1.0.0

Choose a tag to compare

@github-actions github-actions released this 11 Oct 01:23

Changed

  • Upgraded to the OpenCode v2 plugin system. The plugin entrypoint is now an Effect-first Plugin.define({ id, effect }) in src/plugin.ts, default-re-exported from index.ts; the root plugin.ts shim is removed and dropped from files, and package.json declares content: "code" with exports for both . and ./server. This replaces the v1 config() hook on @opencode-ai/plugin. Load-time behavior is unchanged: scope-aware, manifest-gated install-on-load, read-only registration detection, once-per-session not-installed advisory, skipped-file warnings. The direct dependency is @opencode/plugin at latest (2.0.26); effect intentionally stays on the ^4.0.0-rc.112 caret the entire @opencode plugin stack pins — latest (4.0.2) would fork Effect across the plugin boundary.
  • Installer writes v2-native config keys. bunx aurelia-expert install adds aurelia-expert@latest to the plugins array and grants skills via the ordered permissions ruleset ({ action: "skill", resource: "<skill-id>", effect: "allow" }); uninstall cleans both plugins and a legacy plugin entry. Detection reads plugins first and falls back read-only to the legacy singular plugin key, so v1-era registrations are not duplicated.
  • Load-time installs never write consumer config. Permission-ruleset writes and legacy permission.skill migration are gated behind explicit CLI installs (configurePermissions); the load path performs zero config writes (ADR-0007, refining ADR-0005).
  • Config edits are byte-preserving text splices. plugins/permissions mutations anchor into the raw file text and preserve every other byte — comments, indentation, key order — refusing to write when no anchor exists instead of reformatting the file; only fresh-file creation still parses and serializes.
  • Consumer docs realigned. README badges collapse to a single row under the title with canonical aurelia-expert@latest snippets, and the install snippets and load-contract description now teach the plugins array; CONTRIBUTING is rewritten against the current surface (v1 plugin-key snippet and stale v1 prose removed); the release workflow verifies the publishable tarball with npm pack --dry-run before publishing.
  • Skill frontmatter values are double-quoted across all eight skills (native booleans stay bare); contract tests parse frontmatter as YAML and assert the quoting.
  • Dev self-config (.opencode/opencode.json) rewritten to v2-native keys: plugins: ["opencode-architect@latest"] (1.0.0 is the latest release; expressed as @latest per policy). The skills: { paths: [...] } entry was dropped — .agents/skills is natively discovered by OpenCode v2 from any working directory inside the repo, which is more robust than a CWD-relative explicit path.

Added

  • Path-form self-registration detection. Registration detection recognizes plugins/plugin entries that are file:// URLs or filesystem paths resolving to this package — the package root, an entrypoint file such as index.ts, a package.json, or a symlink — by the resolved package.json name, with the same normalization as bare names. Best-effort and read-only: unresolvable or missing paths never match and never throw. bunx aurelia-expert install recognizes existing path-form entries instead of adding a duplicate npm-name entry beside them.
  • bunx aurelia-expert clear-cache plus install-time pruning of this package's own npm cache generations (aurelia-expert, aurelia-expert@latest, aurelia-expert@<version>) — self-only, warn-and-continue; the load hook instructs and never deletes.
  • Failure advisory hardened: emitted at most once per process under its own guard, independent of the not-installed advisory, naming the remediation command (bunx aurelia-expert install --scope global) and the package-qualified npm cache key, with a literal <version> fallback when package metadata is unavailable. Missing bundled skill sources error with the path, package version, cache directory, and reinstall command — CLI hard-exits, load warns.
  • Detection now reads opencode.json and opencode.jsonc, warns once per path on unparseable candidates, and advises read-only when a legacy global config.json mentions the package.
  • tests/plugin.test.ts — first coverage of the plugin entrypoint: v2 export shape through both entrypoints, install-on-load, advisory-once with zero writes when uninstalled, and skipped-consumer-modified-file warning. tests/v2-host.test.ts and tests/fixture-config-schema.test.ts harness the v2 host contract and @opencode/schema Config.Info decoding; tests/config-splice.test.ts and tests/advisory.test.ts pin the splice-writer and advisory contracts.
  • ADR-0006: config-key migration to OpenCode v2 (supersedes the key shapes in ADR-0005's letter; its installer-owns-config principle stands).
  • ADR-0007: the load path never writes consumer config — permission-ruleset writes and legacy permission.skill migration are CLI-only (refines ADR-0005's installer-owns-config principle).

v0.6.0

Choose a tag to compare

@github-actions github-actions released this 06 Oct 01:55

Changed

  • Surgical config writes. writeJsonConfig no longer parses-and-reserializes consumer configs. A new ConfigSpliceWriter (+ JsoncScanner) splices only the missing plugin entries / permission.skill grants into the raw text, preserving comments, indentation, key order, and unrelated bytes; ambiguous or unscannable shapes abort with a warning instead of rewriting. Handles opencode.jsonc end to end.
  • jsonc-aware scope detection. Registration detection now reads opencode.json and opencode.jsonc (global config, repo .opencode/, repo root). An existing-but-unparseable candidate yields an unknown context that short-circuits the load path with zero writes and a warning, instead of being silently treated as unregistered.
  • Permission writes are CLI-only. The load path never writes permission.skill grants anymore; ensureSkillPermissions runs only on explicit bunx aurelia-expert install.
  • Deployment plan declared. package.json now carries "content": "code". bunx aurelia-expert install --mode copy raises CopyModeUnsupportedError — code-backed packages register only; --mode register remains the default.
  • Hook implementation moved under src/. Root plugin.ts is now a one-line re-export of src/plugin.ts; all code lives under src/.
  • Release workflow verifies the tarball. The publish job runs npm pack --dry-run and asserts the expected file set (index.ts, plugin.ts, src, skills, README.md, AGENTS.md, CHANGELOG.md, LICENSE) before npm publish.

Fixed

  • The load hook can no longer throw into OpenCode startup. The entire config() body is wrapped; a failure emits a remediation advisory (bunx aurelia-expert install --scope global|local, the exact ~/.cache/opencode/packages/aurelia-expert@<version> dir, and bunx aurelia-expert clear-cache) guarded by its own once-guard, independent of the install advisory.
  • Missing bundled assets fail loudly and completely. A missing skill directory raises MissingSkillAssetError naming the package version, the missing path, the cache directory, and the remediation commands, instead of a raw ENOENT.
  • Cache hygiene. New bunx aurelia-expert clear-cache subcommand removes this package's current and stale @<version> cache directories.
  • README badge row collapsed to a single line directly below the heading; all eight SKILL.md frontmatter values are now double-quoted (colon-space guard and dispatch keys intact); CONTRIBUTING.md rewritten for the manifest-gated / RegistrationDetector era.

Added

  • Contract tests for the new guarantees: jsonc detection and comment-preserving splices, byte-preservation of unrelated config bytes, unknown-config zero-writes, loud asset-absence errors, load-path no-writes (plugin arrays and permissions), hook never throwing with exactly-once advisories, --mode copy rejection, and clear-cache behavior.

v0.5.2

Choose a tag to compare

@github-actions github-actions released this 18 Sep 14:16

Changed

  • Dev .opencode/opencode.json now registers the opencode-architect plugin by package name instead of a machine-specific file:/// path.

v0.5.1

Choose a tag to compare

@github-actions github-actions released this 18 Sep 14:14

Changed

  • Root-config migration is now opt-in. bunx aurelia-expert install no longer migrates a legacy root opencode.json to .opencode/opencode.json implicitly; pass --migrate-root-config to enable it (or --no-migrate-root-config to be explicit). Unparseable-config blocking behavior is unchanged.

Fixed

  • Conformance hardening against the opencode-architect checklist: README badge row completed with Bun runtime and platforms badges; skill frontmatter ground-truth URL values double-quoted for full YAML hygiene (descriptions untouched — em-dash separators preserved, colon-space guard intact).

v0.5.0

Choose a tag to compare

@github-actions github-actions released this 16 Sep 19:48

Changed

  • Load-time installation rebuilt to the scope-aware, manifest-gated model. plugin.ts#config() now detects where the plugin is registered — global config, repo .opencode/opencode.json, or a repo-root opencode.json — using semantic, @latest-aware name matching (RegistrationDetector, src/registration.ts), then ensures the skills only in the detected scope(s). Detection is read-only.
  • Manifest-gated idempotency shared by the CLI and the load path. Each install writes <configBase>/aurelia-expert.manifest.json with per-file sha256 hashes. Present manifest + matching version + matching hashes → zero-write no-op; version drift → upgrade that scope only; consumer-modified files → skip + warn at load, overwrite only with CLI --force. .version markers are obsolete and reconciled/removed on first manifest-era install.

Fixed

  • Cross-scope leak and dead fast path in the load hook. The old ScopeResolver keyed off the launch directory (which opencode always sets to the consumer repo), and the local fast path checked a marker at <repo>/skills/… while the installer wrote to <repo>/.opencode/skills/… — so every start reinstalled unconditionally. Hard invariants now enforced and tested: no cross-scope writes, the hook never edits plugin arrays, root opencode.json migration is CLI-only, unparseable configs abort with a warning and are preserved byte-for-byte (never rewritten from {}), and plugin references are written canonically as aurelia-expert@latest with semantic dedup.

v0.4.0

Choose a tag to compare

@github-actions github-actions released this 07 Sep 21:09

Added

  • Skill content synced to Aurelia 2.0.0-rc.1 / 2.0.0-rc.2 (validated against DeepWiki + raw source): useEagerLoading router option, containerless <au-viewport> support, canUnload route-context restoration, writable RouteNode.title, task-queue timed slices with tasksSettled() and TaskQueueAggregateError (events-tasks.md), and the deprecated built-in .email() validation rule with its RFC-compliant replacement (validation.md).

Changed

  • .delegate and .call are removed from the v2 binding command set entirely — for custom AND native DOM events alike (source-verified in packages/template-compiler/src/binding-command.ts; AUR0713's help text states the removal). All ~59 skill-body statements claiming ".delegate stays valid for native DOM events" corrected across 15 files; .capture documented as the capture-phase command and lambdas as the .call replacement; @aurelia/compat-v1's compatRegistration noted as the incremental-migration escape hatch.
  • AGENTS.md critical rule 1 and the skill_content_rules ERROR-CODE taxonomy now scope the AUR0713 rule to .delegate on any event (previously "custom events" only).

Fixed

  • DI error-code audit (DeepWiki + kernel/template-compiler source): AUR0010 corrected to "intrinsic type used as a DI token" (was "resolve() of unregistered token"); new rows for AUR0012 (interface with no registration/default) and AUR0017 (same via newInstanceOf/newInstanceForScope, PR #2438); AUR0019 corrected to invalid Event Aggregator publish event name/instance; AUR0022 corrected to @inject on an unsupported target type; containerless + Shadow DOM re-mapped from AUR0901 to the real AUR0501; AUR0907 corrected to dialog cancel-with-rejectOnCancel (no error code exists for hyphen-less element names — kebab-case stays as a convention guardrail). AUR0713 row broadened to "unknown binding command" with the verified valid-command list; AUR0177 row sharpened to the confirmed destructuring triggers (nested patterns, duplicate locals, reserved names).
  • @inject DEPRECATED violations: all remaining "removed"/"does not work"/"never" statements corrected to the canonical "deprecated — resolve() preferred": di.md (×2), au-northwind-pointer.md ("Never use" list), ai-tooling.md scaffold prompt, README.md ("is gone in v2"), v1-removals.md (FORBIDDEN framing + example comment), components.md contamination list.

v0.3.0

Choose a tag to compare

@github-actions github-actions released this 15 Jul 04:02

Added

  • New bundled skill aurelia-ecosystem — leading word wire, seventh pillar (eighth skill overall). Owns the first-party plugin and runtime-ecosystem surface ported and adapted from the vendor aurelia/skills package: @aurelia/fetch-client (HTTP), @aurelia/validation, @aurelia/dialog, @aurelia/state, @aurelia/i18n, forms (model.bind/matcher.bind/submit.trigger:prevent), Vitest + @aurelia/testing component testing, and SSR/prerendering (aurelia2-ssr, remount takeover, hydration, sitemap/robots). Each ported reference carries an upstream-lineage comment and adapts to this package's guardrails (resolve() DI, dispose-hook cleanup for IEventAggregator, narrow .style rule, prohibitions deferred to aurelia-migration/reference/v1-removals.md).
  • New aurelia-foundation/reference/cli.md — the deeper npx makes aurelia feature-flag reference (scaffold pillar), linked from the foundation reference table.
  • Router (aurelia-expert) gains a seventh branch ladder position: wire → aurelia-ecosystem after package. Description, branch table, pillar-location tree, and handoff block updated.

Changed

  • src/installer.ts SKILL_NAMES and tests/skills.test.ts SKILL_NAMES + REFERENCE_FILES now include aurelia-ecosystem (and cli.md under aurelia-foundation); the installer copies the new skill on every install/uninstall cycle and the test suite asserts every reference file is non-empty.
  • Removed the misguided .opencode/opencode.json pre-allows self-config test from tests/skills.test.ts. The repo's .opencode/opencode.json is a dev-only config (not shipped via package.json#files; does not reference the package's own skills). Consumer permission.skill allow-listing for every bundled skill is written by Installer.ensureSkillPermissions at install time and is already verified by tests/installer.test.ts ("writes permission.skill.allow for every bundled skill").

Fixed

  • Dangling aurelia-testing deferrals in aurelia-largespa/SKILL.md and aurelia-migration/SKILL.md now point to aurelia-ecosystem (testing reference). The two pillars previously deferred to a non-existent aurelia-testing skill.

v0.2.0

Choose a tag to compare

@github-actions github-actions released this 14 Jul 09:51

Added

  • New bundled skill aurelia-component-library — leading word assemble, sixth pillar. Owns the styled, variable-driven component-library workflow on Aurelia v2 + Tailwind: design-token layer (CSS custom properties on the root element with the Tailwind @theme bridge), shared/components/ui/ library layout with the ui- element prefix, component anatomy (@bindable variants/sizes, <au-slot> projection in Light DOM, .style property binding), a greenfield deploy procedure, and a migrate-existing procedure with a v1-source gate that defers to aurelia-migration (lift) before any structural move.
  • Router (aurelia-expert) gains a fifth branch ladder position: assemble → aurelia-component-library between resolve and slice. The skill table, branch table, pillar-location tree, and precedence note all updated; precedence clarifies that mixed library + v1 prompts go to lift first (the more constrained case wins), then assemble for the lifted v2 code.
  • New bundled skill aurelia-plugin — leading word package, seventh pillar. Owns the distributable-plugin workflow on Aurelia v2: the register(container) duck-typed entry point, the .customize() options pattern with DI.createInterface tokens, global resource registration with plugin-name prefixes, AppTask lifecycle hooks, rendering-pipeline extensions (IRenderer/@renderer, IRendering, registerHostNode), npm distribution (peerDependencies on aurelia, dual ESM/CJS + .d.ts, explicit ?raw template imports, types/assets.d.ts), and an extract procedure (component-library / feature-slice / shared-dir → plugin) with a v1-source gate that defers to aurelia-migration (lift) before any packaging move.
  • Router (aurelia-expert) gains a sixth branch ladder position: package → aurelia-plugin after lift. Branch table, pillar-location tree, and precedence notes updated; three new precedence sub-rules disambiguate plugin vs component-library, largespa, and migration (v1 source → lift first).
  • aurelia-expert router gains a ground-truth note: for SDK and API questions, prefer GitHub (aurelia/aurelia master branch) as canonical source for the latest. DeepWiki (deepwiki_ask_question against aurelia/aurelia) is the preferred validator; docs.aurelia.io is fallback for overview content only.
  • AGENTS.md gains a <skill_content_rules> section with five codified lessons from a systematic DeepWiki validation sweep of all seven skills: source hierarchy (GitHub > DeepWiki > docs.aurelia.io > NotebookLM), error-code confirmation requirement, @inject severity levels (REMOVED / DEPRECATED / ERROR CODE), .style binding narrow rule (not blanket prohibition), and dispose as the mandatory IEventAggregator cleanup hook.

Changed

  • src/installer.ts SKILL_NAMES array and tests/skills.test.ts SKILL_NAMES + REFERENCE_FILES now include aurelia-component-library and aurelia-plugin; the installer copies them on every install/uninstall cycle and the test suite asserts every reference file is non-empty.
  • .opencode/opencode.json permission allow-list extended to seven skills.

Fixed

  • AUR0009 → AUR0713 (compile-time): .delegate on custom events throws AUR0713 (template compilation error), not AUR0009. All 25 occurrences corrected across reference/v1-removals.md, reference/debugging.md, skills/aurelia-runtime/SKILL.md, skills/aurelia-foundation/SKILL.md, skills/aurelia-plugin/SKILL.md, skills/aurelia-migration/SKILL.md, and all affected reference files. This was a v1-era error code that did not exist in the v2 template compiler.
  • @inject reclassified as DEPRECATED: @inject is still valid in Aurelia v2 — it is not REMOVED. All skill bodies that stated "never use @inject" or "does not appear anywhere in v2" corrected to "prefer resolve() (still valid but idiomatic v2)". The v1-removals table now says DEPRECATED — prefer resolve(); the canonical severity levels in reference/v1-removals.md are the source of truth and must not be contradicted in skill bodies.
  • .style binding — narrow rule, not blanket prohibition: Inline style="width: ${value}%" is safe when the value is guaranteed non-falsy; the prod-optimizer bug only triggers for 0/false/''. Four skill files that said "never inline style=" corrected to the precise conditional: prefer .style binding when the interpolated value can be falsy.
  • IEventAggregator disposal — dispose, not unbinding: dispose is the mandatory permanent cleanup hook for IEventAggregator subscriptions; unbinding runs before potential reactivation and is insufficient. Foundation pillar guardrail corrected; all skill bodies updated accordingly.
  • All skill-count references corrected: README.md (SEO title, H1, intro paragraph, v1-contamination bullet), package.json description, aurelia-plugin/SKILL.md V1 contamination section, and au-northwind-pointer.md now accurately state 7 skills / 6 pillars / 6 prohibited + 1 deprecated v1 pattern.
  • Description fields on aurelia-foundation, aurelia-runtime, and aurelia-migration SKILL.md frontmatter use em-dash (—) instead of colon-space (: ) to avoid the YAML nested-mapping parse error in the skills CLI.

v0.1.0

Choose a tag to compare

@github-actions github-actions released this 13 Jul 22:53

Added

  • Initial release of the aurelia-expert OpenCode plugin + npm skill bundle.
  • Five router-routed Aurelia v2 MVVM skills:
    • aurelia-expert — leading word branch, dispatches to the right pillar.
    • aurelia-foundation — leading word scaffold, philosophy, quickstart, components, lifecycle, AI tooling.
    • aurelia-runtime — leading word resolve, DI, routing, events/tasks, cross-feature orchestration.
    • aurelia-largespa — leading word slice (focal point), feature-first layout, hierarchical Agents.md, orchestrator pattern, Model/DTO boundary.
    • aurelia-migration — leading word lift, v1→v2 removals, debugging, performance, DeepWiki citation protocol.
  • plugin.ts OpenCode plugin factory with version-marker gated config() hook that auto-installs on first load.
  • src/installer.ts Installer class with install(), uninstall(), status(), idempotent version-marker copy, permission pre-grant, plugin entry add/remove, and migrateRootConfig() for legacy opencode.json → .opencode/opencode.json migration.
  • src/plugin-name.ts PluginNameNormalizer class with case-insensitive @<version> stripping (scoped-package safe).
  • src/scope-resolver.ts ScopeResolver class that resolves local vs global scope from the plugin's working directory (cross-platform path separator).
  • src/cli.ts Bun-runnable CLI with install, uninstall, status subcommands (no interactive prompts; CI-friendly).
  • .opencode/opencode.json self-config registering ../skills and pre-allowing all 5 skills.
  • .github/workflows/release.yml two-job pipeline: GitHub Release (notes extracted from CHANGELOG.md) + npm publish --provenance --access public.
  • Test suites: tests/skills.test.ts (frontmatter + reference-file assertions, plugin-name normalization round-trip), tests/installer.test.ts (mocked temp project + global dirs, install/uninstall/status round-trips, idempotency, legacy migration).
  • MIT license, AGENTS.md maintainer contract, CONTRIBUTING.md developer guide, README.md with three-channel install story.