You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
conventions.md's arch-test block is good, but it lives in a doc while tests/Pest.php in the template is where it must actually exist — verify the template's Pest.php ships those arch tests rather than relying on an agent to copy them (the tests.md bootstrap note implies --init may regenerate a bare file).
/deploy's opcache CLI reset is correctly caveated (CLI vs FPM opcache are separate) but the "canonical server-side reset" it defers to doesn't exist anywhere in the harness — a one-liner in the deploy doc (e.g., a cachetool or FPM-pool reload command) would close the loop.
/research references websearch/webfetch tool names and an @scout builtin — these match current OpenCode builtins, but builtin names are the least stable part of any harness; the research doc is the right place for a "verify tool names against opencode --version docs" note.
commitlint's custom patch type is handled by /release's bump logic — checked, consistent.
eslint JS indentation (tabs, ts=4) vs the JS vim modeline (noet) — consistent. SCSS 2-space — consistent everywhere. No drift found in indentation rules.
conventions.md's arch-test block is good, but it lives in a doc whiletests/Pest.phpin the template is where it must actually exist — verify the template'sPest.phpships those arch tests rather than relying on an agent to copy them (thetests.mdbootstrap note implies--initmay regenerate a bare file)./deploy's opcache CLI reset is correctly caveated (CLI vs FPM opcache are separate) but the "canonical server-side reset" it defers to doesn't exist anywhere in the harness — a one-liner in the deploy doc (e.g., acachetoolor FPM-pool reload command) would close the loop./researchreferenceswebsearch/webfetchtool names and an@scoutbuiltin — these match current OpenCode builtins, but builtin names are the least stable part of any harness; the research doc is the right place for a "verify tool names againstopencode --versiondocs" note.commitlint's custompatchtype is handled by/release's bump logic — checked, consistent.eslintJS indentation (tabs, ts=4) vs the JS vim modeline (noet) — consistent. SCSS 2-space — consistent everywhere. No drift found in indentation rules.