[evangress]

The repo's community profile sits at 62%. Description, README, CONTRIBUTING, LICENSE (Apache-2.0) and SECURITY.md are already in place; this adds the three missing items.

Item	Before	After
Code of conduct	❌	CODE_OF_CONDUCT.md
Issue templates	❌	.github/ISSUE_TEMPLATE/ (bug, feature, config)
Pull request template	❌	.github/PULL_REQUEST_TEMPLATE.md

Code of conduct

Contributor Covenant 2.1, verbatim, with scope and enforcement pointed at this repo.

One thing to check before merging: the enforcement contact routes to GitHub's private reporting form, because that's the only private channel this project currently has. It works, and it avoids publishing a personal email address in a public repo — but if you'd rather have a dedicated conduct address, that line is the one to change. Reporters are told to mark conduct reports clearly so they aren't triaged as vulnerabilities.

A short note also keeps expectations honest about a spare-time project having no moderation staff — the same caveat SECURITY.md already makes for vulnerability response.

Issue forms

Written for this project rather than filled in from a generic template:

• The bug form leads with "did this lose or change your writing?" CONTRIBUTING says data-safety bugs outrank everything, so the form should sort for that before it asks anything else — including a nudge not to overwrite the affected file.
• It asks about the folder — Obsidian vault, synced by iCloud/OneDrive/Dropbox, open in another editor, on a network share. Toril is explicitly built to coexist with other writers, and that context explains most behavior that otherwise looks random.
• It asks which format, since .md and .html go through separate serializers.
• The feature form states the already-decided noes up front (multi-format structured editing, a pure-Rust rewrite — CLAUDE.md §12) so nobody writes a careful proposal for something that was never on the table, and routes open-ended ideas to Discussions instead.

config.yml keeps blank issues enabled and adds contact links for security reporting, Discussions, and the contributing guide.

Pull request template

Deliberately doesn't ask for test output — CI now runs typecheck, tests, build and the Rust crates on Ubuntu and Windows. It asks for what CI can't produce:

• what was verified in a live window, and what was left unverified (framed as useful information, not an admission)
• data-safety impact, and whether the §5 command contract changed
• whether CLAUDE.md and CHANGELOG need updating

Kept short on purpose: a long PR template gets deleted wholesale.

Verification

Both issue forms validated against GitHub's schema — YAML parses, block types are legal, every non-markdown block has an id, and validations sits as a sibling of attributes rather than nested inside it. That last check caught a real defect in the feature form before it shipped.

🤖 Generated with Claude Code