Skip to content

v0.10.0

Choose a tag to compare

@lair001 lair001 released this 11 Sep 08:14
· 10 commits to main since this release

APGR v0.10.0 release notes

Release status

This documentation covers v0.10.0. The release includes six frontend and web
profiles, reporting improvements, and qualification maintenance. Installation
instructions use v0.10.0 and apply once that version is published.

Frontend and web guidance

Six new provisional profiles bring the corpus to 45 skills:

  • SVG: namespaces, coordinates, geometry, paint and reuse.
  • Playwright Test: runner configuration, fixtures and browser assertions.
  • Web accessibility: native semantics, accessible names, keyboard operation
    and the hierarchy of automated and human checks.
  • Vite: development serving, production builds and environment handling.
  • npm: package metadata, lockfiles and reproducible installation.
  • Browser runtime: browser-host behavior and its boundary with JavaScript,
    Node and framework owners.

The profiles compose with existing JavaScript, TypeScript, JSX, React, CSS,
MDX and Astro guidance. Profile availability alone does not prove that an
agent selected or followed it.

Reporting and qualification maintenance

Persisted-report verification checks canonical and accepted historical
records without repairing the source file. Structured operational records
receive semantic validation. Opt-in idempotency distinguishes an exact retry
from conflicting content while retaining default append behavior.

Qualification maintenance covers delimiter-heavy verification, browser
scenario-family authority and Node identity-probe stream custody.

JavaScript qualification consolidates four resolved debt entries, preserves
the CommonJS seam with Node, and strengthens failure custody and static
process-call checks. JS-QD-005 remains active and condition-triggered.

Repo Map support

Reusable support available in v0.10.0 includes Go and Python
engineering guidance, PostgreSQL and SQLite ownership, bounded implementation
and testing practices, deterministic reporting, skill context and footprint
primitives. These can support Repo Map work without claiming Repo Map adoption.

The Repo Map support roadmap ships as
v0.10 documentation. Its RM-S0 through RM-S5 product gates replace a fixed
release promise for specialized support.

Future versioned-protocol and knowledge-graph-quality profiles remain gated on
qualified consumer contracts, evidence of reusable gaps, independent validation
and post-v0.10 discovery-capacity admission. Migration composition starts with
existing owners. No specialized leaf, hosted Repo Map qualification, production
migration or JACA adoption is included.

Context capacity and maturity

The corpus remains 45 canonical leaves, 14 stable and 31 provisional.
Descriptions occupy 11,142 UTF-8 bytes under the unchanged 11,507-byte
ceiling. The remaining 365 bytes do not authorize another leaf. Description
bytes, selected guidance and provider overhead are separate measurements;
byte accounting is not a model token-budget guarantee.

No bulk maturity promotion is included. All five CSS qualification debts and
JS-QD-005 retain their existing triggers and maturity implications.

Limitations and compatibility

Desktop Chromium, Firefox and WebKit execution does not qualify the actual
Tauri embedded WebView, native host, sidecars or assistive technology. Consumer
dogfood failures remain consumer observations unless an APGR cause is shown.

The JavaScript process guard proves only its named source files and named
functions. Supported aliases are conservative; arbitrary reflection, computed
calls, newly introduced functions outside that set and general Python
metaprogramming require source review.

Linux packages receive cross-build and archive inspection. Linux runtime
execution has not been established by Darwin qualification work. The Linux
developer qualification gate remains limited by the recorded runner and
Darwin-specific preflight prerequisites.

Report verification establishes artifact-local integrity, not the truth of
recorded operations or external Git relationships. The 128 MiB verification
limit remains unchanged. Accepted historical format behavior is preserved;
historical compatibility does not authorize malformed new operational records.

Public Go package ownership and thin Python/npm adapters remain unchanged.
External consumer adoption and host activation are not established by APGR
qualification.