fkst-hosted

Operator manual for the fkst-hosted control plane — how to start, drive, monitor, and stop autonomous fkst-substrate coding sessions ENTIRELY through GitHub issues (there is no other API surface for this). Use whenever you need to: (a) launch a session by opening an `fkst-substrate-trigger` issue with the exact `### Session Name` / `### Packages` / `### Work Label` / optional `### Environment` / `### Auto-merge` / `### FKST Contributors` (alias: `### Log Access Allowlist`) / `### Output Language` / `### Engine Config` body; (b) queue tasks by opening issues that carry the session's Work Label; (c) interpret the session's status comments and labels (registered / picked-up / degraded / retired / invalid / config-rejected); (d) download a session's redacted logs from the identity-gated `/api/v1/logs/{session_id}` endpoint; or (e) stop or idle a session by closing issues. Covers the package-reference grammar `owner/repo@ref:path`, config immutability, the idle-vs-permanent lifecycle, and the one-work-label-per-tr