Add a new AccessFlow engine plugin under engines/ / — scaffold the Maven project and QueryEngine SPI implementation, pin the shaded JAR in connectors/ /connector.json, wire DbType + migration + credential gates + i18n + frontend registration + docs/website, and open a PR. Trigger when the user says "add a engine"…
Prepare an AccessFlow release — verify every roadmap item is closed and documented, regenerate website screenshots, mark the milestone released in docs/website/README, then open a chore PR. Refuses to proceed when anything is missing. Trigger when the user says "prepare release vX.Y", "release prep for X.Y", or passes…
Review an existing AccessFlow pull request — check the head out into an isolated worktree, fan out the read-only agents (change summary, conventions, security, frontend, cross-cutting drift), explain what the PR actually does, then merge the findings into one numbered list and let you pick which ones to keep. Never…
Run the SQL-gate attack suite, confirm every hostile query is denied with a named rule, and report coverage gaps. Use after editing src/policy/gate.ts or the demo policy.