Skip to content

fix: operational hardening - #25

Merged
Monotox merged 5 commits into
mainfrom
fix/operational-hardening
Jul 23, 2026
Merged

fix: operational hardening#25
Monotox merged 5 commits into
mainfrom
fix/operational-hardening

Conversation

@Monotox

@Monotox Monotox commented Jul 23, 2026

Copy link
Copy Markdown
Owner

Summary

Test Plan

  • uv run pytest passes
  • uv run ruff check . passes
  • Documentation updated, if user-facing behavior changed
  • Golden fixtures updated, if a public JSON or Markdown contract changed

Contract Impact

  • No public contract surfaces changed
  • Public contract changes are intentional and versioned per CONTRIBUTING.md (Public contracts)

Monotox added 5 commits July 23, 2026 19:45
A batch re-parsed every shared mission, vehicle, and asset per run: ten
runs over one 500x500 terrain grid took 48s. Parse each input once per
invocation and load YAML with libyaml when present; the same batch now
runs in under two seconds.
Click's existence pre-check returned shell-style exit 2 with a usage
panel for a routine file race; let the loaders handle missing paths so
every input failure lands on the documented 11 with an error envelope.
A mission truncated at a clean line boundary validated silently because
constraints, assets, and policy are schema-optional. Validate-only now
names the absent blocks in its OK line and in a notes field on the
preflight envelope, without failing minimal missions.
Progress records carried no run identity, so a worker tailing the
stream could not tell which run stalled; batch records now include the
run_id of the run that just completed.
@Monotox
Monotox merged commit 688af77 into main Jul 23, 2026
6 checks passed
@Monotox
Monotox deleted the fix/operational-hardening branch July 23, 2026 17:53
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.

1 participant