feat!: integrate reliable network runtime and public site - #10
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bring the current runtime and public interface into selfmd/main. The existing main lacks later security and delivery fixes; this integration adds authenticated reliable delivery, persisted receipts and retries, group-manifest synchronization, and the public/operator interface with explicit publication controls.
Preserves the newer design and security implementation when reconciling the historical dashboard and policy branches. Policy PRs #2–#6 remain a separate forward-port stage; this PR does not enable agent tool execution.
Fixes a deployment blocker discovered during verification: the Docker image built successfully but failed at startup because production pruning removed workspace dependencies. Uses a frozen production install and adds a container startup/authentication smoke check to CI. Both CI jobs initialize the pinned docs submodule; package verification includes its exact commit.
Compatibility: handshake v3 requires coordinated peer upgrades; database migration reaches schema 9. MCP identity public keys use hex. Back up data and secrets before migration; rollback restores the prior data snapshot with the prior application version.
Validation: frozen pnpm 10.33.2 install, full production build including docs, workspace and dashboard-client TypeScript, 503 tests, five clean-archive npm tarball consumer checks, Linux arm64/Node 22 Docker build and live container publication/authentication checks passed. Production rollout and amd64 execution have not been verified.
See docs/releases/2026-09-07-integration.md for source reconciliation and rollout steps.