Add "What's next" section to ROADMAP (Stage 11 implementation order) by aallan · Pull Request #483 · aallan/vera

aallan · 2026-04-17T08:48:25Z

Tiny docs-only PR that captures the Stage 11 implementation order ahead of the longer-term milestone structure.

The phase numbering in milestones (Phase 4a/4b/4c) reflects strategic grouping. It does not reflect the order we plan to tackle things in. This section is where implementation order lives — a rolling view of the next few weeks.

Why add this now

While planning #480/#463/#465, a model writing Conway's Game of Life gave concrete feedback that reshaped the priority ordering: capability-expansion issues (IO.sleep, Random, math) move ahead of error-reduction issues (array/string utilities) because they unlock entire genres of program rather than just reducing error rate on existing programs. Worth writing down before it gets lost.

What's in the section

The capability-vs-ergonomics framing
The empirical agent quote that motivated the reordering
An 8-row implementation table from Reimplement higher-order array ops as iterative WASM loops #480 (structural prerequisite) through JSON typed accessors: json_as_string, json_get_number, etc. #366 (polish)
A note that this is meant to rotate out as items ship

Verification

doc counts consistent (3,319 tests, 28 files, 73 conformance, 30 examples, 24 hooks, 7 CI jobs)
site assets up to date
all pre-commit hooks pass

🤖 Generated with Claude Code

Summary by CodeRabbit

Documentation
- Roadmap updated with a new short-term priorities section that defines two issue categories (capability-expansion vs error-reduction/ergonomic), an ordering principle prioritising blocking capability gaps before ergonomic improvements, a fixed implementation-order table of upcoming items with guidance to refresh as work completes, and an expanded Milestone note clarifying planned IO-related operations.

