Feature PRs have arrived with a self-ticked "maintainer approved" box on
issues the maintainer never answered, and with large AI-generated diffs
the author could not stand behind. Make approval a label only the
maintainer can add, and state what an AI-assisted contribution owes
reviewers: an author who has read the diff, answers reviews personally,
does not split changes to dodge the size guideline, and makes only
checkable claims.
Readers in these languages had only the English README. The language
bar follows the CONTRIBUTING order by language code, and the release
skill now lists the new files so their Latest callout is updated with
the others.
Add a shared instruction kernel and byte-budgeted topic router so agents load only task-relevant repository guidance. Wire drift checks into local and CI workflows and point project skills at the routed topics.
An ordering chosen by hand between Simplified and Traditional Chinese
invites argument. Sorting by code needs no judgement, and README-zh.md
becomes README-zh-CN.md so neither file reads as the default Chinese.
Restructure contribution guidelines to clarify expectations:
- Issues are the primary entry point for all contributions
- PRs are for small fixes; features require issue + proposal first
- Implementation is handled by maintainer after proposal approval
- All development must use devcontainer (make devc)
Add PR template to surface checklist when contributors open PRs.
Add proposals/ directory with TEMPLATE.md for feature proposals.