docs: establish BlockWire boundaries and deployment baseline - #88
Draft
stormchaserog wants to merge 1 commit into
Draft
stormchaserog wants to merge 1 commit into
stormchaserog wants to merge 1 commit into
Conversation
stormchaserog
added
the
internal
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
BlockWire's root status entry pointed to an August handoff without a current deployment baseline or a consistent architecture/agent contract. This establishes the four root documents and marks STATUS.md as historical evidence.
The docs preserve the public client/private service boundary, the existing dev production branch, Matrix delegation and service-worker deployment constraints, and a dated serving-commit baseline. Private infrastructure and deployment-account details remain outside this public repo.
Validation: changed-document Oxfmt 0.61.0 check passed under Node 24; relative Markdown links and source facts checked; git diff --check passed. Documentation only: no application, dependency, workflow, or production configuration changes. Device push, calls, native builds, and backend behavior were not re-tested. Uses the existing internal label for a documentation-only change rather than a product release changeset.
Remote CI found existing formatting failures in src/app/features/lobby/Lobby.tsx and src/app/features/project-identity/ProjectInfoOverview.tsx. Both files are unchanged by this PR; changed-document formatting passes.
Browser CI stopped during test-account registration: the Matrix test server returned HTTP 403 / M_FORBIDDEN (registrations disabled). No application or test-server settings were changed to bypass this. Build, typecheck, lint, Knip, CodeQL, and Vercel preview passed; the unit-test job also passed. Formatting remediation is isolated in PR #89.