chore(harness): bootstrap Systemfsoftware agent harness and strategy - #1
Open
systemfsoftware-maker wants to merge 12 commits into
Open
chore(harness): bootstrap Systemfsoftware agent harness and strategy#1systemfsoftware-maker wants to merge 12 commits into
systemfsoftware-maker wants to merge 12 commits into
Conversation
Single-source AGENTS.md across all product trees with machine-native @AGENTS.md CLAUDE.md pointers. Establish Systemfsoftware positioning and refactor roadmap in STRATEGY.md, rewrite server/foundry architecture docs to reflect current runtime, and add deterministic docs terminology gate.
…ocs gate Root, server, frontend, and foundry AGENTS.md were git symlinks to CLAUDE.md (30a66a7); writing through them lost the new law. Replace with real files. Convert scripts/check-docs.ts to deno with deno.jsonc and deno.lock in scripts/.
Judge sweep flagged G1/D4: AGENTS.md named check:ci and check:docs gates that existed nowhere, and described CI behavior that was false. Wire the Deno docs-gate chain into package.json, point CI at it, trim the shared-component echo trio to its sdks owner plus a root pointer.
systemfsoftware-maker
force-pushed
the
harness/systemfsoftware-bootstrap
branch
from
August 29, 2026 07:54
217d927 to
a7f351c
Compare
systemfsoftware-maker
changed the title
… test The test added Mock to the install list but not to the launcher setup loop, so install(Mock) always wrote the builtin launcher and reported already_installed=false. Mock is native_required=false like Pi and Cursor; stage its launcher stub alongside theirs. Red on main since June 19 (upstream run 27808704382).
The test connected to /v1/desktop/stream/ws, a path that no longer exists; the route, the TypeScript SDK, and both generated OpenAPI documents all serve /v1/desktop/stream/signaling.
… test The test asserted a ready frame, a JPEG video frame, and moveMouse input on the signaling websocket, all artifacts of the pre-neko in-house streaming design. The endpoint is a transparent relay: video and input travel over WebRTC. Assert the real contract: a non-empty relayed signaling frame arrives, and a client frame is accepted by the relay.
The suite's beforeEach builds the docker test-agent image in-process on every fresh CI runner, and a cold build of the common-software stack exceeds vitest's default 120s hookTimeout before the server health wait (bounded separately at 30s) ever starts. Give the hook an explicit 15 minute budget.
The in-process cold build compiles the whole Rust workspace in release mode inside docker on a cache-empty runner; 15 minutes measured short. Build progress is invisible because ensureImage pipes docker build stderr only, so the ceiling stays a ceiling until layer caching lands.
Two ceilings maxed (120s, 900s, 2700s) with zero build output in the log: ensureImage swallowed docker build stdout and piped stderr to nowhere, so a stall in the hub pull, apt layer, or cargo release build was invisible. Inherit stdio and force plain progress so the next run names where the time goes.
The sdk suite's docker build completed fully cached in under a second, then the image export stalled for the entire 45 minute hook budget. Best-supported cause is disk pressure: the runner holds node_modules, the debug target tree, toolchains, base images, and buildkit cache mounts when the exporter writes the final image. Drop the dead target tree and dangling layers after the cargo suites, and print usage so the next run either clears or names the stall.
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.
Summary
Bootstraps the end-state agent instruction hierarchy, strategy grounding, and deterministic verification gates for the repository under the Systemfsoftware banner.
This prepares the repo governance for the upcoming Effect-TS v4 migration and full oxlint integration without modifying product runtime code or forcing pre-migration linter dependencies.
Key Changes
AGENTS.mdat root,server/,sdks/,frontend/,examples/,foundry/, andfoundry/packages/backend/, paired with machine-native@AGENTS.mdpointers in all correspondingCLAUDE.mdfiles. Net deletion of ~1,050 lines of duplicate law.STRATEGY.md): Defines Systemfsoftware positioning ("L'État, c'est moi" sovereign standard), primary personas, boundary conditions, scoreboard metrics (CI green, rename completeness, Effect coverage), and the three active tracks (banner migration, Effect v4 adoption, lint sovereignty).ARCHITECTURE.md): Rewroteserver/ARCHITECTURE.mdand addedfoundry/ARCHITECTURE.mdto document current runtime components with Mermaid flowcharts, real data-flow paths, and explicit transition notes for the Effect-actor target state (purged dead package references and fabricated endpoints).scripts/check-docs.ts): Added deterministic gate for documentation rules (no em dashes in user-facing.mdx, no raw ACP references outside ACP-dedicated pages), and fixed existing em dashes indocs/deploy/boxlite.mdx,docs/processes.mdx, anddocs/sdk-overview.mdx.Verification
scripts/check-docs.tsruns clean locally (docs law: clean).