# Pending feedback drafts → mgf-common

Drafts staged here per the cross-repo feedback flow; relay into
mgf-common's FEEDBACK.md (or a Codeberg issue) on the next
mgf-common triage pass.

---

### PAPER — mirror the mgf-alembic scope delineation in `mgf.common.versioned`'s docstring

- **Severity:** Low (doc-only)
- **Filed by:** mgf-alembic queue sweep (Court/CTO sweep agent), 2026-07-10
- **What hurts:** A consumer with "a schema with a version field
  that needs migrating from N to N+1" can land on either
  `mgf.common.versioned.VersionedFileStore[T]` or mgf-alembic
  depending on which README they read first. mgf-alembic's README
  now states its side of the split ("DB-schema migrations only; for
  typed file-store versioning see
  `mgf.common.versioned.VersionedFileStore[T]`"), but the
  `mgf.common.versioned` docstring does not state the reverse.
- **Why it matters:** vm-vmanager-app's 2026-05-18 meta-feedback
  (mgf-alembic FEEDBACK.md §3) identified this as a class of
  consumer confusion; the fix is only complete when both surfaces
  point at each other.
- **Evidence:** mgf-alembic FEEDBACK.md §3 ("From vm-vmanager-app —
  2026-05-18") and the README scope blockquote shipped in
  mgf-alembic branch `feedback/queue-sweep-2026-07-10` (2026-07-10).
- **Suggested shape:** One sentence in `mgf.common.versioned`'s
  module docstring: "Scope: typed file-store versioning (YAML/JSON
  documents with a `version:` root field). NOT for SQL
  database-schema migrations — use mgf-alembic." Optionally, a
  follow-on "are you using the right primitive?" hint in the
  `_check_federation_contract` audit step (the submitter's larger
  ask — separate decision).
- **Status:** OPEN
