Skip to content

Milestones

List view

  • Systematic, evidence-backed discovery and remediation of duplicate facilities, implementation drift, interface friction, representation churn, dead code, shallow modules, and repetitive tests. Excludes routine CRAP/coverage ratchet work and issue-specific preparatory refactors.

    No due date
    2/7 issues closed
  • The feed-machinery slices that follow #282 rather than sit inside the Inbound v1 arc: adaptive polling, WebSub push delivery, inbound auto-discovery, source lifecycle and health, interaction-surface discovery, and the webmention reaction slice. Design: docs/feed-reading.md (its §9 decomposition is this epic's contents).

    No due date
    0/6 issues closed
  • User-facing web-UI product & operator features (hub UI, onboarding/invites, operational controls) with no other engineering-epic home.

    No due date
    0/10 issues closed
  • Make invalid states unrepresentable for domain values, per ADR-0063. Establishes the standard str-newtype trailer (as a #[derive] in the macros crate) and threads validated newtypes through storage, DTOs, and the server-fn boundary. Pulls together the numeric-ID / token / hash work (#17), the DTO/boundary threading (#14, #91), and the string domain-value gaps: AudienceName (#350), Email (#397), RenderedHtml (#398), FeedUrl (#399), InviteCode (#400), DisplayName (#401), PostBody/PostTitle (#402).

    No due date
    106/110 issues closed
  • Cross-cutting correctness and data-integrity bugs without a feature-epic home: backup/restore data loss, visibility/privacy enforcement, transactional integrity, scheduling, and auth/credential hardening.

    No due date
    28/40 issues closed
  • Build the hub between a real producer and a real consumer, per docs/hub-architecture.md and the sequencing discussion on #172: (1) RSS/Atom as the first, cheapest producer — it exercises the same archive → Item → event-log seams as any protocol, while AP's cost is mostly Q2 identity work the hub never sees; (2) sync engine v1 + a minimal reader as the first jaunder-client slice (triggers the Q8 API design); (3) Q2 federated-actor identity as an independent parallel track; (4) AP inbound as the second producer, landing into a contract RSS already stabilized — the second protocol proves the abstraction.

    No due date
    0/7 issues closed
  • CRAP grind-down and clippy-suppression removal, plus small structural refactors. The web co-located-Leptos convergence work has moved to its own milestone.

    No due date
    76/119 issues closed
  • Planning the inbound/federation half of Jaunder: consuming others' broadcasts (ActivityPub, RSS/Atom, AT) and the user-centered hub design.

    No due date
    0/2 issues closed
  • End-to-end (Playwright/NixOS-VM) plus the broader test-infra surface: harness dedup, wasm-bindgen-test, visual/snapshot + a11y assertions, the CSR->spec traceability matrix, and mutation testing.

    No due date
    82/95 issues closed
  • Authoring + reconcile over AtomPub, plus the server-side extensions it needs. Epic spec: docs/superpowers/specs/2026-06-16-emacs-blogging-frontend-design.md

    No due date
    41/48 issues closed
  • devtool ergonomics, the host build/e2e loop, worktree-hook fixes, and dependency maintenance. (Supersedes the completed 'Devtool migration' scope.)

    No due date
    52/65 issues closed