Captures implementation order for Stage 11 work separately from the strategic phase grouping in the milestones below. Records the reasoning — capability-expansion (IO.sleep, Random, math) vs ergonomic / error-reduction (array/string/char utilities) — and the empirical evidence that reshaped the ordering (feedback from a model writing Conway's Game of Life during Stage 11 planning). Intended as a rolling 'next few weeks' view, not a permanent roadmap layer. When Stage 11 primitives mostly ship, the table shrinks and the section gets re-evaluated. Co-Authored-By: Claude <noreply@anthropic.invalid>

coderabbitai · 2026-04-17T08:48:39Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 77bb2414-15a2-4fb6-947f-d3a0c0724eef

📥 Commits

Reviewing files that changed from the base of the PR and between 2cb47f8 and 810a4d8.

📒 Files selected for processing (1)

ROADMAP.md

📝 Walkthrough

Walkthrough

Adds a "What's next — short-term priorities" section to ROADMAP.md that defines two issue categories (capability-expansion vs error-reduction/ergonomic), sets prioritisation rules (capability gaps first; #480 as prerequisite), and adds an ordered "Implementation order" table of eight issues.

Changes

Cohort / File(s)	Summary
Roadmap prioritisation guidance `ROADMAP.md`	Inserted a "What's next — short-term priorities" section before "Milestone 1".Defines two issue categories, states prioritisation principle (capability gaps before ergonomic/error-reduction; `#480` as top prerequisite), expands Milestone 4a note for `#463` (adds `IO.sleep`, `IO.time`, `IO.stderr`), and adds an "Implementation order" table listing `#480`, `#463`, `#465`, `#467`, `#466`, `#470`, `#471`, `#366` in sequence; doc-only changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

Track 7 new issues in ROADMAP.md and KNOWN_ISSUES.md #472: Modifies ROADMAP.md and references many of the same Stage 11 issues (#463, #465, #466, #467, #470, #471) present in this implementation order.
Documentation consistency sweep + stdlib improvement issues #369: References issue #366 (JSON typed accessors / stdlib items), which appears in this PR's implementation table.
docs: split ROADMAP into milestone roadmap + HISTORY build narrative #405: Alters ROADMAP.md structure and "what's next" sequencing, overlapping with this PR's changes.

Suggested labels

docs

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarises the main change: adding a 'What's next' section to ROADMAP with Stage 11 implementation ordering, which is the primary content of this documentation-only PR.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch roadmap-whats-next

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

codecov · 2026-04-17T08:49:39Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.37%. Comparing base (0ccc930) to head (810a4d8).
⚠️ Report is 4 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #483   +/-   ##
=======================================
  Coverage   90.37%   90.37%           
=======================================
  Files          58       58           
  Lines       19588    19588           
  Branches      225      225           
=======================================
  Hits        17703    17703           
  Misses       1881     1881           
  Partials        4        4

Flag	Coverage Δ
javascript	`50.67% <ø> (ø)`
python	`95.29% <ø> (ø)`

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

'Stage 11' is vocabulary from HISTORY.md (narrative development phases) and isn't introduced anywhere in ROADMAP. Referencing it without definition in the roadmap is confusing. Reworded to use terms that stand on their own: 'near-term queue', 'the next few weeks of work', 'implementation order'. Co-Authored-By: Claude <noreply@anthropic.invalid>

coderabbitai

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@ROADMAP.md`:
- Around line 38-48: The ROADMAP table's row for issue [`#463`] is inaccurate: it
claims three operations but the GitHub issue only adds IO.sleep; update the
Order 2 row (the table entry for [`#463`]) to either split it into separate rows
for IO.sleep, IO.time, and IO.stderr (creating new issue entries or referencing
the correct issue numbers) or simply correct the "Why now" cell to describe only
"Add IO.sleep operation" to match `#463`; ensure the row text and any bolded
summary reflect the chosen fix so the table and issue link are consistent.
- Around line 25-26: Phase 4a's brief description currently only mentions
IO.sleep for issue `#463` but the issue and the implementation table cover three
operations; update the Phase 4a entry (the "Phase 4a" heading/paragraph) to
either enumerate IO.sleep, IO.time, and IO.stderr or to reference the fuller
scope for `#463` so the description matches the implementation table and issue
scope (use the symbols IO.sleep, IO.time, IO.stderr and issue `#463` when
editing).

🪄 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: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: e8a165fd-e115-4d0f-9ba6-2396f7f868fb

📥 Commits

Reviewing files that changed from the base of the PR and between d892ceb and 2cb47f8.

📒 Files selected for processing (1)

ROADMAP.md

CodeRabbit caught that Phase 4a still described #463 as 'IO.sleep operation' — the original narrow scope — while the issue body (extended earlier in this session) now covers IO.sleep, IO.time, and IO.stderr. Two fixes: 1. Updated issue #463 title from 'Add IO.sleep operation' to 'Add IO.sleep, IO.time, and IO.stderr operations' so the title no longer understates the scope. 2. Updated Phase 4a's description to list all three operations with their signatures and concrete rationale, matching the 'What's next' table row. The 'What's next' section's entry was already accurate; this commit brings the Phase 4a milestone entry and the issue title in line. Co-Authored-By: Claude <noreply@anthropic.invalid>

coderabbitai Bot reviewed Apr 17, 2026

View reviewed changes

Comment thread ROADMAP.md

Comment thread ROADMAP.md

aallan merged commit e9a1d24 into main Apr 17, 2026
19 checks passed

aallan deleted the roadmap-whats-next branch April 17, 2026 09:43

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add "What's next" section to ROADMAP (Stage 11 implementation order)#483

Add "What's next" section to ROADMAP (Stage 11 implementation order)#483
aallan merged 3 commits into
mainfrom
roadmap-whats-next

aallan commented Apr 17, 2026 •

edited by coderabbitai Bot

Loading

Uh oh!

coderabbitai Bot commented Apr 17, 2026 •

edited

Loading

Walkthrough

Changes

Estimated code review effort

Possibly related PRs

Suggested labels

Uh oh!

codecov Bot commented Apr 17, 2026 •

edited

Loading

Uh oh!

coderabbitai Bot left a comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

aallan commented Apr 17, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Why add this now

What's in the section

Verification

Summary by CodeRabbit

Uh oh!

coderabbitai Bot commented Apr 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Estimated code review effort

Possibly related PRs

Suggested labels

Uh oh!

codecov Bot commented Apr 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

aallan commented Apr 17, 2026 •

edited by coderabbitai Bot

Loading

coderabbitai Bot commented Apr 17, 2026 •

edited

Loading

codecov Bot commented Apr 17, 2026 •

edited

Loading