These are local tracked issue IDs, not claims that remote GitHub issues exist. Strict expected failures remain visible in every full-suite report. An unexpected pass fails the suite, requiring review and removal of the marker. Other skips include missing integrations and unsupported legacy feature tests. They are distinct from these seven known roadmap expectations and must not all be described as optional hardware coverage.
Pipeline stage/fork DSL parsing is incomplete. The existing test recovers into an
incorrect stage node. TestLanguageIntegration.test_pipeline_processing retains
its assertions and expects AssertionError until pipeline grammar is implemented.
Stream checkpoint synchronization is not an executable language feature.
test_stream_synchronization expects the existing AST-shape AssertionError.
Symbolic function declarations and solve/prove DSL operations are roadmap syntax.
test_symbolic_mathematics expects the existing empty-AST IndexError.
The enhanced tensor-map DSL is unimplemented. The minimal parser’s basic tensor declaration routing was fixed and its tests now pass; this separate tensor-map expectation remains a strict AttributeError expected failure.
Adaptive parameter-sweep refinement is not implemented. The legacy test expects record-shaped adaptive results, whereas supported fixed-grid sweeps return a dictionary of parameter tuples to values. It remains a strict TypeError expected failure, not a claim that adaptive sampling works.
Automatic serial/parallel strategy selection is not implemented. Its test remains a strict AttributeError expected failure for the absent optimize_strategy API.
Automatic memory-budget-based scheduling is not implemented. Bounded queue depth and explicit batch sizes are supported; the memory_limit/auto_batch contract remains a strict TypeError expected failure. A fixed test budget avoids hiding that missing API behind a missing psutil dependency.
The repository has pre-existing lint and typing debt beyond this patch. New verification and isolation modules are lint-gated; the whole-package legacy audit is retained as a visible, non-blocking CI diagnostic, not reported as clean.
Local verification cannot prove Windows behavior. The full CI matrix must actually run on its OS-specific runners before cross-platform release approval. No remote run is triggered and no cross-platform success is claimed merely from editing YAML.