The flag rewires the workflows but deliberately leaves the scaffolded
config.jsonc on OPENAI_API_KEY, so ecr verify-config fails in CI until the
user edits auth. Print that edit as an explicit next step instead of
leaving a silent CI failure (review finding 6cb8b566167c on PR #37).
* context-file: inject external context (Atlantis plans) into reviews as untrusted data
* context-file: enforce the read ceiling during the read, not by a prior stat
In routed aggregate ("single") mode, ecr ci posted an empty approve
comment with a zero-row scope table on every PR whose changed files
matched no scope. Now it posts nothing and deletes a stale aggregate
comment from an earlier run instead. The unmatched-files warning stays
in the job log. Per-scope mode already behaved this way.
The partial-run merge moves into an exported pure mergePartialAggregate
so the empty/carry-over boundary is unit-tested.
LLP 0009 said init is a pure copy with no logic; --token-env made that
false. Records the CI gap it closes (secret set but never mapped in the
YAML), why the mapping stays static, and the fail-loud template markers.
Retrofit of https://github.com/ccheever/llp. Ten LLP docs capture the
design rationale (trust model, engine pipeline, runtimes, config,
verification, sources/reporters, CLI, templates); 161 @ref comments link
code to the sections that explain it. ref-check (copied from upstream,
dependency-free) validates refs and metadata on every push and PR.
Every rationale claim is tagged [observed] with its evidence.