docs(roadmap): sweep the roadmap to main after v0.6.0 - #149
Merged
Conversation
Move the baseline from the v0.6.0 tag to main @ 1807734 (2026-09-09) and bring every track to what that commit carries. Everything merged after the tag is unreleased at this baseline and is the content of the next release. Status movements, each backed by the pull request's merge commit on main: - Track F closed: F1/F2 (#116), F3 (#120); #119 moved the synchronized step boundary. known_failures.txt is empty. - Track S landed: S1 (#110), S2 (#123), S3 (#125), S4 (#134); #141 made region order a choice point, #138 wrote the guide. The REPL refuses `%schedule explore` (confirmed against bin/sysml). - Track X: X3 (#115), X4 (#113), X6 (#122), X7's values (#121), X8's typing (#112) landed. Open: X2's chain-read half (interpolateLinear still refuses, confirmed against bin/sysml), X7's RDF literal form and native layout, X8's two harness halves (nothing under cmd/pilot-exec-diff or internal/core/export moved them). - Track A: A6 (#117), A3 (#118), A2 (#133), A5 (#136) landed; A4 remains, unblocked by A5. - Track L: L7 restated — Sample and domain-library calcs run, interpolateLinear is gated on X2. - Track Q: Q3 unblocked by A5. - Track E: deferral restated — F and S landed, no release carries them yet. - Track R: R4's MSI build fixed by #127 (v0.6.0 shipped no .msi); the repeated test-suite figures in README.md and spec-compliance.md are still hand-typed. - Track D: #774 was on the previous repository; no counterpart is open here and nothing under internal/core/rdf/ontology landed since the tag beyond #142's coverage wiring. - CI statements follow .circleci/config.yml (four jobs since #132, main and tags only since #108, HEAD^1 / previous-tag wire baseline) and .github/workflows/pr.yml; coverage table re-measured after #142. Counting commands used for "Where the repository stands": make docs-counts ls internal/core/runtime/testdata/conformance/*.sysml | wc -l # 770 go test -v -run TestExecutionConformance ./internal/core/runtime # 770 run ls internal/core/runtime/testdata/conformance/*.trace.golden | wc -l # 216 grep -l '"outcomes"' internal/core/runtime/testdata/conformance/*.expected.json | wc -l # 19 ls internal/core/runtime/testdata/conformance/*.trace.order | wc -l # 5 cat internal/core/runtime/testdata/conformance/known_failures.txt # 0 go test -v -run TestRuntimeRobustness ./internal/core/runtime # 369 go test -v -run TestGolden ./internal/core/parser # 197 go test -v -run TestNegative ./internal/core/parser # 249 / 338 / 396 go test -v -run 'TestGRPCConformance|TestGRPCRobustness' ./internal/grpc # 15 / 8 docs/project/pilot-rejection-baseline.json, validation-census and rdf-corpus-roundtrip baselines as committed go test -count=1 -cover -pgo=off -timeout 60m ./... # coverage table Verification: make build-sysml, make docs-counts, make docs-check, python3 scripts/changelog.py check, gofmt -l . (empty), go build ./..., go vet ./..., go test ./..., and the corpus gates with OPENSYSML_REQUIRE_TRAINING_CORPUS=1 OPENSYSML_REQUIRE_PILOT_CORPORA=1 all pass. Co-Authored-By: jason.han <[email protected]>
Contributor
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
Contributor
Author
There was a problem hiding this comment.
🔍 Devin Review: 2 flags
Not posted on this PR by your GitHub settings — view them in Devin Review. (Configure)
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why
docs/project/roadmap.mdwas pinned to thev0.6.0tag (30f103bb). Since then 34 pull requests (#110–#142, #144) merged tomainand only #140 touched the roadmap, so most of its "in progress" and "open" statements were stale. This moves the baseline tomain@180773449(2026-09-09), newest tagv0.6.0, and states every track as that commit carries it. Everything merged after the tag is described as unreleased at this baseline and the content of the next release; the roadmap does not depend onchanges/unreleased/or on any release pull request.Every landed/open/not-started word is backed by the pull request's merge commit on
main, by the tree, or by a probe againstbin/sysml. Only the roadmap changed;spec-compliance.md, the oracle and the corpus records are quoted, not edited.Item labels below (F1, S3, X2, …) are the roadmap's own cross-reference labels, defined in that record.
Status movements
ErrActionDeadlockoutcomes,.trace.orderreverse/declared/seed:<n>)-schedule explore)%schedule explore*value and.metadatacmd/pilot-exec-difforinternal/core/exportmoved them)interpolateLinear)bin/sysmlSampleand domain-library calcs run,interpolateLineargated on X2.msiin the release workflowv0.6.0shipped no.msi;WIX_CMDfix onmain, first published by the next tagv0.6.0README.md/spec-compliance.md;make docs-countscovers only the pilot figuresinternal/core/rdf/ontologylanded beyond #142's coverage wiringbuild-and-testjobmain/tags, GitHub Actions on PRs,HEAD^1/previous-tag wire baselineTracks D, N, M, I, V, B, Q1/Q2 and R2/R3/R5 are carried as they were, after checking
git log v0.6.0..origin/mainover their directories; the only movement noted is that the clients carry the four newValuearms.Recount, before → after
v0.6.0baseline.expected.jsonfiles listingoutcomes.trace.orderfilesspec-compliance.mdenumerates 337)TestNegative*)go test -count=1 -cover -pgo=off ./...How it was verified
make build-sysml, then probes againstbin/sysmlfor the X2 chain read, X3 casts, X4 infinity/metadata, X6 function values and-compilerefusal, X7 set equality and-compilerefusal, and the REPL's%schedule explorerefusal.make docs-counts,make docs-check(0 broken links,check-doc-idsOK),python3 scripts/changelog.py check— all pass.gofmt -l .empty;go build ./...,go vet ./...,go test ./...pass.OPENSYSML_REQUIRE_TRAINING_CORPUS=1 OPENSYSML_REQUIRE_PILOT_CORPORA=1 go test -count=1 ./internal/core/model -run 'TestTrainingExamples|TestPilotCorpora'pass;training_examples_expected.txtuntouched.Checklist
make testandmake lintpass locallychanges/unreleased/<slug>.<section>.md, not as an edit toCHANGELOG.md(none: a project-record edit is not a user-visible change, andchanges/unreleased/README.mdstates no requirement for one; the previous roadmap edits docs(roadmap): refresh 0.6.0 baseline #111 and docs(roadmap): add the bindings track, kernel conformance and the API element form #140 added none)make docs-countsrun if a gate count moved (compliance rows need nothing: the census is counted at docs build)F4,K5) in the body, docs, or changelog — the item labels used are the roadmap's own, defined indocs/project/roadmap.md