docs(6207): migrations 0079, 0082, 0087, 0104, 0111, 0112, 0116-0118 drop milestone and record citations

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

alembic/versions/0079_code_shapes_ledger.py

@@ -1,13 +1,13 @@
-"""The shape ledger: code_shapes (#2787, milestone 294)
+"""The shape ledger: code_shapes
 
 Revision ID: 0079
 Revises: 0078
 Create Date: 2026-08-19
 
-The accounting half of the pattern system (governing note 2786): the snippet
+The accounting half of the pattern system: the snippet
 library records canon (small); this table accounts for EVERY shape the
 coverage extractor finds in a bound repo (total). Rows arrive `unclassified`
-from the coverage sync (step 2) and gain judgments — canonical / instance /
+from the coverage sync and gain judgments — canonical / instance /
 variant / exempt — from audits, hooks, and the mechanical proposer.
 Unclassified IS the todo list.
 """

alembic/versions/0082_repo_binding_ref.py

@@ -1,13 +1,13 @@
-"""Per-binding ref — the branch a project's ledger follows (#2873, milestone 294)
+"""Per-binding ref — the branch a project's ledger follows
 
 Revision ID: 0082
 Revises: 0081
 Create Date: 2026-08-21
 
-A repo binding used to imply the repo's default branch; the shape ledger
+Without a ref, a repo binding implies the repo's default branch, so the shape
-therefore only saw work after a merge to main, while the operator's work
+ledger only sees work after a merge — while a project may do its work on a
-lands on dev (rule 1). `ref` names the branch the coverage refresh reads —
+dev branch. `ref` names the branch the coverage refresh reads; NULL means the
-NULL keeps today's behaviour (the forge's default branch).
+forge's default branch.
 """
 import sqlalchemy as sa
 from alembic import op

alembic/versions/0087_canonical_systems.py

@@ -1,12 +1,12 @@
 """canonical_systems — the global area vocabulary, promoted from a constant
-to a table (milestone 307 step 1, decision note 3026)
+to a table
 
 Revision ID: 0087
 Revises: 0086
 Create Date: 2026-08-26
 
 The eight standard area names already existed as `STANDARD_SYSTEMS`, a tuple in
-services/systems.py that milestone 297 seeds into a project at inception. A
+services/systems.py that is seeded into a project at inception. A
 constant cannot be referenced: a rule that applies across projects has nothing
 to point at, because `systems.project_id` is NOT NULL and a family rule cannot
 be chained to one project's row. This makes the vocabulary a table so it can be
@@ -35,7 +35,7 @@ depends_on = None
 # service computes (canonical_slug: lowercase, "&" -> "and", non-alphanumerics
 # collapsed to "-"). Charters stay generic on purpose: a project refines its
 # own System's description, never this one. Nothing here names an app, a repo,
-# a vendor or a house convention — the catalog ships to every install (rule 115).
+# a vendor or a house convention — the catalog ships to every install.
 _SEED = (
     ("CI & Release", "ci-and-release",
      "How the project is verified and shipped: pipelines, runners, image/artifact builds, release tagging and rollback."),

alembic/versions/0104_tuning_events_carry_their_calibration.py

@@ -1,10 +1,10 @@
-"""retrieval_tuning_events carries the space each number was measured in (#4104)
+"""retrieval_tuning_events carries the space each number was measured in
 
 Revision ID: 0104
 Revises: 0103
 Create Date: 2026-09-17
 
-Milestone 416 step 6. A retrieval floor is a cosine distance in ONE embedding
+A retrieval floor is a cosine distance in ONE embedding
 model's geometry, computed over documents cut one particular way. Change the
 model and every score moves at once; change the chunker and the same record
 embeds different text. Either way a number chosen before the change is a
@@ -16,7 +16,7 @@ merely unknown.
 the startup backfill re-embeds precisely what is stale instead of wiping the
 table. These two columns are that idea applied to the tuned numbers.
 
-TWO COLUMNS, NOT ONE (rule 149). A reader has to be able to say WHICH half
+TWO COLUMNS, NOT ONE. A reader has to be able to say WHICH half
 moved: a new embedding model and a re-cut document shape invalidate the same
 numbers for different reasons, and a fused `"<model>@<n>"` could only report
 that something changed.

alembic/versions/0111_lesson_rule_links.py

@@ -1,5 +1,4 @@
 """lesson_rule_links — a lesson points at the rule it is an instance of
-(milestone 440 step 1, #4196)
 
 Revision ID: 0111
 Revises: 0110
@@ -21,8 +20,8 @@ down_revision = "0110"
 branch_labels = None
 depends_on = None
 
-# One place, so the CHECK and the model's LINK_STATES cannot drift (rule 36:
+# One place, so the CHECK and the model's LINK_STATES cannot drift (a new
-# a new value later means DROP + ADD CONSTRAINT in the same migration).
+# value later means DROP + ADD CONSTRAINT in the same migration).
 _STATES = ("suggested", "confirmed", "rejected")
 
 

alembic/versions/0112_lesson_no_rule.py

@@ -1,5 +1,4 @@
-"""lesson_no_rule — "no rule fits" is a recorded answer (milestone 440 step 2,
+"""lesson_no_rule — "no rule fits" is a recorded answer
-#4631)
 
 Revision ID: 0112
 Revises: 0111

alembic/versions/0116_moment_mappings.py

@@ -1,5 +1,5 @@
 """moment_mappings — an install's own corrections to which actions reach which
-moment (milestone 458 step 2)
+moment
 
 Revision ID: 0116
 Revises: 0115
@@ -8,7 +8,7 @@ Create Date: 2026-10-05
 The moments and their default actions are code; this table holds what an
 install adds ("make ship" is a deliver here) and the defaults it switches off.
 User-owned configuration, so it cascades with the user. No CHECK on `effect`,
-which the service validates (rule 36).
+which the service validates.
 """
 import sqlalchemy as sa
 from alembic import op

alembic/versions/0117_rule_moments.py

@@ -1,4 +1,4 @@
-"""rule_moments — the moments of work a rule arrives at (milestone 458 step 3)
+"""rule_moments — the moments of work a rule arrives at
 
 Revision ID: 0117
 Revises: 0116
@@ -28,7 +28,7 @@ def upgrade() -> None:
         sa.Column("moment", sa.Text(), primary_key=True),
         sa.Column("created_at", sa.DateTime(timezone=True), nullable=True),
     )
-    # The delivery read (step 4) asks "which rules are on this moment?", the
+    # The delivery read asks "which rules are on this moment?", the
     # opposite direction from the primary key.
     op.create_index("ix_rule_moments_moment", "rule_moments", ["moment"])
 

alembic/versions/0118_rule_moment_judgments.py

@@ -1,5 +1,4 @@
 """rule_moment_judgments — whether a rule belongs on a moment, and who said so
-(milestone 458 step 7, #4925)
 
 Revision ID: 0118
 Revises: 0117
@@ -23,8 +22,8 @@ branch_labels = None
 depends_on = None
 
 # One place each, so the CHECKs and the model's JUDGMENT_STATES / SOURCES
-# cannot drift (rule 36: a new value later means DROP + ADD CONSTRAINT in the
+# cannot drift (a new value later means DROP + ADD CONSTRAINT in the same
-# same migration).
+# migration).
 _STATES = ("suggested", "confirmed", "rejected")
 _SOURCES = ("pass", "signal", "edit")