Implement WP-0015-T02: extract policy/profile spec files

specs/policies/linear-longstop-v0.md extracted from
OpenQuestions-WorkingDefaults.md Q7's prose, with policy_id/title
frontmatter -- Q7 now records only the adoption decision, pointing at
this file for the formula itself.

Six specs/profiles/*.md files extracted from
CanonicalMonetizationProfiles.md's per-profile sections (#1-6), each
with extension_id/title frontmatter matching the ids already used in
real Phase Manifests. CanonicalMonetizationProfiles.md keeps the
cross-profile summary and non-goals sections, now pointing at the
extracted files instead of containing their content.

DevelopmentEffortCalculatorConcept.md gets calculator_id/revision/title
frontmatter for consistency, no move (already conformed as one file per
model). Checked for stale cross-references before editing -- nothing
in the repo links to the removed section anchors.

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

specs/profiles/development-license.md

@@ -0,0 +1,23 @@
+---
+extension_id: trsl:extension:development-license@1.0
+title: Development License
+---
+
+# Development License
+
+**What the payer receives:** commercial-use rights and early commercial
+access to the protected, pre-conversion Milestone Release — the direct
+purchase of a Commercial Entitlement under the Commercial Use Agreement.
+
+**Worked narrative:** a company wants to run the governed software
+commercially before its Conversion Event. It pays a fixed development fee
+under the CUA's Exhibit A. Once the payment settles (processor
+confirmation, not invoice date — Rule 4), 100% of the net amount (after
+tax, refunds, chargebacks) becomes Development Credit for the Phase named
+in the CUA. This is the simplest and most direct profile: the payment's
+entire purpose is buying into the protected development, so its entire
+net value counts.
+
+**Default `development_allocation`:** 100%.
+
+**Fixture:** `examples/phase-001/extensions/development-license.json`.