Skip to content

tracking: disposition of the parked afm-* / aozora-* scaffold repos #102

@P4suta

Description

@P4suta

Seven downstream repos describe themselves as "Archived snapshot (parked scaffold)" but are not actually GitHub-archived (they're live, and were included in the 2026-06 signed-commits ruleset sweep):

repo language
afm-logseq TypeScript
afm-obsidian TypeScript
afm-pandoc Lua
afm-zola HTML
aozora-epub Rust
aozora-typst Typst
aozora-zola HTML

Each needs a disposition decision (no implementation work — this is a 棚卸し):

  • Formally archive (set the GitHub archived flag) if they're truly parked — makes the "archived" description real and read-only.
  • Revive with the ecosystem baseline (pin aozora v0.4.x, hygiene) if they're on the roadmap.
  • Delete if superseded (e.g. afm-obsidian vs the active aozora-obsidian).

Note: the active downstream (afm-epub, aozora-obsidian) are tracked separately. Part of the 2026-06 ecosystem alignment (umbrella #101).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions