chore(repo): restore registry drift check and refresh AGENTS docs

[marcusrbrown]

Summary

• restore the CI registry drift step to run bun run registry:drift, keeping generated-output drift detection separate from source registry validation
• refresh the root AGENTS.md snapshot for the released v2.7.0 repo state, including plugin export shape, command layout, hook naming, and current test counts
• refresh docs/AGENTS.md for Astro 6 and shared frontmatter parsing, and pin the workflow/package registry command contract in unit tests

Testing

• bun test tests/unit/plugin.test.ts
• bun run typecheck
• bun run registry:validate
• bun run registry:drift
• bun run docs:build

[fro-bot]

Verdict: PASS

Clean PR that restores a CI registry drift check via an npm script, pins the contract in unit tests, and refreshes AGENTS.md documentation to match current codebase state.

Blocking issues

None

Non-blocking concerns

• Test naming: The extended CI smoke test now asserts both plugin loading and registry:drift presence, but the test name 'CI smoke test loads the default plugin export' doesn't reflect the added concern. Consider renaming to something like 'CI workflow script contract' or splitting into a dedicated test. Pure naming nit — not blocking.
• Test brittleness: The package exposes distinct registry validation and drift commands test pins exact script values (e.g., 'bun scripts/build-registry.ts --validate-only'). This is intentional contract testing, but anyone changing those scripts will need to update both the test and CI simultaneously. Acceptable tradeoff given the PR's stated goal of keeping these in sync.

Missing tests

None — the PR adds the right tests for the new contract.

Risk assessment

LOW — No production code changes. The workflow now calls bun run registry:drift instead of bun scripts/generate-registry.ts --check, which resolves to the identical command via the new package.json script. The tests validate this contract. Documentation updates are accuracy corrections that bring AGENTS.md in line with current source (verified: hook name is experimental.chat.system.transform, SystematicPlugin is a const, 15 unit test files exist, commands/ dir is removed, SKILL_FRONTMATTER_FIELDS exists at line 48). Zero blast radius.

---

Run Summary

Field	Value
Event	pull_request
Repository	marcusrbrown/systematic
Run ID	25200900297
Cache	hit
Session	ses_21e68af22ffev5LznFlvoM7v19

[marcusrbrown]

Test naming: The extended CI smoke test now asserts both plugin loading and registry:drift presence, but the test name 'CI smoke test loads the default plugin export' doesn't reflect the added concern.

Addressed: renamed the test to CI smoke test validates the workflow plugin export and registry drift contract so the name matches the assertions it now covers.

[fro-bot]

Verdict: PASS

Previous non-blocking concern addressed: the test is now renamed to 'CI smoke test validates the workflow plugin export and registry drift contract' which accurately describes its assertions. No new issues introduced in the follow-up commit.

Blocking issues

None

Non-blocking concerns

None — the prior naming concern has been resolved.

Missing tests

None

Risk assessment

LOW — Identical to prior assessment. No production code changes, CI script refactoring documented and tested, AGENTS.md refreshed to match current source state.

---

Run Summary

Field	Value
Event	pull_request
Repository	marcusrbrown/systematic
Run ID	25201130469
Cache	hit
Session	ses_21e68af22ffev5LznFlvoM7v19