wtclaude ab2efb62e4 feat(rust): RunicNPC as the Rust bundle's third artefact (runicnpc stage 4, D224) ...

The compose job carries the latest RunicNPC release that answers the API the
bridge's manifest declares (runicnpc_api), verified against its SHA256SUMS
like the other two; none when the bridge needs none, RunicNPC has not
released, or its API is too old, each said in the summary. Walked against a
mock Gitea in all three cases.

The installer reads the optional npc component (older bundles still parse),
fetches and checks RunicNPC's tarball against its manifest, places
RunicNPC.cs before the bridge in each instance's plugins directory, records
it, puts it back on update when edited or deleted, reports it in doctor, and
removes it on uninstall. Its data directory is never touched. Kits joins the
required plugins it reports.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

2026-09-30 04:52:36 -05:00

..

bundle.yml

feat(rust): RunicNPC as the Rust bundle's third artefact (runicnpc stage 4, D224)

2026-09-30 04:52:36 -05:00

pr-checks.yml

feat(installer): implement Phase 1 — the installer core

2026-08-04 14:58:17 -05:00

release.yml

fix(release): static musl Linux binaries, so the installer runs on Debian 12 (D158)

2026-09-26 04:47:07 -05:00

sync-project-tree.yml

fix(ci): preflight release credentials and recover from an orphan tag

2026-08-04 10:14:47 -05:00