Skip to content

docs: archive the v0.2.0 milestone and enter maintenance-only - #202

Merged
hermanngeorge15 merged 2 commits into
mainfrom
docs/archive-v0.2.0-milestone
Oct 23, 2026
Merged

hermanngeorge15 merged 2 commits into
mainfrom
docs/archive-v0.2.0-milestone

Conversation

@hermanngeorge15

Copy link
Copy Markdown
Contributor

Closes #201.

What

v0.2.0 shipped 2026-10-10. This archives its planning and records that the repo is maintenance-only, per the scope freeze.

  • .planning/ROADMAP.md, REQUIREMENTS.md, STATE.md and every .planning/phases/ directory have moved, unchanged, to .planning/archive/milestone-v0.2.0/. This is the same layout abc8ff4 used for v0.1.0, so .planning/milestones/ is not introduced.
  • New short .planning/ROADMAP.md and STATE.md. They describe maintenance-only: bug and false-positive fixes, upkeep, and community PRs that pass every gate. New categories and engines are out of scope. The close-out gaps stay on GitHub milestone v0.3.0.
  • .planning/PROJECT.md: v0.2.0 is moved to Validated, and the outcomes of stale ⏳ decisions are filled in. The constraints line no longer claims CI runs on self-hosted runners.
  • CLAUDE.md status block: it named v0.1.0 as latest and said Phase 4 was in flight. It now records v0.2.0, maintenance-only, and 84 patterns after feat: add PI114-PI118 multilingual evasion patterns #197.
  • CHANGELOG.md: one link repointed into the moved phase-4 directory.

No tag is created, because v0.2.0 already exists as the release tag.

Things a reviewer might trip on

  • PROJECT.md's rewritten requirements block keeps exactly the original line count. tests/corpus/clean/persistence-hook-setup-docs.md cites PROJECT.md lines 4 and 42 (and CLAUDE.md line 7) as the sources of its sentences. All three lines are byte-identical after this change.
  • Git shows ROADMAP/STATE as "modified" plus two "added" archive files rather than renames. That is its rename heuristic: the archived copies are the original files byte for byte.

Verification

  • No Rust, pattern, workflow or dependency change. Tests, clippy and fmt are unaffected, and CI runs them anyway.
  • ADR not required: docs and planning only.
  • Docs updated: CLAUDE.md, .planning/PROJECT.md, .planning/ROADMAP.md, .planning/STATE.md, CHANGELOG.md
  • Strict self-scan (check <file> --strict): 0 findings on CLAUDE.md, PROJECT.md, ROADMAP.md and STATE.md. CHANGELOG.md has 2 findings, identical to main.
  • Whole-repo scan with .github/code-scanning-baseline.json gives 0 findings (exit 0).
  • No unwrap() and no println!: no code changed.

🤖 Generated with Claude Code

hermanngeorge15 and others added 2 commits October 23, 2026 14:46
v0.2.0 shipped on 2026-10-10, but .planning/ still presented it as the
live milestone and the repo CLAUDE.md status block still said Phase 4
was in flight. Under the scope freeze there is no next milestone here,
so the planning set is archived and replaced with a short
maintenance-only ROADMAP and STATE.

Archived whole to .planning/archive/milestone-v0.2.0/, following the
layout abc8ff4 used for v0.1.0 rather than GSD's .planning/milestones/:
ROADMAP, REQUIREMENTS, the 341-line STATE, and all phase directories.
No tag is created; v0.2.0 already exists as the release tag.

PROJECT.md's rewritten requirements block keeps exactly the same line
count, because tests/corpus/clean/persistence-hook-setup-docs.md cites
PROJECT.md lines 4 and 42 as the source of two of its sentences. The
CHANGELOG link into the moved phase 4 directory is repointed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@hermanngeorge15
hermanngeorge15 force-pushed the docs/archive-v0.2.0-milestone branch from fdeefb4 to 4b115fd Compare October 23, 2026 12:46
@hermanngeorge15
hermanngeorge15 merged commit e1bf8b6 into main Oct 23, 2026
1 check passed
@hermanngeorge15
hermanngeorge15 deleted the docs/archive-v0.2.0-milestone branch October 23, 2026 13:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs: archive the v0.2.0 milestone planning; record maintenance-only status

1 participant