Skip to content

[carve-out 2/9] Evict k9-svc/ implementations → k9-ecosystem; dedupe k9-svc/actions/validate → k9-validate-action #491

Description

@hyperpolymath

Child of #479. k9-svc/ is 1,915 files / 13MB and contradicts its own published site copy ("Implementations and CI live in the k9-ecosystem hub; the normative spec is in standards" — site/index.md, site/spec.md).

Stays: SPEC.adoc, SPEC.adoc.invariants.md, GUIDE.adoc, TESTING.adoc (conformance-relevant parts), security analyses, IANA media-type application doc.
Moves to hyperpolymath/k9-ecosystem: bindings/ (~5.4M), editors/ (~1.8M), pandoc/ (~1.8M), lsp/, tools/, k9-scan/, k9-sign/, site/, showcase/, packaging/, benchmarks/, mime/, receipt/, must/, Containerfile, compose.yaml, guix.scm.
Deleted here (exists upstream): k9-svc/actions/validate/ — a vendored copy of hyperpolymath/k9-validate-action (its in-tree SECURITY.md names the other repo as its identity). Two copies of an executable CI action is a supply-chain hazard.

Same mechanics as #490: subtree-split for history, registry regen in the same PR, --check green, mass-deletion marker if a guard exists, SPDX/licence content untouched (flag-only rule). Turn SPEC.adoc.invariants.md + the k9-coordination test vectors into a language-neutral conformance suite as the follow-up that makes this spec evidenced.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions