11 Commits

Include renames

Author	SHA1	Message	Date
justme	904ea2b0ae	refactor: remove the runtime binary binding; every release registration path verifies the CI signature [CI] ... The hash a node reports about itself cannot be trusted (a swapped binary can copy the old hash), so the runtime binding only caught files that were replaced by something that did not lie. Provenance stays where it can be verified: the signed release manifest (digest) and the signed SHA256SUMS. - Remove BinaryBindingService, the node_bindings table (schema v15 drops it), BinaryPolicy, the handshake hash/manifest fields and the admin binary column. - Drop the per-platform "binaries" list from the release manifest, the hash scripts and the updater's installed.manifest copy. - ReleaseService.PublishAsync now verifies the release signature, so the admin POST /releases route is no longer an unsigned path; tests sign with a test key. - Docs: section 16 explains why the runtime check is gone.	2026-10-08 18:30:05 +08:00
justme	4841f7b15b	feat: bind each node to the binary it runs at its first handshake; refuse changes that are not in a CI-signed manifest [CI]	2026-10-08 05:39:13 +08:00
justme	117d34a2af	feat: signed manifests live in the image registry; updaters and first deploys fetch and verify them without the panel [CI]	2026-10-08 05:05:13 +08:00
justme	f704c66dd9	feat: CI registers release manifests without a token; the panel verifies the CI signature instead [CI]	2026-10-08 04:22:01 +08:00
justme	84f9d211bc	backend: require confirmation for signed channel updates [CI]	2026-10-07 12:57:20 +08:00
justme	2e146d4da7	refactor!: rename the project from Monitor to MoShiro [CI] ... Namespaces, assemblies, solution, binaries, images, systemd units, config paths, environment variables, protocol methods and the Linux user are all renamed. Breaking: existing databases, node identities and installed units must be recreated.	2026-10-07 02:03:25 +08:00
justme	d449e50791	feat: update controls in the admin, release token scope, build info in CI images [CI] ... The versions page shows each node's update state with update buttons, API tokens get a release scope that can only register releases (used by CI), and the CI image and release builds now pass the tag, commit and build time.	2026-10-06 22:57:04 +08:00
justme	8dd3209a65	feat!: probes link to the panel; signed release updates for container nodes [CI] ... Probes connect to the panel directly and get the agent list as desired state. CI signs the image digest of agent and probe releases, the panel forwards the manifest, and a host updater verifies it with a local public key, pulls by digest and rolls back when the new version is unhealthy.	2026-10-06 22:42:12 +08:00
justme	383afa777b	ci: publish main amd64 images to dev Zot [CI SKIP]	2026-10-06 16:14:50 +08:00
justme	19c6cab104	ci: run main amd64 image builds in parallel [CI SKIP]	2026-10-06 15:59:54 +08:00
justme	46499b10b6	ci: build amd64 on opt-in main commits [CI SKIP]	2026-10-06 15:40:35 +08:00