Skip to content

REST-only main vs community regression lane

Summary

Add a REST-only parity lane where existing seams make comparison against release/v0.72a-community meaningful.

This is not a promise that the community branch exposes the broadband REST API. It is also not a community release target. It is a guard for behavior that can be compared through shared seams or harness probes without changing stock runtime behavior.

Acceptance Criteria

  • [x] comparable status, preference, sharing, and network observations are identified
  • [x] broadband-only API behavior is explicitly marked as intentional delta
  • [x] failures distinguish product regression from missing community seam
  • [x] the lane runs against release/v0.72a-community by default, not stale historical branches

Progress

  • 2026-05-07: Added the supported workspace entrypoint python -m emule_workspace test community-core-coverage. It resolves main versus the default community baseline from workspace policy, runs native main/community coverage plus live-diff classification, and includes a main-scoped REST E2E leg to keep broadband-only REST behavior explicit. Validation command used for the entrypoint slice: python -m emule_workspace test community-core-coverage --config Debug --platform x64 --rest-coverage-budget smoke --rest-stress-budget off. Result: passed; live REST smoke report repos\emulebb-build-tests\reports\rest-api-smoke\20260507-120320-eMule-main-debug and community-core summary repos\emulebb-build-tests\reports\community-core-coverage\20260507-120309\community-core-coverage-summary.json.
  • 2026-05-07: Marked the broadband-only REST behavior criterion complete. The lane keeps REST E2E main-scoped and records that scope as intentional instead of treating missing community REST API support as a release regression.

Relationship To Other Items

  • backs CI-011
  • must follow the workspace parity/regression baseline rules