Browser and local console
React and static documentation present tasks, fixtures, safety settings, and reviewable output. Public demos stop here and never connect to a platform account.
How the toolkit works
A layered local architecture keeps orchestration, long-running workers, parsers, and output review separate. The public site documents those boundaries without exposing the private operator console.
Local control service
A Node.js HTTP/WebSocket process coordinates bounded commands, streams task output, and serves the developer console on loopback only.
Workers and APIs
.NET workers validate structured requests, use explicit queues for longer work, and expose health or result endpoints to local clients.
Parsers and protocol research
Package readers, protobuf models, and decoders work against files or captured synthetic fixtures. Unknown fields are preserved so reports remain inspectable.
Storage and reports
SQLite-compatible data and generated HTML/JSON reports hold derived results. Public screenshots replace paths, repository names, and identifiers with neutral fixtures.
Build lifecycle
- Resolve the selected component and configuration.
- Validate required tools and paths before execution.
- Spawn a bounded process with captured output.
- Stream state changes to the local console.
- Collect artifacts, checksums, and exit status.
Request lifecycle
- Validate and normalize the request.
- Assign a temporary correlation ID.
- Queue work outside the request thread.
- Persist only the derived result that is needed.
- Return a stable status and scrubbed diagnostic.
Protocol fixture lifecycle
- Load a schema and fabricated envelope.
- Decode known tags without discarding unknown data.
- Validate length, type, and nesting boundaries.
- Render a field tree and ordered event timeline.
- Export a report with identity fields removed.
Safety controls
- Loopback binding for local control surfaces.
- Explicit allowlists for command owners and paths.
- Example configuration separated from local secrets.
- No browser-side secret values or webhook URLs.
- No live Steam or Game Coordinator path in the public tester.
Open formats and community dependencies
| Area | Typical format or library | Purpose | Public-demo policy |
|---|---|---|---|
| Messages | Protocol Buffers / SteamKit-style models | Typed envelope research | Synthetic fixtures only |
| Packages | Valve resource and package formats | Local asset inventory | Metadata examples only |
| Services | HTTP, WebSocket, JSON | Local orchestration and progress | Mocked in browser |
| Workers | .NET background services | Queue processing and diagnostics | Architecture documented |
| Reports | HTML, JSON, PNG | Human and machine review | Paths and IDs scrubbed |
Compatibility research, not platform integration
Valve, Steam, Counter-Strike 2, and Game Coordinator are referenced to explain file formats and interoperable protocol research. The project is unofficial, does not claim endorsement, and does not ship a browser login or a live-service connection. Contributors are responsible for applicable licenses, terms, and local law.