Skip to content

[Epic] Cross-platform assurance, test infrastructure, and performance #31

Description

@plx

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

  1. Run existing behavior on all supported operating systems and make fixtures hermetic.
  2. Land defect-specific regressions with the implementation tickets.
  3. Add generated round-trip/mutation properties and parser fuzz targets after contracts stabilize.
  4. Add platform conformance, coverage/mutation evidence, and performance baselines.

Completion criteria

  • Linux, macOS, and Windows execute the supported behavioral suite.
  • Generated supported filesystem trees round-trip exactly and mutations are detected.
  • Parser fuzzing covers historical reproductions and finds no panic, bypass, timeout, or uncontrolled allocation.
  • Tests are hermetic and retained public wrappers receive direct coverage.
  • Critical modules meet the reassessment coverage/effectiveness gates.
  • Performance scaling and resource limits meet the reassessment playbook.

Relationships

  • Parent epic: [Epic] Production readiness and formal v0.2.0 release #26
  • Native child and dependency links will be added after leaf creation.
  • Property and fuzz tickets depend on the stable parser/generator contracts; platform conformance depends on finalized symlink and identity policies.

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1Significant semantic, completeness, correctness issues.component: test-infraFixtures, property tests, fuzzing, coverage, and benchmarksdiscovered-by-codexIssues discovered via review by codex.domain: compatibilityPlatform, Rust-version, API, or format compatibilitydomain: correctnessBehavioral correctness and accurate validation resultsdomain: performanceRuntime scaling, memory use, or resource boundsdomain: reliabilityFail-closed, deterministic, and robust operational behaviorepicOrganizing issue that tracks a coherent remediation workstreamproduction-readinessPart of the audited path from prototype to production-ready userelease-blockerMust close before the production-readiness release gate can passrisk: cross-platformBehavior depends on operating-system or filesystem semanticstarget: v0.2.0Must be resolved or explicitly waived before the v0.2 production auditworkflow:production-readinessIncluded in automatic production-readiness work selectionworkflow:production-readiness-gateEpic, audit, publication, or program gate requiring landed prerequisites

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions