chore: build in public, not open to contribution

[anusbutt]

Repositions the repo as a personal product built in public rather than a community project.

What & why

The repo was carrying a full open-source community-health set — contribution guide, code of conduct, issue templates, PR template. That advertises a contribution process that isn't real: it invites people to file issues and open PRs against something with no roadmap, no support commitment, and copy tied to one real outreach operation. Better to say so plainly than to leave the invitation standing.

Removed:

• CONTRIBUTING.md
• CODE_OF_CONDUCT.md
• .github/PULL_REQUEST_TEMPLATE.md
• .github/ISSUE_TEMPLATE/bug_report.md, feature_request.md

Kept deliberately:

Kept	Why
LICENSE (MIT)	Not inviting contributions is a different decision from withdrawing reuse rights. The code has already been published under MIT, so anyone holding a copy keeps those rights regardless of what the repo says next — removing the file would only split the history into MIT and non-MIT halves without retracting anything.
SECURITY.md	Reworded for a solo maintainer with issues closed. This tool holds mail credentials and sends on my behalf; a private channel for a real flaw is worth keeping open, and it's now the only open channel.
.github/workflows/ci.yml	My own quality gate, not a contributor-facing one.

The one judgment call worth reviewing

CONTRIBUTING.md was not purely process. It also held the numbered guarantees mapped to the constitution principles, the "profiles are content, not capability" rules, and the trust-boundary / no-secrets / no-prospect-data conventions — and the README links to it as the authoritative statement of the safety guarantees.

Deleting it outright would have thrown away the most useful writing in the repo and left a dangling README link. So that substance moved to docs/design-guarantees.md, reframed as what this build holds itself to rather than what a contributor must preserve. Contribution framing ("will not be merged", "open an issue first", the PR checklist) is gone; the engineering content is intact.

If you'd rather that content simply disappear too, say so and I'll drop the file and inline a short version in the README instead.

Also

• README gains a Project status section: issues closed, PRs not accepted, no roadmap or stability promise, fork it if it's useful. The License section now spells out what MIT does and does not oblige me to do.
• SECURITY.md no longer says "do not open a public issue" (there are none) and drops the corporate "we".

How it was verified

• pytest -q → 593 passed.
• All README table-of-contents anchors resolve, including the new section.
• Every relative link checked: docs/design-guarantees.md, SECURITY.md, LICENSE all exist.
• Swept the tree for dangling references to the five deleted files — none remain in any tracked Markdown, TOML, or workflow file.

Companion changes outside this PR

Two things live in GitHub settings rather than the tree, done alongside this:

• Issues disabled — the main signal that a repo takes outside input.
• Repo description corrected. It still read "(email, or assisted Messenger)", which has been wrong since feature 008 removed the Messenger channel.

Wiki and Projects were left enabled, per your call.

🤖 Generated with Claude Code