Skip to content

docs: reflect shipped burst strategy and accepted ADR statuses - #58

Merged
ThomasK33 merged 1 commit into
mainfrom
docs/v0.2.0-doc-polish
Aug 28, 2026
Merged

docs: reflect shipped burst strategy and accepted ADR statuses#58
ThomasK33 merged 1 commit into
mainfrom
docs/v0.2.0-doc-polish

Conversation

@ThomasK33

Copy link
Copy Markdown
Member

Pre-release doc polish for v0.2.0: two stale doc surfaces that lagged behind the ConcurrencyBurst landing (#57) and the ADR 0015 acceptance (#54/#56).

Changes

  • README § Dedupe, Locks, And Concurrency — the section claimed four strategies shipped with burst "staged". All five ADR 0012 strategies ship (ConcurrencyDrop, ConcurrencyQueue, ConcurrencyDebounce, ConcurrencyConcurrent, ConcurrencyBurst, feat(runtime): revive ConcurrencyBurst per-instance under ADR 0015 invariants #57). Added the burst bullet and narrowed the "remaining surface" paragraph to the one genuinely outstanding concept: force/steerability (onLockConflict) preemption, rejected for v0.x per ADR 0015 with the names reserved behind its formal-design bar.
  • docs/explanation.md § Decision Records — ADR 0012 row updated from "Accepted (staged)" with burst staged to "Accepted" with all five strategies implemented; ADR 0015 row updated from "Proposed" to "Accepted". Both match the ADRs' own Status sections.

Claims verified against runtime.go (all five Concurrency* constants ship, incl. ConcurrencyBurst + BurstWindow/MaxBurstBatch) and the Status sections of ADR 0012 and ADR 0015.

Doc-only diff; no code changes.


Generated with mux • Model: anthropic:claude-fable-5 • Thinking: xhigh

README's concurrency section still claimed four strategies with burst
staged; all five ship since #57. The ADR index in explanation.md still
showed 0012 as staged and 0015 as Proposed; both are Accepted and
implemented. Force/steerability preemption remains the sole
rejected/reserved concept per ADR 0015.
@ThomasK33

Copy link
Copy Markdown
Member Author

@codex review

@ThomasK33

Copy link
Copy Markdown
Member Author

@codex security review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. 🚀

Reviewed commit: 2a3556e00b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@chatgpt-codex-connector

Copy link
Copy Markdown

Security review completed. No security issues were found in this pull request.

Reviewed commit: 2a3556e00b

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

@ThomasK33
ThomasK33 merged commit 42b8a86 into main Aug 28, 2026
1 check passed
@ThomasK33
ThomasK33 deleted the docs/v0.2.0-doc-polish branch August 28, 2026 00:30
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