Skip to content

Make .fkst/env.example describe what it can actually do - #3970

Merged
fkst-loning-s-macbook-m5[bot] merged 1 commit into
devfrom
docs/env-example-documents-what-it-reads
Aug 25, 2026
Merged

fkst-loning-s-macbook-m5[bot] merged 1 commit into
devfrom
docs/env-example-documents-what-it-reads

Conversation

@fkst-loning-s-macbook-m5

Copy link
Copy Markdown
Contributor

The template taught twelve FKST_* settings. Exactly one of them works.
scripts/bin_bootstrap.sh greps this file for ^BIN= and never sources it, so
every other line a reader copies into .fkst/env is inert.

Worse, the settings it taught contradict what the repository does with them.
scripts/run.sh unsets FKST_GITHUB_WRITE before run so a single department run
cannot mutate GitHub, and clears a twenty-eight variable hermetic set before
tests so they cannot read host posture -- and every FKST_GITHUB_* and
FKST_DEVLOOP_* line in the template was in that set. The file also described
supervise, an entry point this repository stopped providing when operation
moved to fkst-ops.

That is residue from the supervise-entry migration: the supply side moved to
deployment declarations plus fkst-ops, and the template stayed behind. It now
documents the one line it is read for, states where the rest actually comes
from, and says plainly why putting host posture here would do nothing twice
over.

Verified rather than asserted: bin_bootstrap.sh has one ^BIN= grep and no
source of this file; run.sh:406 unsets FKST_GITHUB_WRITE; run.sh:558 is the
hermetic clear; bin_bootstrap.sh reads .fkst/substrate-ref for the pinned-source
fallback. scripts/run.sh check exits 0 and the layout tests pass.

Co-authored-by: Claude Opus 5 (1M context) noreply@anthropic.com

The template taught twelve FKST_* settings. Exactly one of them works.
scripts/bin_bootstrap.sh greps this file for `^BIN=` and never sources it, so
every other line a reader copies into .fkst/env is inert.

Worse, the settings it taught contradict what the repository does with them.
scripts/run.sh unsets FKST_GITHUB_WRITE before `run` so a single department run
cannot mutate GitHub, and clears a twenty-eight variable hermetic set before
tests so they cannot read host posture -- and every FKST_GITHUB_* and
FKST_DEVLOOP_* line in the template was in that set. The file also described
`supervise`, an entry point this repository stopped providing when operation
moved to fkst-ops.

That is residue from the supervise-entry migration: the supply side moved to
deployment declarations plus fkst-ops, and the template stayed behind. It now
documents the one line it is read for, states where the rest actually comes
from, and says plainly why putting host posture here would do nothing twice
over.

Verified rather than asserted: bin_bootstrap.sh has one `^BIN=` grep and no
source of this file; run.sh:406 unsets FKST_GITHUB_WRITE; run.sh:558 is the
hermetic clear; bin_bootstrap.sh reads .fkst/substrate-ref for the pinned-source
fallback. scripts/run.sh check exits 0 and the layout tests pass.

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
@fkst-loning-s-macbook-m5
fkst-loning-s-macbook-m5 Bot merged commit 12eebdc into dev Aug 25, 2026
2 checks passed
@fkst-loning-s-macbook-m5
fkst-loning-s-macbook-m5 Bot deleted the docs/env-example-documents-what-it-reads branch August 25, 2026 15:36
@codecov

codecov Bot commented Aug 25, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants