docs(readme): mark project as unmaintained

[MacAttak]

Summary

• Adds a prominent "Project status: unmaintained" notice near the top of the README, explaining that active development has stopped while leaving the door open to minor fixes or a future revival.
• Rewrites the Contributing section to set realistic expectations: issues/PRs may not be reviewed, forks are welcome under MIT.

Notes

• No code changes — README-only.
• The repo is not being archived, so minor edits remain possible without an unarchive round-trip.

Test plan

• README renders correctly on GitHub (notice blockquote, horizontal rules, Contributing section)
• No broken links introduced

🤖 Generated with Claude Code

[github-actions]

Eval Smoke Results

✅ Smoke evals clean — 0 regressions, 3 improvements

Eval	Pass Rate	Duration	Tokens (input+output)	Verdict
grader-function-tests	1.00 (+0.00)	410ms (-1084ms)	0 (+0)	improved
structural-handoff-template	1.00 (+0.00)	30ms (-13ms)	0 (+0)	improved
structural-skill-validation	1.00 (+0.00)	4631ms (+170ms)	0 (+0)	ok
structural-state-enforcement	1.00 (+0.00)	81ms (-10ms)	0 (+0)	improved
workflow-yaml-validation	1.00 (+0.00)	1328ms (+28ms)	0 (+0)	ok

_{Posted by Specwright eval-smoke workflow. This comment is updated on each push.}

[claude]

Review: docs(readme): mark project as unmaintained

Overall: approve with one gap to address before merge.

This is a clean, honest communication of the project's current state. The notice is well-placed, the wording is clear without being abrupt, and the decision not to archive (so minor fixes can still land without the unarchive round-trip) is sensible.

---

What works well

• The blockquote notice is immediately visible and explains why development stopped, not just that it did — that's genuinely useful for anyone evaluating a fork.
• Leaving core/ as the recommended entry point for forks is accurate (the directory exists and contains the most transferable material: skills, protocols, agents).
• Keeping the repo unarchived while setting expectations explicitly is the right call for a reference project.

---

Gap: CONTRIBUTING.md is now contradictory

The README's Contributing section has been updated, but the top-level CONTRIBUTING.md still actively invites people to open bug reports, feature requests, and pull requests — complete with issue template links and a full development workflow. A user who lands on the repo root and clicks the file (or follows the GitHub "Contributing" link that many clients surface automatically) will get the old, actively-maintained story.

Minimum fix: add the same unmaintained notice at the top of CONTRIBUTING.md, or replace the body with a short redirect to the README notice.

---

Minor suggestions (non-blocking)

• No timestamp on the notice. Future readers — and anyone who revisits the repo in a year — won't know when "no longer under active development" began. Adding a rough month/quarter (as of early 2026 or similar) gives that anchor without over-committing.
• Test plan checkboxes are unchecked. If rendering has been verified locally, checking them before merge keeps the PR record tidy (no functional impact).

---

The CONTRIBUTING.md gap is the only change I'd ask for before merge. Everything else is solid.

[claude]

The README Contributing section is now updated, but CONTRIBUTING.md at the repo root still reads as if the project is actively maintained — it opens with "Thanks for your interest in contributing!" and provides issue template links for bug reports and feature requests. GitHub surfaces that file automatically in several places (PR creation flow, repo sidebar). A visitor who follows that path will get the old, contradictory story.

Suggest either prepending the same unmaintained notice to CONTRIBUTING.md, or replacing its body with a short redirect:

Suggested change

	The project is **unmaintained** (see the notice at the top of this README). Issues and pull requests may not be reviewed or merged. Forks are welcome — the MIT license places no restrictions on adapting the code for your own use.
	The project is **unmaintained**. See the [Project status notice](README.md#project-status-unmaintained) at the top of the README. Issues and pull requests may not be reviewed or merged. Forks are welcome under the MIT license.

(Replace line 426 in the README is fine as-is; this suggestion is for CONTRIBUTING.md — flagging here for visibility.)