Move BCP 14 boilerplate to project level; add MIT license

The citation paragraph did no enforcement work inside spec files (the
tool binds keyword semantics mechanically) and cost agent context on
every spec read. It now lives once in the README; REQ-001.1.5 revised
in place to mandate the project-level placement, and the conformance
doc states the divergence and its reasoning.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: tylerwillis

.2119/verdicts/REQ-001.3.1--26558ec45ce4.json

@@ -0,0 +1,8 @@
+{
+  "reviewId": "REQ-001.3.1--9c8825a17d16",
+  "requirementId": "REQ-001.3.1",
+  "hash": "9c8825a17d16",
+  "verdict": "pass",
+  "summary": "Full git history (d99164a..HEAD) plus working tree shows no ID renumbered or reused: all changes are appends; the one in-place edit (REQ-001.1.5 boilerplate-location flip) revises the same requirement's subject, keeps its number, and every external reference (docs/rfc-conformance.md, verdicts, annotations) resolves to the current text.",
+  "timestamp": "2026-07-09T04:03:48.459Z"
+}

.2119/verdicts/REQ-001.3.1--9c8825a17d16.json

@@ -0,0 +1,8 @@
+{
+  "reviewId": "REQ-001.3.2--9510ec1e81b2",
+  "requirementId": "REQ-001.3.2",
+  "hash": "9510ec1e81b2",
+  "verdict": "pass",
+  "summary": "Every addition in history was appended with the next sequential number (REQ-001.1.5-6 and REQ-001.2.5-6 at section ends, REQ-003.5 as a new section after .4); all four specs currently number items 1..N with no gaps or out-of-order insertions.",
+  "timestamp": "2026-07-09T04:04:01.014Z"
+}

.2119/verdicts/REQ-001.3.2--0c6302266a04.json

@@ -0,0 +1,8 @@
+{
+  "reviewId": "REQ-001.3.3--81973ae43c0a",
+  "requirementId": "REQ-001.3.3",
+  "hash": "81973ae43c0a",
+  "verdict": "pass",
+  "summary": "No requirement has ever been removed (specs history is insertion-only, 0 deleted items), so no tombstone is required; every ID ever published still carries a live statement and 2119 cover confirms zero dangling test/verdict references.",
+  "timestamp": "2026-07-09T04:04:01.108Z"
+}

.2119/verdicts/REQ-001.3.2--9510ec1e81b2.json

@@ -0,0 +1,8 @@
+{
+  "reviewId": "REQ-002.3.2--20b87ce578cb",
+  "requirementId": "REQ-002.3.2",
+  "hash": "20b87ce578cb",
+  "verdict": "pass",
+  "summary": "Benchmarked: synthetic repo with 100 specs (500 MUSTs) and 2000 annotated test files runs 'check' in ~0.30s wall (3 runs, incl. SHA-256 review-hash computation for 500 review targets); implementation is a single synchronous fs walk + picomatch + regex parsing with no network or subprocess calls.",
+  "timestamp": "2026-07-09T04:04:01.204Z"
+}

.2119/verdicts/REQ-001.3.3--81973ae43c0a.json

@@ -0,0 +1,8 @@
+{
+  "reviewId": "REQ-003.2.2--f3e8da349382",
+  "requirementId": "REQ-003.2.2",
+  "hash": "f3e8da349382",
+  "verdict": "pass",
+  "summary": "writeVerdict emits pretty-printed JSON to .2119/verdicts/, init.ts gitignores only .2119/reviews/ (explicit comment excluding verdicts, REQ-003.2.2), repo .gitignore matches, and git check-ignore confirms verdict files are tracked (they appear as tracked D/M entries in status).",
+  "timestamp": "2026-07-09T04:04:01.296Z"
+}