Skip to content

docs: synchronize roadmap and evidence status#91

Merged
div0rce merged 1 commit into
mainfrom
docs/roadmap-sync-after-m29
Jun 2, 2026
Merged

docs: synchronize roadmap and evidence status#91
div0rce merged 1 commit into
mainfrom
docs/roadmap-sync-after-m29

Conversation

@div0rce
Copy link
Copy Markdown
Owner

@div0rce div0rce commented Jun 2, 2026

Summary

  • Synchronize root memory files after M28/M29 review so M29 is classified as perf workflow plus constrained-environment validation, not full hardware PMU evidence.
  • Record issue M29 follow-up: generate full Linux hardware PMU perf artifacts #90 as the follow-up for full Linux hardware PMU perf artifacts.
  • Add backlog/roadmap entries for TSan limits, pool-backed order-book integration, and M32-M41.
  • Add ADRs for dynamic concurrency validation limits, allocator-vs-engine-storage separation, and constrained perf artifacts.

Verification

  • Documentation-only change.
  • No code changes.
  • No benchmark result changes.
  • make check passes locally: 186/186.

Note

AGENTS.md was updated locally as requested, but it is intentionally ignored by this repository via .gitignore, so the PR carries the committed source-of-truth docs (CLAUDE.md, MILESTONES.md, PROGRESS.md, HANDOFF.md, CHANGELOG.md, and docs/ADR files).

@div0rce
Copy link
Copy Markdown
Owner Author

div0rce commented Jun 2, 2026

@codex review

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 2535f3bbd7

ℹ️ 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".

Comment thread PROGRESS.md Outdated
@div0rce div0rce force-pushed the docs/roadmap-sync-after-m29 branch from 2535f3b to 9cfddf7 Compare June 2, 2026 06:04
@div0rce
Copy link
Copy Markdown
Owner Author

div0rce commented Jun 2, 2026

@codex review

@chatgpt-codex-connector
Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Nice work!

ℹ️ 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".

@div0rce div0rce marked this pull request as ready for review June 2, 2026 06:10
@div0rce div0rce merged commit 86443f0 into main Jun 2, 2026
6 checks passed
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9cfddf7de3

ℹ️ 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".

Comment thread HANDOFF.md
Comment on lines +17 to +18
The repo is released at `v0.1.0`. M0–M28 are merged. M29 is PR #89 and should land as Linux
`perf` workflow plus constrained-environment validation only.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Mark M29 as completed in the handoff

In this post-M29 docs-sync context, PROGRESS.md now records M29 as squash-merged via PR #89/commit 60bd5ee and points the next action at PR #91 then M30, but HANDOFF.md is the operator manual read on resume and this line still tells the next agent that M29 is PR #89 and should land. Following the handoff can send future work back to an already-merged PR instead of treating M29 as complete, so this current-state sentence should mark M29/#89 complete and make M30/PR #91 the active handoff.

Useful? React with 👍 / 👎.

@div0rce div0rce deleted the docs/roadmap-sync-after-m29 branch June 2, 2026 06:14
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