docs: explain Boatstack's supervisory runtime

[bigboateng]

Summary

• explain the operator, kernel, Control Program, and Flow boundaries
• separate the general kernel from the software-delivery domain and developer surfaces
• document objective bindings and the state-and-receipt control loop
• state the current alpha scope without presenting unfinished Flow ergonomics as shipped

Verification

• python3 .github/scripts/release_notes.py validate
• python3 -m unittest discover -s .github/tests -p 'test_*.py' -q (34 tests)
• git diff --check

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[github-actions]

Codex automated review

Verdict: patch is incorrect
Confidence: 0.98

The documentation incorrectly attributes delivery-engine idempotent replay to the generic kernel. Model-level verification is not recommended; this is directly established from the runtime and Store interfaces.

[github-actions]

Codex automated review

Verdict: patch is incorrect
Confidence: 0.97

The README's new domain split incorrectly attributes software-delivery authority classes to the general kernel. Model-level verification is not recommended; correcting the documented ownership boundary and its contract test is sufficient.

[github-actions]

Codex automated review

Verdict: patch is correct
Confidence: 0.98

The patch only reorganizes and clarifies README documentation, adds a matching release note, and enforces the intended kernel/domain wording boundary in the repository contract test. No actionable behavioral defect was established. Model-level verification is not recommended because no runtime control behavior changes.