Skip to content

Align both roadmaps with the roadmap grammar - #245

Open
leynos wants to merge 2 commits into
mainfrom
docs/roadmap-syntax
Open

Align both roadmaps with the roadmap grammar#245
leynos wants to merge 2 commits into
mainfrom
docs/roadmap-syntax

Conversation

@leynos

@leynos leynos commented Jul 1, 2026

Copy link
Copy Markdown
Owner

Summary

This branch aligns both namespaced roadmaps with the mapsplice roadmap
grammar, which requires numbered phase and step headings (## N. Title,
### N.M. Title), forbids unnumbered headings after the first phase,
and rejects reference-style links. Headings written as ## Phase N: Title and ### Step N.M: Title are rewritten to the numbered forms
with every number and title kept intact. No phases, steps, tasks,
numbering, ordering, or checkbox states change, and the files are not
renamed.

Review walkthrough

  • Start with docs/lille-map-and-presentation-roadmap.md, where the change is purely mechanical: eight Phase/Step headings become ## N./### N.M. forms.
  • Then read docs/lille-physics-and-world-engine-roadmap.md, which additionally drops the stray section number from ## 1. Vision and Strategy (making it and the Bevy Upgrade Checklist preamble), demotes the unnumbered ### Tick timing heading inside phase 3 to a bold paragraph, and inlines the [health-type-defs] reference-style link.

Validation

  • mapsplice append docs/lille-map-and-presentation-roadmap.md <dummy-phase>: exit 0 (grammar-clean)
  • mapsplice append docs/lille-physics-and-world-engine-roadmap.md <dummy-phase>: exit 0 (grammar-clean)
  • bunx markdownlint-cli2 on both files: 0 errors

Notes

  • ## 1. Vision and Strategy carried a document-section number that
    made the checker parse it as phase 1, colliding with the real phase 1
    (Phase 1: Foundational Migration to DBSP). Removing that stray
    number, rather than renumbering the four real phases, keeps every
    existing phase number stable and turns the section into valid
    preamble.
  • The Bevy Upgrade Checklist keeps its heading and position; once the
    Vision section is unnumbered, it sits in the preamble, where the
    grammar accepts unnumbered sections and checklists.
  • Task lines such as - [x] Task 1.1.1 — ... and the ordered
    **Key Tasks** groupings are accepted by the checker as they stand,
    so they are left untouched.
  • The demoted **Tick timing:** paragraph ends with a colon so that
    markdownlint's MD036 (emphasis-as-heading) rule does not fire.
  • No documents link to the renamed headings by anchor; the only
    cross-reference into the physics roadmap is a commit-pinned permalink
    with line numbers, which is unaffected.

Summary by Sourcery

Align the Lille map/presentation and physics/world-engine roadmap documents with the roadmap grammar by standardizing numbered phase/step headings, adjusting preamble structure, and replacing reference-style links with inline links while keeping all roadmap content and task structure intact.

Enhancements:

  • Align roadmap phase and step headings with the mapsplice grammar by converting "Phase/Step" headings to numbered forms without changing content or structure.
  • Treat the physics roadmap vision and Bevy upgrade checklist as preamble by removing the stray phase number from the vision heading and demoting the tick timing subsection from a heading to emphasized text.
  • Inline the health-type definitions reference-style link in the physics roadmap to use direct inline Markdown links compliant with the roadmap checker.

Documentation:

  • Update both Lille roadmap documents to conform to the required roadmap heading and link grammar while preserving existing phases, steps, tasks, and ordering.

References

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Sorry @leynos, you have reached your weekly rate limit of 500000 diff characters.

Please try again later or upgrade to continue using Sourcery

@coderabbitai

coderabbitai Bot commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review

Summary

  • Updated both Lille roadmap documents to use the numbered mapsplice heading hierarchy.
  • Removed the stray physics roadmap section number and demoted “Tick timing” to a bold paragraph.
  • Converted the health-type definition reference to an inline link.
  • Added Oxford spelling dictionary entries for polymer-related variants.
  • Preserved roadmap content, ordering, numbering, and checkbox states; both documents pass mapsplice validation and markdownlint.

Walkthrough

Reformat both Lille roadmap documents with numbered hierarchy, updated subsection syntax, and an inline health-type link. Extend typos.toml with polymer spelling mappings while preserving existing roadmap content.

Changes

Documentation and spelling updates

Layer / File(s) Summary
Reformat roadmap structure and references
docs/lille-map-and-presentation-roadmap.md, docs/lille-physics-and-world-engine-roadmap.md
Renumber phase and step headings, remove the redundant vision heading prefix, convert “Tick timing” to a bold label, and replace the health-type link reference with an inline link and remove its unused definition.
Add polymer spelling mappings
typos.toml
Add UK polymer spelling variants and corresponding US spellings to default.extend-words.

Possibly related PRs

Suggested labels: Roadmap

Poem

Number the phases, align every line,
Let roadmap headings neatly shine.
Polymer spellings join the queue,
Old link references bid adieu.
Tick-time speaks in bold anew.

🚥 Pre-merge checks | ✅ 20
✅ Passed checks (20 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately reflects the main change: standardising the roadmap grammar across both Lille roadmap documents.
Description check ✅ Passed The description stays on-topic and matches the documented roadmap heading, link, and grammar changes.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Testing (Overall) ✅ Passed The diff changes only typos.toml (HEAD^..HEAD); the branch adds no behaviour, so no substantive tests are required.
User-Facing Documentation ✅ Passed Only internal roadmap docs and typos config changed; no user-facing functionality or behaviour was added, so no users-guide update is required.
Developer Documentation ✅ Passed PASS: The PR only reformats roadmap headings and updates typos.toml; no APIs, architecture, tooling, developer-guide, ADR, or execplan content changed.
Module-Level Documentation ✅ Passed This PR only edits documentation and typos config; no modules are changed, so the module docstring rule is not applicable.
Testing (Unit And Behavioural) ✅ Passed Docs and typo-config only; no runtime or behavioural boundary changed, so unit or end-to-end tests are not applicable.
Testing (Property / Proof) ✅ Passed The PR only rewrites roadmap prose and typos.toml; it adds no runtime invariants, state transitions, or proof assumptions that warrant property or proof tests.
Testing (Compile-Time / Ui) ✅ Passed PASS: The PR only reworks Markdown docs and typos config; no compile-time or UI behaviour changed, so trybuild/snapshot tests are not applicable.
Unit Architecture ✅ Passed Only roadmap docs and typos.toml changed; no executable units, dependencies, queries, or side-effects were modified.
Domain Architecture ✅ Passed Only typos.toml changed in the actual commit; no domain, adapter, persistence, or framework code was touched.
Observability ✅ Passed Touch only typos.toml spelling mappings; no runtime code, logging, metrics, tracing, or alerts changed.
Security And Privacy ✅ Passed Only spelling-dictionary entries changed; no secrets, credentials, auth logic, or sensitive data exposure appeared in the diff.
Performance And Resource Use ✅ Passed Docs and typo-dictionary edits only; no executable paths, loops, I/O, allocations, or resource-growth changes were introduced.
Concurrency And State ✅ Passed Only Markdown roadmap headings and a typos dictionary changed; no executable shared state, async tasks, locks, or ordering-sensitive code was introduced.
Architectural Complexity And Maintainability ✅ Passed No new abstractions, layers, traits, or dependencies were introduced; the patch is documentation formatting plus typo dictionary entries.
Rust Compiler Lint Integrity ✅ Passed PASS: The PR only changes docs and typos.toml; no Rust files, lint suppressions, or ownership changes were introduced.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/roadmap-syntax

Comment @coderabbitai help to get the list of available commands.

codescene-access[bot]

This comment was marked as outdated.

@leynos
leynos force-pushed the docs/roadmap-syntax branch from 26ef93d to b87cd64 Compare July 8, 2026 11:04
codescene-access[bot]

This comment was marked as outdated.

@leynos
leynos marked this pull request as ready for review July 24, 2026 15:36
The roadmap grammar requires numbered phase and step headings of the
form "## N. Title" and "### N.M. Title", forbids unnumbered headings
after the first phase, and rejects reference-style links.

In docs/lille-map-and-presentation-roadmap.md, rewrite the
"## Phase N: Title" and "### Step N.M: Title" headings to the
numbered forms, keeping every number and title unchanged.

In docs/lille-physics-and-world-engine-roadmap.md:

- Drop the stray section number from "## 1. Vision and Strategy" so
  the section reads as preamble instead of a phase; this also places
  the Bevy Upgrade Checklist in the preamble, where unnumbered
  sections are valid.
- Rewrite the "## Phase N: Title" headings to "## N. Title".
- Demote the unnumbered "### Tick timing" heading, which sits inside
  phase 3, to a bold paragraph in place.
- Convert the "[canonical type definitions][health-type-defs]"
  reference-style link to an inline link and remove the link
  definition, because reference links are unsupported.

No phases, steps, tasks, numbering, ordering, or checkbox states
change. The mapsplice checker now parses both documents cleanly.
@sourcery-ai

sourcery-ai Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates both Lille roadmap documents to conform to the mapsplice roadmap grammar by renumbering phase/step headings into strict numeric forms, adjusting a misparsed preamble heading, demoting an internal subheading to emphasized text, and inlining a reference-style link while preserving roadmap structure and tasks.

Sequence diagram for mapsplice roadmap grammar validation after heading updates

sequenceDiagram
  actor Developer
  participant mapsplice
  participant roadmap_file as LilleRoadmapMarkdown
  participant grammar_checker as RoadmapGrammarChecker

  Developer->>mapsplice: mapsplice append docs/lille-physics-and-world-engine-roadmap.md dummy_phase
  mapsplice->>roadmap_file: load_document
  mapsplice->>grammar_checker: validate_headings
  grammar_checker-->>mapsplice: headings_valid
  mapsplice->>grammar_checker: validate_links
  grammar_checker-->>mapsplice: links_valid
  mapsplice-->>Developer: exit 0

  Developer->>mapsplice: mapsplice append docs/lille-map-and-presentation-roadmap.md dummy_phase
  mapsplice->>roadmap_file: load_document
  mapsplice->>grammar_checker: validate_headings
  grammar_checker-->>mapsplice: headings_valid
  mapsplice-->>Developer: exit 0
Loading

File-Level Changes

Change Details Files
Convert roadmap headings from "Phase/Step" labels to strict numeric heading grammar without altering roadmap semantics.
  • Rewrite all phase headings from the form "## Phase N: Title" to "## N. Title".
  • Rewrite all step headings from the form "### Step N.M: Title" to "### N.M. Title".
  • Keep all existing phase/step numbers, titles, ordering, and task lists unchanged.
docs/lille-map-and-presentation-roadmap.md
docs/lille-physics-and-world-engine-roadmap.md
Adjust physics roadmap preamble and internal formatting to satisfy grammar and lint rules while keeping content and structure intact.
  • Remove the leading numeric section marker from the "Vision and Strategy" heading so it is treated as preamble rather than phase 1.
  • Inline the previously reference-style "health-type-defs" markdown link into the paragraph that uses it.
  • Demote the "Tick timing" subheading from a level-3 heading to a bold paragraph with a trailing colon to avoid emphasis-as-heading lint issues.,
docs/lille-physics-and-world-engine-roadmap.md

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Hey - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

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

Copy link
Copy Markdown

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: b87cd64107

ℹ️ 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 docs/lille-physics-and-world-engine-roadmap.md
@lodyai
lodyai Bot force-pushed the docs/roadmap-syntax branch from b87cd64 to bb5b9ea Compare July 24, 2026 15:48
codescene-access[bot]

This comment was marked as outdated.

@coderabbitai coderabbitai Bot added the Roadmap label Jul 24, 2026
Record the Oxford spelling entries regenerated by the documentation gate so
subsequent validation leaves the worktree clean.
codescene-access[bot]

This comment was marked as outdated.

codescene-access[bot]

This comment was marked as outdated.

@codescene-access codescene-access Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

No quality gates enabled for this code.

@buzzybee-df12

Copy link
Copy Markdown
Collaborator

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Jul 25, 2026

Copy link
Copy Markdown
Contributor
✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/lille-physics-and-world-engine-roadmap.md`:
- Line 3: Update the roadmap headings to sentence case:
docs/lille-physics-and-world-engine-roadmap.md lines 3, 42, 101, 153, and 303
should use “Vision and strategy,” “Foundational migration to DBSP,” “Achieving
physics parity,” “Expanding physics and agent dynamics,” and “Advanced features
and polish,” respectively.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 6b4f21b6-45b5-4ce6-9462-ddaf287eb012

📥 Commits

Reviewing files that changed from the base of the PR and between a304c92 and c81c2ce.

📒 Files selected for processing (3)
  • docs/lille-map-and-presentation-roadmap.md
  • docs/lille-physics-and-world-engine-roadmap.md
  • typos.toml

# Lille Physics and World Engine Roadmap

## 1. Vision and Strategy
## Vision and Strategy

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Use sentence case for the updated roadmap headings.

The changed headings remain in title case, contrary to the documentation style instruction.

  • docs/lille-physics-and-world-engine-roadmap.md#L3-L3: Change Vision and Strategy to Vision and strategy.
  • docs/lille-physics-and-world-engine-roadmap.md#L42-L42: Change Foundational Migration to DBSP to Foundational migration to DBSP.
  • docs/lille-physics-and-world-engine-roadmap.md#L101-L101: Change Achieving Physics Parity to Achieving physics parity.
  • docs/lille-physics-and-world-engine-roadmap.md#L153-L153: Change Expanding Physics and Agent Dynamics to Expanding physics and agent dynamics.
  • docs/lille-physics-and-world-engine-roadmap.md#L303-L303: Change Advanced Features and Polish to Advanced features and polish.

Triage: [type:docstyle]

📍 Affects 1 file
  • docs/lille-physics-and-world-engine-roadmap.md#L3-L3 (this comment)
  • docs/lille-physics-and-world-engine-roadmap.md#L42-L42
  • docs/lille-physics-and-world-engine-roadmap.md#L101-L101
  • docs/lille-physics-and-world-engine-roadmap.md#L153-L153
  • docs/lille-physics-and-world-engine-roadmap.md#L303-L303
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/lille-physics-and-world-engine-roadmap.md` at line 3, Update the roadmap
headings to sentence case: docs/lille-physics-and-world-engine-roadmap.md lines
3, 42, 101, 153, and 303 should use “Vision and strategy,” “Foundational
migration to DBSP,” “Achieving physics parity,” “Expanding physics and agent
dynamics,” and “Advanced features and polish,” respectively.

Source: Path instructions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants