Merge spec/ into specs/: one specs directory for the whole repo

Moves TargetRevenueLicenseConcept.md from the separate singular spec/
directory into specs/ (git mv, preserving history) and updates every live
cross-reference (README, CONTRIBUTING, all specs/*.md, workplans, schema
comments, source docstrings, test file) to the new path.

This resolves the spec/ vs specs/ split that history/260728-SWOT-Assessment.md
flagged as a "perpetual footgun" and recommended deciding on. The historical
record of that split and the recommendation itself are left unedited in
history/ (a dated assessment, not a living document) — only README and TSD
now document the merge as resolved, with a pointer back to that history file
for context.

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

workplans/TREV-WP-0001-license-prior-art-research.md

@@ -16,7 +16,7 @@ state_hub_workstream_id: "6f91cef8-c75c-4955-aaba-0b240390fbe9"
 
 Research prior art and adjacent licensing/monetization concepts to ground an
 initial draft of the Target Revenue Source License (TRSL). The concept is
-already established in `spec/TargetRevenueLicenseConcept.md` and
+already established in `specs/TargetRevenueLicenseConcept.md` and
 `specs/ProductRequirementsDocument.md`; `history/260728-InitialExploration.md`
 already surfaces several reference points (Fair Source, PolyForm
 NonCommercial, Business Source License 1.1, FSL, OSI Open Source Definition,
@@ -64,7 +64,7 @@ licenses. For each, capture: the trigger mechanism (fixed date vs. revenue vs.
 hybrid), the pre-conversion restriction scope, the automatic-conversion legal
 wording, and known criticisms or disputes. Record findings so they can be
 diffed directly against TRSL's Phase/Target/Conversion model in
-`spec/TargetRevenueLicenseConcept.md` §7, §10, §18.
+`specs/TargetRevenueLicenseConcept.md` §7, §10, §18.
 
 **Deliverable path (suggested):** `history/` or `specs/research/TRSL-PriorArt-Survey.md`.
 
@@ -120,7 +120,7 @@ canonical Future Licenses, focusing on: the extent and legal certainty of any
 implied patent grant under MIT, Apache-2.0's explicit patent grant and
 patent-litigation termination clause, and precedent for offering both as
 parallel canonical options (per PRD open question 3 /
-`spec/TargetRevenueLicenseConcept.md` §24.3). Produce a recommendation on
+`specs/TargetRevenueLicenseConcept.md` §24.3). Produce a recommendation on
 whether the TRSL pre-conversion phase itself needs an express patent license
 independent of the eventual Future License choice.
 
@@ -156,7 +156,7 @@ projects and other dual/relicensing projects handle contributor rights.
 Compare against the Developer Certificate of Origin (DCO), and determine
 whether a DCO alone is sufficient or whether TRSL requires a broader inbound
 grant (per `history/260728-InitialExploration.md` §8 and
-`spec/TargetRevenueLicenseConcept.md` §21.4).
+`specs/TargetRevenueLicenseConcept.md` §21.4).
 
 Update `CONTRIBUTING.md` if the recommendation changes interim policy
 (external contributions still blocked for governed Milestone Releases until
@@ -208,11 +208,11 @@ human_accept_required: true
 Using T01–T05, produce `specs/TargetRevenueSourceLicense-Draft.md`: a
 non-binding initial drafting basis (not final legal text) structuring the
 license around the components already identified in
-`spec/TargetRevenueLicenseConcept.md` §21 (permitted noncommercial use,
+`specs/TargetRevenueLicenseConcept.md` §21 (permitted noncommercial use,
 commercial-use restriction, automatic Future License conversion, patent
 treatment, termination and cure, warranty/liability exclusions). Explicitly
 mark every clause requiring specialist legal review before use, per
-`spec/TargetRevenueLicenseConcept.md` §21.5.
+`specs/TargetRevenueLicenseConcept.md` §21.5.
 
 **Human accept gate:** Do not set this task to `done` until a human maintainer
 explicitly accepts the skeleton as adequate briefing material for counsel.

workplans/TREV-WP-0003-normative-core-extraction.md

@@ -18,7 +18,7 @@ Extract stable, versioned normative documents from the exploratory concept
 draft so that schemas (WP-0002), legal skeleton (WP-0001), and later Trust
 Service work share one frozen vocabulary.
 
-**Authority chain:** `spec/TargetRevenueLicenseConcept.md` remains the
+**Authority chain:** `specs/TargetRevenueLicenseConcept.md` remains the
 concept source. Extracted docs under `specs/` become the day-to-day
 normative references for implementers; they must not invent divergent
 meanings for core terms (PRD §6.1). Working defaults that affect required
@@ -106,7 +106,7 @@ Updated `schemas/ledger_entry.schema.json`, `src/target_revenue/fold.py`,
 `specs/TargetLedgerSpecification.md` §2/§6, `specs/TechnicalSpecificationDocument.md`
 §3.2, and `specs/ProductRequirementsDocument.md` FR-5. Added dedicated test
 coverage (`tests/test_ledger_fold.py`) for both new types plus a regression
-test confirming the old unsplit type name is now rejected. `spec/TargetRevenueLicenseConcept.md`
+test confirming the old unsplit type name is now rejected. `specs/TargetRevenueLicenseConcept.md`
 §17 was left unedited — its entry-type list is explicitly non-exhaustive
 ("may include"), so the split specializes rather than contradicts it.
 
@@ -204,7 +204,7 @@ accept):
       `product-ideation` and `general-consulting` as not yet fixture-backed.
 - [ ] Cross-links (T05) — confirm PRD §6.1/§6.2, TSD §0/§1.1, README, and
       CONTRIBUTING.md all point at the new extracts without contradicting
-      `spec/TargetRevenueLicenseConcept.md` as ultimate authority.
+      `specs/TargetRevenueLicenseConcept.md` as ultimate authority.
 - [ ] No open question (concept §24) is answered by omission — each extract
       either cites a working default explicitly or states the item remains
       open.