v1.0.0 — CodeCrew 1.0, protocol 1.0

The first stable release of the gh extension and of the protocol it
implements: SPEC 1.0. Everything below merged through the protocol — a
task, a plan, a PR, the reviewer seat's approval, task finish — and is
recorded on the linked issues.

The protocol has a version, and the CLI checks it

• codecrew version prints both: v1.0.0 (protocol 1.0). The pointer's
  codecrew: field is checked by every verb that reads it — another
  protocol major refuses PROTOCOL_MISMATCH; "0.1" (the pre-1.0 form of
  these same conventions) and a missing field proceed with a note. init
  scaffolds codecrew: "1.0". Decided at a recorded gate. (#114, PR #127)
• SPEC is "Version 1.0" — no longer draft — and §10 states what 1.0
  promises (below).

Contracts extend without forking

• roles/<role>.local.md — a project's own instructions for a role,
  loaded after the contract: hub contract, hub extension, spoke extension.
  roles show <role> prints the composition a dispatched session loads;
  status's drift report never sees extensions. The first extension is
  this hub's editorial voice for outward-facing writing. (#122, PR #123)

The record gathers completely

• milestone close gathers one record per labelled paragraph: qualified
  labels (**Decision (…):**) are captured verbatim, a record written
  after other text in the same comment is found, CRLF comments are
  handled, and each task's PRs are listed as summary pointers. Proven on
  the real M5 comment corpus, committed as a regression test: 3 records
  gathered before, 7 after. PR bodies are never gathered (SPEC §4).
  (#113, PR #126)

A close leaves the repo clean

• task finish deletes the head branch it merged. milestone close
  sweeps the tasks' branches after every gate has passed — deleting only
  a branch whose PR merged and still sits at the merged commit, or one
  with no open PR and nothing beyond the default branch; never a fork's
  head or the default branch; reporting everything else. status notes
  when the repo does not delete branches on merge. (#129, PR #130)

Launch readiness

• A scaffold that stands alone: every reference init writes resolves
  from an adopter's repo (upstream URLs; the token script installs with one
  line). --help exits 0 on every verb and is resolved before any verb
  runs. SPEC promises only what ships: no PR-body deviation check; github.com
  only (GitHub Enterprise Server is a non-goal for now). The quickstart
  names pull-request CI as a prerequisite. CONTRIBUTING, SECURITY and a
  teardown inventory. (#131, PR #135)

Docs and branding

• A landing-page README in the house voice, with four illustrations
  (#111, PR #124); the former README is docs/introduction.md — the map,
  what exists, and the catalogue of all twenty-one refusal codes by verb
  (#112, PR #125); the CodeCrew logo and a mark adopters may use for their
  own crew Apps (#110, PR #121); the Copilot coexistence statement (#104,
  PR #105); the M5 milestone document (#106, PR #107).

What 1.0 promises

Within a major release series of the CLI: verb names and their flags are
additive — nothing is renamed or removed; a refusal code's meaning is
stable — codes may be added in a minor, never repurposed, removed only in
a major; the refused[CODE]: detail line and the version output are
stable shapes, other human-facing text is not; pointer fields are
additive; the embedded role contracts may change in a minor, with the
drift report and roles diff as the mechanism. A protocol change that
invalidates existing pointers or recorded comments is a protocol major,
and the CLI that implements it refuses the old pointer.

Full Changelog: v0.5.0...v1.0.0