docs(adr): supersede ADR-0013 with core ADR-0055

docs/README.md

@@ -59,8 +59,8 @@ Repo-local decisions; org-wide ones go to frostyard/core and are listed in
   Hive ACMM path checks; directory criteria get real trees; the alias table
   is the registry
 - [ADR-0013 — Separate generic generation from production publishing](adr/0013-separate-generic-generation-from-production-publishing.md)
-  — proposed structural boundary that preserves generic callers while making
-  Frostyard production publication explicit and fail closed
+  — superseded by core ADR-0055 (never accepted): `frostyard/apt-publisher`,
+  not Repogen, publishes Frostyard's Debian packages
 - [ADR-0014 — Debian incremental restore fails closed](adr/0014-debian-incremental-restore-fails-closed.md)
   — Debian incremental initializes only when the suite is absent; every
   existing `Packages`/`Packages.gz` must parse, agree, and be selected, and no

docs/adr/0013-separate-generic-generation-from-production-publishing.md

@@ -1,8 +1,20 @@
 # 0013 - Separate generic generation from production publishing
 
-- **Status:** Proposed
+- **Status:** Superseded by [core ADR-0055](https://github.com/frostyard/core/blob/main/docs/adr/0055-publish-debian-packages-through-the-apt-publisher.md) (never accepted)
 - **Date:** 2026-09-12
 
+> **Superseded, 2026-10-23.** This ADR proposed a Frostyard production path for
+> Debian publication inside Repogen. Core ADR-0055 (Accepted 2026-10-02) makes
+> [`frostyard/apt-publisher`](https://github.com/frostyard/apt-publisher) the
+> only writer of Frostyard's Debian metadata and rejects Repogen as that writer.
+> So the production path below will not carry Frostyard Debian publication.
+> The rest of Repogen does not change: `generate` stays a general-purpose
+> generator (all formats, unsigned output), its output is not a production
+> artifact, and `publish-to-r2` keeps publishing sysexts and refuses `deb`.
+> The R2–R10 production code ([Plan 0001](../plans/0001-frostyard-production-publisher.md))
+> stays in the tree and stays tested; removing it is a separate decision.
+> The text below is kept unchanged as the record.
+
 ## Context
 
 Repogen is a general-purpose repository generator. Its current `generate`

docs/design/overview.md

@@ -351,13 +351,13 @@ Debian-input, explicit initialize, and strict signed-reconcile boundaries,
 while the isolated R4 primitive enforces conditional no-overwrite handling
 for shared-pool bytes in fixtures. Neither can generate or publish a
 production repository.
-The complete fail-closed Frostyard production publisher remains specified in
-[Plan 0001](../plans/0001-frostyard-production-publisher.md). The plan
-preserves generic local and unsigned generation while defining the proposed
-production-only target, identity, restore, shared-pool, staging, manifest,
-publication, and rollback contracts. The architectural rationale is recorded
-in proposed
-[ADR-0013](../adr/0013-separate-generic-generation-from-production-publishing.md).
+The complete fail-closed Frostyard production publisher is specified in
+[Plan 0001](../plans/0001-frostyard-production-publisher.md), which is
+superseded for Frostyard Debian publication: core
+[ADR-0055](https://github.com/frostyard/core/blob/main/docs/adr/0055-publish-debian-packages-through-the-apt-publisher.md) makes `frostyard/apt-publisher` the only Debian writer, so
+[ADR-0013](../adr/0013-separate-generic-generation-from-production-publishing.md)
+is superseded too. The R2–R10 code stays tested; removing it is a separate
+decision.
 
 ## Dependencies