Repository navigation
v1.2.0
·
81 commits
to main
since this release
Immutable
release. Only release title and notes can be modified.
The pull-request pipeline is complete, and the stacks gain the ported rule set. Three new reusable
workflows sit behind optional setup questions: a DeepSeek review of each pull request, a deploy on
merge through your webhook, and the strip of agent config from the production branch. Their
callers still hold the release placeholder, so setup keeps them back until the plugin releases
that pin them to this commit. The Hono, Next.js and FastAPI stacks gain the opt-in payload
contract, and every stack gains the missing rules, anti-patterns, checks and a CODEOWNERS starter.
Reusable workflows and actions
Added
deepseek-review.ymlandactions/deepseek-review: an AI review of a pull request's diff by
DeepSeek, posted as one comment that later runs update. It reads the pull request over the
GitHub API and checks nothing out, so no pull-request code runs; it skips, and passes, without
theDEEPSEEK_API_KEYsecret, for a fork's pull request, a draft or a closed one. Lockfiles and
yourexcludepatterns are left out, the diff is capped atmax-diff-bytes(100,000) and the
answer atmax-tokens(16,384), so a review costs a cent or two and at most about ten US cents;
each comment shows the tokens it used. Mentions in the answer are quietened.deploy-webhook.ymlandactions/deploy-webhook: when a pull request is merged into the
production branch, POST toDEPLOY_WEBHOOK_URLwith agent-deploy'strigger-deploy.sh(the
same file, kept identical by a test): https only, a 3xx or 4xx fails the job, a busy platform is
asked again, and the URL is never printed. Withdocs-repositoryandDOCS_DISPATCH_TOKENit
then sendsapp-deployed, which agent-docs-nextra's changelog answers.strip-ai.yml: runsactions/strip-aiafter a merge into the production branch with a checkout
that keeps no token; git gets the job's token from a credential helper in that step's
environment.- Every new reusable workflow takes
runs-on(empty usesCI_RUNNER, thenubuntu-latest) and
timeout-minutes, and every input is optional.
Changed
actions/strip-ai: its README and header point at the reusable workflow and a checkout with
persist-credentials: false. The action itself is unchanged.scripts/workflow-policy.pyallowsissue_commentin one place only: a template's
deepseek-review.ymlfor/ask-deepseek, and only in its safe shape (types: [created], a job
that calls this repository'sdeepseek-review.ymlwithcontents: readand
pull-requests: write, anif:that requires a comment on a pull request by an OWNER, MEMBER or
COLLABORATOR, and a called workflow that checks nothing out). ADR 0004 records why.scripts/version-sync.mjsaccepts a caller pinned to the all-zero placeholder when its comment
names the coming release (or, in the release pull request, the release being cut), and asks for
a changelog entry when any reusable workflow changes.scripts/catalog.mjslists every workflow a plugin's setup installs as a component, with a docs
page, in the README catalogs.
agent-core 1.1.0
Changed
.claude/CI-RUNNERS.example.mdnames the workflows the kit installs on each runner pool, and
its budget test opens a throwaway pull request instead of aworkflow_dispatchworkflow, which
the kit's CI policy does not use.- The README catalog lists the CodeQL, dependency-review and workflows-lint workflows, each with a
docs page. /agent-core:reviewruns the installed i18n guard, SEO validator and accessibility audit on the
parts of the diff they own, starts with the cheap scans (staged secrets, a real env file, eval and
raw-HTML sinks, secret-shaped assignments), reports the gates it ran, and ends by offering the
fixes./agent-core:resolve-pr-reviewreads the review threads, skips resolved ones, shows a fix plan
before a larger change, and resolves each thread it answered, so the readiness check can pass./agent-core:merge-prnever uses--auto, and deletes aninternal/*head only once the pull
request readsMERGED./agent-core:create-prrefuses a protected branch, runs the gates first,
asks once for what is missing, and redrafts on request./agent-core:planadds UNKNOWNS, timed
tasks, rated risks, phases past 50 tasks and per-stack layers./agent-core:promotecompares an Alembic head (not a count) and lists the browser pass it means.DATABASE.example.mdsays which query tools run the SQL they are given and when to widen the
write guard; the working agreements add three lines (a green suite and an untested transport,
another session's authorisation, the zsh array trap).
Added
/agent-core:check-fix: runs the repo's gates, fixes each failure at its cause (format and lint
twice, types, build, tests in CI's environment, schema and stack checks) and re-runs until green;
it never silences a finding and never commits.- The security guard checks web response headers where a repo renders pages: the header set, an
unjustified'unsafe-inline'or'unsafe-eval', a nonce CSP frozen into static config, raw HTML
without a safety note, and the payload contract where a repo adopted it. OPERATIONS.example.mdgains how the guards fail (closed, one deadline, the Linux argument cap)
and why the shell cannot rewrite them, and sections on the unlock, the staged secret scan, server
access with a break-glass order, and client IP behind a CDN or proxy.
agent-ai-fastapi 1.2.0
Added
- Setup question
deepseek-review(recommended no):.github/workflows/deepseek-review.yml, a
DeepSeek review of each pull request with notes about a FastAPI service, leaving out Alembic
revisions. Needs theDEEPSEEK_API_KEYsecret. Held until a release pins it. - A
.github/CODEOWNERSstarter, seeded once: CI, the guardrails, startup, settings and the
database. - The payload contract, an opt-in setup answer (
payload-encryption): a Python implementation in
src/app/core/payload/(the same envelope, AAD and freshness as the TypeScript stacks, key rings,
the switch, and a plain ASGI middleware that replays the opened body and never invents a
disconnect) with tests at 100% branch coverage, including the shared test vectors. It needs the
cryptographypackage.
Changed
- The starter adds §P; the review checklist and the reviewer add input size caps, corpus changes,
pipeline data integrity and the ways around theAnyban.
agent-be-hono 1.2.0
Added
- Setup question
deepseek-review(recommended no):.github/workflows/deepseek-review.yml, a
DeepSeek review of each pull request with notes about a Hono + Drizzle API, leaving out
drizzle-kit migrations and the exported spec. Needs theDEEPSEEK_API_KEYsecret. Held until a
release pins it. - A
.github/CODEOWNERSstarter, seeded once: CI, the guardrails, startup, env and the database. - The payload contract, an opt-in setup answer (
payload-encryption): a reference implementation
insrc/lib/payload/(AES-256-GCM envelopes bound to method, route pattern, status and key id,
a two-minute freshness window, pre-shared key rings with_NEXTrotation, browser key agreement,
the committed strict/off switch refused in production) and a Hono middleware, with tests at 100%;
the endpoint registry andgenerate:endpoints;check:endpoints(registry drift, reasons for
every exemption, route literals, the committed switch, peer spec and policy parity) and
check:crypto-interop(shared known-answer vectors and peers checked out beside the repo);
.claude/PAYLOAD-CONTRACT.mdand a rule that loads with the transport. Key material stays out
of the repo. check:openapiandspec:export: the document the app declares builds, describes a route, and
equals the committedopenapi.json.check:dockerfile: the image builds what the gate validated.- Anti-patterns: a cookie cache that outlives revocation, account endpoints the client cannot
reach, passkey cancellation and user verification, a plugin list option that replaces its
defaults, and a gateway cancel whose result is not the state.
Changed
- The starters add §P (the payload contract, where adopted), a transactional-email section and a
knownzod-openapityping trap; the review checklist adds per-route guards; the Hono rule adds a
switch for the public spec routes.
agent-deploy 1.1.1
Added
- Setup question
deploy-on-merge(recommended no):.github/workflows/deploy.ymldeploys
through your webhook when a pull request is merged intoprod, one at a time and never
cancelled. Needs theDEPLOY_WEBHOOK_URLsecret; fails, rather than skipping, without it. - Setup question
strip-ai(recommended no):.github/workflows/strip-ai.ymlstrips the agent
config fromprodafter each merge, merges back intodevand verifies both. - Both callers are held until a release pins them.
Changed
/agent-deploy:promote-deploybuilds a static site before uploading it, confirms the content
changed after, and walks the browser pass and a third-party sign-in on the live site.
agent-docs-nextra 1.1.1
Added
- Setup question
deepseek-review(recommended no):.github/workflows/deepseek-review.yml, a
DeepSeek review of each pull request with notes about a Nextra site, leaving out the generated
changelog and API reference. Needs theDEEPSEEK_API_KEYsecret. Held until a release pins it. - A
.github/CODEOWNERSstarter, seeded once: CI, the deploy target, the generators and the
guardrails.
Changed
- The security guard checks third-party embeds and
javascript:/data:URLs in MDX; the SEO
validator gains a private-site mode; the starter says the reference generator needs the
documented app checked out beside the docs repo.
agent-fe-nextjs 1.2.0
Added
- Setup question
deepseek-review(recommended no):.github/workflows/deepseek-review.yml, a
DeepSeek review of each pull request with notes about a Next.js app, leaving out the generated
API client and the translation catalogues. Needs theDEEPSEEK_API_KEYsecret. Held until a
release pins it. - The payload contract, an opt-in setup answer (
payload-encryption): the same reference cipher as
the backend insrc/lib/payload/, a browser transport (one agreed key per tab, a handshake, a
refusal of plaintext successes on sealed routes) and a server bridge between the browser hop and
the backend hop, with tests at 100%; the endpoint registry,generate:endpoints,
check:endpoints(including rawfetchoutside the transport and unregistered generated-client
URLs) andcheck:crypto-interop; the contract document and its rule. check:dockerfile, andcheck:skeleton-pairsin the skeletons module: a skeleton a screen
renders is measured in the harness or listed with a reason.check:i18nfails on a literal key a
scoped translator uses that its namespace does not hold;check:socflags a render loop in a
component.- Anti-patterns: a cookie cache that outlives revocation, gated account endpoints, passkey quirks,
a prefixedbackdrop-filterleft alone by the CSS pipeline, and a cropper that letterboxes.
Changed
- The seeded
.github/CODEOWNERSstarter explains itself in the same words as the other stacks'
and names the setup lock. - The starters add §M (session and authorization boundary), §N (data surfaces) and §P (the payload
contract), and SSOT §5.2, §5.4 and §5.5 (service-hook conventions, fixtures before the backend,
three states). The reviewer checks them; the SEO validator gains an app-behind-sign-in mode;
plan-fullstackcarries authorization, states and fixtures;serena-errors.mdstarts with the
known tool failures; the UI conventions add parity across sibling apps.
agent-fe-nextjs-static 1.1.1
Added
- Setup question
react-doctor(recommended no):.github/workflows/react-doctor.ymland
doctor.config.json, advisory React Doctor comments and a commit status on pull requests. - Setup question
deepseek-review(recommended no):.github/workflows/deepseek-review.yml, a
DeepSeek review of each pull request with notes about a static export. Needs the
DEEPSEEK_API_KEYsecret. Held until a release pins it. - A
.github/CODEOWNERSstarter, seeded once: CI, the headers, the build config, the budgets and
the guardrails. - Anti-pattern: a prefixed
backdrop-filterthe CSS pipeline keeps while dropping the standard
one.
agent-fe-threejs 1.0.2
Changed
- The 3D rule warns about unscoped
npxpackage names in skills and checks the renderer's React
peer range before a React upgrade.
Each plugin is tagged <plugin>--v<version>. The full history is in CHANGELOG.md.