Skip to content

Beta 0.7.3 Community Parity Audit Plan

Historical release plan only. Current beta 0.7.3 execution is controlled by RELEASE-0.7.3-EXECUTION-PLAN.

This plan turns the broad release/v0.72a-community...main app delta into an actionable Beta 0.7.3 hardening backlog. It is documentation-first: each code or test change discovered by this audit must be implemented later as its own granular item commit.

Audit Inputs

Execution Workflow

  1. Refresh repository state.
  2. Check git status --short --branch in repos\emulebb-tooling, repos\emulebb-build, repos\emulebb-build-tests, and the active app worktree.

  3. Confirm the app candidate is on main and the baseline branch exists.

  4. Rebuild the changed-surface ledger.

  5. Run git diff --name-status release/v0.72a-community...main.
  6. Exclude generated Visual Studio user/filter churn unless it carries a release-relevant build change.

  7. Assign each changed file to exactly one release audit area in CI-022.

  8. Reconcile post-1.0 hardening.

  9. Run git log --oneline emule-bb-v1.0.0..main.
  10. Map BUG-102 through BUG-110 commits to test evidence, release area, and follow-up risk in CI-023.

  11. Create missing bug items only when a fix lacks acceptance or replay evidence.

  12. Run gate-by-gate proof.

  13. Controller and adapter proof: CI-024 and CI-025.
  14. Shared-file, download, persistence, search, networking, UI, and packaging proof: CI-026 through CI-031.

  15. Legacy disposition: REF-037.

  16. Promote findings.

  17. A release-blocking product defect becomes the next BUG-111+ item.
  18. Missing or weak automation stays in CI-022+.
  19. Intentional cleanup or compatibility-preserving refactor work becomes REF-038+.

  20. Non-blocking improvements go to FEAT-055 or later feature items.

  21. Close release.

  22. Update RELEASE-0.7.3 gate statuses only when each item contains passing evidence.
  23. Update INDEX counts and status tables after every item status change.
  24. Tag only after all Beta 0.7.3 release gates are Done or explicitly Wont-Fix by product decision.

Area Matrix

Area Primary item Required proof
Changed-surface inventory CI-022 Every app diff path has owner, risk, evidence lane, and item disposition.
Post-tag hardening CI-023 BUG-102..BUG-110 focused tests and validation are replayed.
Arr and aMuTorrent CI-024 Prowlarr, Radarr, Sonarr, and aMuTorrent live artifacts pass or are valid inconclusive.
REST/qBit/Torznab CI-025 Contract manifests, adapter quirks, auth, errors, and destructive routes are replayed.
Shared files/startup/cache/long paths CI-026 50k tree, watcher churn, cache restart, long-path, and shared-file REST probes pass.
Downloads/persistence CI-027 Part-file, known/server/Kad metadata, direct-download, completion hook, and restart probes pass.
Search/server/Kad CI-028 Search lifecycle, server import, Kad bootstrap, source exchange, and close/cleanup flows pass.
Network adversity CI-029 Bind, UPnP, TCP/UDP, WebSocket, HTTPS, and resource-churn checks pass.
UI/preferences/languages CI-030 Main-window smoke, list controls, preferences, tray, keyboard, resources, and representative language DLLs pass.
Packaging/release assets CI-031 x64/ARM64 packages contain expected binaries, manifests, docs, templates, and data files.
Legacy/frozen features REF-037 Each removed/frozen stock feature is explicitly dispositioned.
Improvements FEAT-055 Improvement ideas are ranked without expanding the Beta 0.7.3 blocking scope.

Evidence Rules

  • Prefer existing supported harnesses before adding new automation.
  • If behavior changed, compare against release/v0.72a-community when a meaningful parity lane exists.
  • If a community feature was intentionally removed or frozen, record the product decision in REF-037.
  • Do not mark a gate Done from a passing build alone; each gate needs behavior evidence for its changed area.
  • Do not mix app fixes, test hardening, and docs-status updates in one commit unless the change is inseparable.