gofastr

Documentation

Overview

Package main — `gofastr harness` subcommand.

Boot sequence per docs/harness-architecture.md § Lifecycle / boot. v0.1 flags supported:

--framework             use the framework preset profile
--profile <path>        explicit profile TOML
--web                   launch the bundled web client
--listen <addr>         bind a control-plane TCP listener
--no-listen             disable the Unix socket too (in-process only)
--allow-project-hooks   enable hooks in <repo>/.gofastr/harness/
--auto-approve          bypass human-ack permission requirement
--strict-permissions    no quiet-mode preset
--log-to-stderr         also write logs to stderr
--log-level <spec>      per-component level overrides

v0.1 doesn't yet launch the TUI / web — those are tasks 39 and 40. The subcommand instead boots the engine, registers everything, and runs a tiny REPL so the binary is functional end-to-end.

check-csp:ignore-file The harness web client is a dev-only operator surface, not a production browser app, so the framework's strict-CSP contract does not apply. The renderTUIShell helper inlines a tiny bootstrap <script> + <style> bundle so the harness runs without a build step or an extra HTTP round-trip; that's the explicit trade-off, hence the directive.