-
Notifications
You must be signed in to change notification settings - Fork 0
[Epic] Cross-platform assurance, test infrastructure, and performance #31
Copy link
Copy link
Open
4 / 54 of 5 issues completedOpen
4 / 54 of 5 issues completed
Copy link
Labels
P1Significant semantic, completeness, correctness issues.Significant semantic, completeness, correctness issues.component: test-infraFixtures, property tests, fuzzing, coverage, and benchmarksFixtures, property tests, fuzzing, coverage, and benchmarksdiscovered-by-codexIssues discovered via review by codex.Issues discovered via review by codex.domain: compatibilityPlatform, Rust-version, API, or format compatibilityPlatform, Rust-version, API, or format compatibilitydomain: correctnessBehavioral correctness and accurate validation resultsBehavioral correctness and accurate validation resultsdomain: performanceRuntime scaling, memory use, or resource boundsRuntime scaling, memory use, or resource boundsdomain: reliabilityFail-closed, deterministic, and robust operational behaviorFail-closed, deterministic, and robust operational behaviorepicOrganizing issue that tracks a coherent remediation workstreamOrganizing issue that tracks a coherent remediation workstreamproduction-readinessPart of the audited path from prototype to production-ready usePart of the audited path from prototype to production-ready userelease-blockerMust close before the production-readiness release gate can passMust close before the production-readiness release gate can passrisk: cross-platformBehavior depends on operating-system or filesystem semanticsBehavior depends on operating-system or filesystem semanticstarget: v0.2.0Must be resolved or explicitly waived before the v0.2 production auditMust be resolved or explicitly waived before the v0.2 production auditworkflow:production-readinessIncluded in automatic production-readiness work selectionIncluded in automatic production-readiness work selectionworkflow:production-readiness-gateEpic, audit, publication, or program gate requiring landed prerequisitesEpic, audit, publication, or program gate requiring landed prerequisites
Description
Metadata
Metadata
Assignees
Labels
P1Significant semantic, completeness, correctness issues.Significant semantic, completeness, correctness issues.component: test-infraFixtures, property tests, fuzzing, coverage, and benchmarksFixtures, property tests, fuzzing, coverage, and benchmarksdiscovered-by-codexIssues discovered via review by codex.Issues discovered via review by codex.domain: compatibilityPlatform, Rust-version, API, or format compatibilityPlatform, Rust-version, API, or format compatibilitydomain: correctnessBehavioral correctness and accurate validation resultsBehavioral correctness and accurate validation resultsdomain: performanceRuntime scaling, memory use, or resource boundsRuntime scaling, memory use, or resource boundsdomain: reliabilityFail-closed, deterministic, and robust operational behaviorFail-closed, deterministic, and robust operational behaviorepicOrganizing issue that tracks a coherent remediation workstreamOrganizing issue that tracks a coherent remediation workstreamproduction-readinessPart of the audited path from prototype to production-ready usePart of the audited path from prototype to production-ready userelease-blockerMust close before the production-readiness release gate can passMust close before the production-readiness release gate can passrisk: cross-platformBehavior depends on operating-system or filesystem semanticsBehavior depends on operating-system or filesystem semanticstarget: v0.2.0Must be resolved or explicitly waived before the v0.2 production auditMust be resolved or explicitly waived before the v0.2 production auditworkflow:production-readinessIncluded in automatic production-readiness work selectionIncluded in automatic production-readiness work selectionworkflow:production-readiness-gateEpic, audit, publication, or program gate requiring landed prerequisitesEpic, audit, publication, or program gate requiring landed prerequisites
Parent
#26
Objective
Turn the remediation fixes into durable evidence: real behavioral CI on every supported OS, generated filesystem round-trip properties, parser fuzzing, hermetic tests, direct library coverage, branch-aware coverage reporting, and explicit performance/resource bounds.
Why this blocks release
The current 127 tests all pass but miss the core false-success cases. Full tests run only on Ubuntu; macOS and Windows merely build. The suite has no property-generated filesystem invariant, fuzz targets, or branch coverage, and one integration test walks the mutable checkout. Parser hierarchy and placeholder verification show measured quadratic scaling.
Workstream order
Completion criteria
Relationships
Non-goals
A coverage percentage alone does not close this epic. The suite must demonstrate that blocker regressions are red on the audited baseline and green on the candidate.