Skip to content

Beta 0.7.3 community parity changed-surface ledger

Summary

Create the authoritative changed-surface ledger for Beta 0.7.3. Every path changed between release/v0.72a-community and current Broadband main must be mapped to a release area, regression risk, evidence lane, and item disposition.

This gate closes first because it decides whether later work needs a bug item, test item, refactor item, feature item, or explicit no-action rationale.

Scope

  • REST, WebServer, qBit-compatible, Torznab-compatible, and WebSocket paths
  • shared files, startup cache, long-path, and watcher paths
  • download, part-file, direct-download, completion-hook, and persistence paths
  • upload queue, bandwidth, and scoring paths
  • search, server, Kad, source-exchange, and UDP paths
  • preferences, UI shell, tray/menu, keyboard, and language/resource paths
  • GeoLocation, IPFilter, bundled flags, and refresh paths
  • packaging, build, manifest, setup, README, and policy-facing paths
  • removed or frozen legacy stock features

Acceptance Criteria

  • [x] git diff --name-status release/v0.72a-community...main is captured or regenerated with the exclusions documented in the audit plan.
  • [x] Every changed path is assigned to exactly one Beta 0.7.3 audit area.
  • [x] Every area has an owner item: CI-023 through CI-031, REF-037, FEAT-055, an existing active item, or a new item.
  • [x] Every removed path is marked as restored, intentionally removed/frozen, or release-blocking.
  • [x] Every high-risk changed path has either existing evidence or a follow-up item with acceptance criteria.
  • [x] The ledger records whether release/v0.72a-community comparison is meaningful for that path.

Completion Evidence

powershell git diff --name-status release/v0.72a-community...main -- . ':!srchybrid/emule.vcxproj.filters' ':!srchybrid/emule.vcxproj.user'

  • The ledger assigns every path to exactly one of ten release audit areas and records owner item, baseline-comparison policy, and release disposition.
  • Removed or renamed paths are explicitly routed to either downstream owner gates or REF-037 for legacy/frozen feature disposition.
  • Validation:
  • active-doc link check
  • git diff --check
  • python -m emule_workspace validate

Validation

  • git -C EMULE_WORKSPACE_ROOT\workspaces\v0.72a\app\eMule-main diff --name-status release/v0.72a-community...main
  • python -m emule_workspace validate

Relationship To Other Items