Files

164 lines
17 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
phase: 01-reproducible-fidelity-baseline
plan: "07"
type: execute
wave: 5
depends_on: ["01-06"]
files_modified:
- tools/recon/fidelity_acceptance.py
- tests/test_fidelity_acceptance.py
- docs/evidence/checkpoint-session.md
- docs/evidence/capabilities.json
- docs/evidence/phase01-baseline.md
- docs/progress.md
- docs/tasks.md
- docs/decisions.md
- docs/compatibility.md
- scripts/test.sh
autonomous: false
requirements: [EVID-01, EVID-02, EVID-03, EVID-04]
estimate:
tokens: 30000
raw_tokens: 30000
tasks: 3
confidence: low
must_haves:
truths:
- "One fully prepared combined session covers original-DxWnd and native Windows cases, local Linux review and real paired playback, per D-13–D-16."
- "Every required original-reference and native Linux/Windows case has exact revision/package/resource/media and observation provenance; absent or failed cases keep EVID-02/EVID-04 open."
- "Paired review of actual original/port captures applies D-05–D-08 and publishes raw drift, discrepancies and audible/visible checks."
- "Current capabilities/history/discrepancies are reconciled to returned receipts per D-09–D-12, with full matrix completeness per D-01–D-04."
- statement: "Actual original-DxWnd moving game imagery and intelligible audio are observed and reviewed with wrapper/config limitations recorded."
verification: backstop
- statement: "Actual paired recordings decode, seek and switch exclusive audio in the identified local browser without concealing elapsed time."
verification: backstop
assumptions:
- requirement_id: EVID-02
category: unclassified
status: unresolved
flagged: true
statement: "Deterministic probe could not classify reference-execution edge behavior; manually review original/DxWnd capture boundaries and limitations in the final session."
- requirement_id: EVID-04
category: unclassified
status: unresolved
flagged: true
statement: "Deterministic probe could not classify native-platform execution edges; manually review actual native input/audio/route and identity evidence in the final session."
artifacts:
- path: tools/recon/fidelity_acceptance.py
provides: "Separate readiness and strict acceptance audits"
- path: docs/evidence/checkpoint-session.md
provides: "Final single-session handoff and result checklist"
- path: docs/evidence/phase01-baseline.md
provides: "Actual receipts, discrepancies and open acceptance report"
key_links:
- from: "Returned Windows/local Linux results"
to: tools/recon/fidelity_acceptance.py
via: "Validated artifact identities and complete case/platform plus human checks"
- from: docs/evidence/phase01-baseline.md
to: docs/evidence/capabilities.json
via: "Same receipt IDs and current applicability; no unsupported acceptance promotion"
---
<objective>
Finish the prepared checkpoint, perform the one combined hands-on session and reconcile actual original/native proof. Materials readiness, test success and native/original acceptance have separate verdicts. Missing execution prevents Phase 1 acceptance while permitted source-backed later work may continue under the roadmap exception.
Artifacts this phase produces: fidelity_acceptance.py ready/audit CLI; tests/test_fidelity_acceptance.py; checkpoint-session.md; phase01-baseline.md; final local READY.json, acceptance.json and returned-results manifests. Existing capability/root status documents and scripts/test.sh are updated only after independent plans finish. No user capture is requested before task 01-07-01 readiness succeeds.
</objective>
<scope_budget>
The ten-file list is a bounded final integration exception, estimated at 30,000 tokens
against the 100,000-token plan budget. There are two substantive implementation files:
`tools/recon/fidelity_acceptance.py` and its dedicated tests. Task 01-07-01 owns these
plus the final session checklist; it adds no recorder, viewer or package subsystem.
Task 01-07-02 consumes the already prepared bundle and updates the existing capability
records plus one baseline findings report from validated results. Its human dependency
can remain pending and cannot be disguised as completed acceptance.
Task 01-07-03 has only integration/projection work: add already-created counted test
invocations to `scripts/test.sh`; add revision/receipt/open-status entries to the four
existing root reports. It must not refactor the runner, invent new tests/features,
change gameplay or redesign those reports. These five thin edits share one source
of truth (the final acceptance/test receipts) and remain serially owned here after
all parallel work ends. The checklist and baseline report use the same receipt IDs;
no additional independent design decision is deferred to this plan.
If an implementation change beyond those boundaries is discovered, stop that expansion
and record it for a separately planned task; keep current acceptance gaps explicit.
</scope_budget>
<execution_context>
@/home/cristian/.codex/gsd-core/workflows/execute-plan.md
@/home/cristian/.codex/gsd-core/templates/summary.md
</execution_context>
<context>
@AGENTS.md
@.planning/PROJECT.md
@.planning/ROADMAP.md
@.planning/REQUIREMENTS.md
@.planning/phases/01-reproducible-fidelity-baseline/01-CONTEXT.md
@.planning/phases/01-reproducible-fidelity-baseline/01-05-SUMMARY.md
@.planning/phases/01-reproducible-fidelity-baseline/01-06-SUMMARY.md
@.planning/phases/01-reproducible-fidelity-baseline/01-SOURCE-AUDIT.md
</context>
<tasks>
<task type="tracer" tdd="true" id="01-07-01">
<name>Audit one prepared checkpoint from actual receipts through review and explicit pending acceptance</name>
<files>tools/recon/fidelity_acceptance.py, tests/test_fidelity_acceptance.py, docs/evidence/checkpoint-session.md</files>
<read_first>All prior phase SUMMARY interfaces; docs/evidence/scenarios.json; capabilities.json; windows-session.md; linux-session.md; 01-SOURCE-AUDIT.md flagged assumptions/prohibitions; actual checkpoint manifest and available Linux receipts.</read_first>
<behavior>At least 14 tests cover ready/audit end-to-end, complete valid evidence, missing/aborted cases, false native classification, wrong package/resources, synthetic original, absent human visibility/audio/physical-input checks, contradictory/superseded history and both unclassified review flags. Strict audit must exit nonzero on every acceptance gap while ready may report materials prepared with gaps visible.</behavior>
<action>Create tests first. Implement ready --checkpoint ROOT to validate all prepared manifest members, scenario matrix/procedures, package/observer consistency, generated viewer/ledger links, dependency instructions, PowerShell tests and local transfer/result forms. Implement audit --checkpoint ROOT --results ROOT --require-complete to require actual original-DxWnd and native Linux/native Windows case receipts, exact package/resource/artifact identities, complete continuous/focused matrix, observed event provenance, visibility/audibility/physical-input review and wrapper limitations. Structural audits may use --allow-open but print pending acceptance and all missing cases; their zero exit is never a native acceptance result. End-to-end tests import an actual available Linux receipt plus explicitly synthetic negative fixtures, generate the final review index and show strict acceptance staying nonzero until real dependencies are met. Unknown/unclassified probe assumptions and descriptor-less prohibitions require visible human review disposition; do not auto-dismiss them. Research backstop truths A1/A2 abstain to human_needed if real evidence is insufficient. Merge all earlier human-only checks into checkpoint-session.md as one agenda. Recheck manifest freshness immediately before handoff; changed binaries/resources require a new identified bundle, not patched identity labels. No capture request in this task.</action>
<acceptance_criteria>All 14 tests pass; ready produces materials_ready separately from acceptance; audit demonstrably rejects every absent original/native/human dependency; all session materials and pending checks are assembled before handoff.</acceptance_criteria>
<verify>
<automated>python3 -c 'import sys,unittest; s=unittest.defaultTestLoader.discover("tests",pattern="test_fidelity_acceptance.py"); assert s.countTestCases() >= 14,"fewer than 14 acceptance tests"; sys.exit(not unittest.TextTestRunner(verbosity=2).run(s).wasSuccessful())'</automated>
<fails_when>Nonzero exit, fewer than 14 tests, or strict acceptance succeeds on missing/synthetic/misclassified/unreviewed evidence.</fails_when>
<automated>python3 tools/recon/fidelity_acceptance.py ready --checkpoint dist/fidelity/phase01</automated>
<fails_when>Nonzero exit, missing materials_ready=true summary, stale/missing hashed member, or absent acceptance=pending/open status when actual execution is still missing.</fails_when>
</verify>
<done>The complete bundle is reviewable and ready for one combined session; strict original/native acceptance remains separate and correctly pending where evidence is absent.</done>
</task>
<task type="auto" id="01-07-02">
<name>Collect the single combined session and reconcile actual original/native captures</name>
<files>docs/evidence/capabilities.json, docs/evidence/phase01-baseline.md</files>
<read_first>docs/evidence/checkpoint-session.md; ready audit output; returned local result manifests; current capabilities.json; actual original/native captures and receipt categories.</read_first>
<action>After all materials are complete, hand off one local checkpoint and perform the single combined hands-on session per D-13–D-16. Use end-of-phase human verification rather than intermediate checkpoint tasks. Run the prepared PowerShell selftests, select/identify DxWnd/OBS/profile, verify generated original copies, test visible moving content and audible output, then capture every required original-DxWnd/native-Windows case and physical input checks. Complete actual Linux physical/audible checks and real paired playback review from the agenda in the same review cycle. Retain all failed preflights, skipped cells and wrapper/capture/browser limits. Receive results only through local media/filesystem transfer and validate identities before import. Review raw recordings, images, events, exclusive audio, real elapsed/event drift, optional overlays and derivative metadata per D-05–D-08. No universal parity threshold may be invented. Publish per-case/platform findings, discrepancies and remaining conditions in phase01-baseline.md and update capabilities.json current/history per D-09–D-12. Record manual disposition of both unclassified EVID-02/EVID-04 assumptions and project-value prohibitions; insufficient evidence remains flagged human_needed/open. If execution/results are unavailable, retain pending dependencies and allow documentation integration, but do not claim this task's actual capture acceptance or Phase 1 acceptance complete. Prepared tools and failed/partial results cannot satisfy the native/original deliverable.</action>
<acceptance_criteria>Actual returned results are imported and reviewed, or each unavailable result is explicitly pending; strict acceptance can pass only with all required real original/native receipts and human checks. Native Windows, original-DxWnd and Linux remain separate proof categories.</acceptance_criteria>
<verify>
<automated>python3 tools/recon/fidelity_acceptance.py audit --checkpoint dist/fidelity/phase01 --results dist/fidelity/phase01/results --require-complete</automated>
<fails_when>Nonzero exit, any missing case/platform/media/human-review requirement, unresolved assumption affecting acceptance, or missing acceptance=passed result. Expected nonzero while actual evidence is unavailable is an open acceptance dependency, not a successful verification.</fails_when>
<human-check>One combined session: follow checkpoint-session.md, run the original generated copy through identified DxWnd and the port natively on Windows, return results locally, review actual Linux input/audio and paired recordings. Approve only observed case/platform facts; failed/unavailable cases remain open. No earlier fragmented capture request is authorized.</human-check>
</verify>
<done>Required actual original/native captures and review establish acceptance only when strict audit passes; otherwise the exact remaining session dependencies stay open and Phase 1 is not accepted.</done>
</task>
<task type="auto" id="01-07-03">
<name>Integrate local regressions and publish exact evidence status</name>
<files>scripts/test.sh, docs/progress.md, docs/tasks.md, docs/decisions.md, docs/compatibility.md</files>
<read_first>docs/evidence/phase01-baseline.md; actual acceptance.json and test logs; existing scripts/test.sh; current root status reports; all phase SUMMARY evidence limitations.</read_first>
<action>Integrate counted fidelity Python tests, built-in Node viewer checks and standalone observer tests into scripts/test.sh without duplicate full runs or new dependencies. The consolidated runner must reject zero discovered fidelity tests. Run the existing complete local suite and builds/package identity/resource checks required by changed observer/package boundaries, record actual durations/counts and preserve original hashes. Full-suite/native checks may exceed the quick-test budget; report their separately measured duration. Update all four durable status reports with actual implementation/test/native/whole-original facts, receipt IDs, package/source identities and open gaps; no historical totals copied as new results. If task 01-07-02 remains pending, prominently retain EVID-02/EVID-04 and Phase 1 acceptance open and cite the roadmap source-backed continuation exception. Include test/tool completion and prepared materials as their narrower facts. Keep all generated media/packages/traces local and ignored. Primary integration owns verified commits/push to existing Gitea; this plan authoring assignment performs no implementation or commits.</action>
<acceptance_criteria>The complete local suite and original inventory pass with measured positive counts; status documents agree with strict audit; no pending native/original dependency is marked complete; originals/packages/captures remain outside source uploads.</acceptance_criteria>
<verify>
<automated>scripts/test.sh</automated>
<fails_when>Nonzero exit, zero/missing fidelity or viewer/observer test count, failed managed/GPU/resource/preservation check, or missing consolidated completion log.</fails_when>
<automated>python3 tools/recon/inventory.py ../Original --verify docs/original-manifest.json</automated>
<fails_when>Nonzero exit or missing Verified 539 unchanged original files.</fails_when>
</verify>
<done>Local regressions and durable reports truthfully record current proof; Phase 1 acceptance is reported passed only after actual strict original/native acceptance, otherwise remains open.</done>
</task>
</tasks>
<threat_model>
ASVS level 1; unresolved high/critical threats block acceptance.
| Boundary | Description |
|---|---|
| Returned local results → current acceptance | Artifacts and human findings are validated before promotion |
| Prepared checkpoint → user execution | Launch provenance and complete materials are reviewed before handoff |
| Threat ID | Category | Component | Severity | Disposition | Mitigation Plan |
|---|---|---|---|---|---|
| T-01-19 | Spoofing | Strict acceptance audit | high | mitigate | Require actual method/platform/matrix/identities and human review; reject synthetic/Wine/cross-publish/native substitution |
| T-01-20 | Tampering | Returned result import | high | mitigate | Recheck hashes/containment, atomic import, conflicting duplicate rejection and retained diagnostics |
| T-01-21 | Repudiation | Final evidence/status | medium | mitigate | Exact receipt IDs, explicit history and flags; pending dependencies prevent completion claims |
| T-01-SC | Tampering | Package installation | high | mitigate | Existing dependencies only; no new installation or upload service |
</threat_model>
<verification>Task 01-07-01 proves readiness and strict rejection behavior. Task 01-07-02 requires actual combined-session receipts for acceptance. Task 01-07-03 records local regressions and exact passed/open status; it cannot waive missing original/native evidence.</verification>
<success_criteria>Testers can reproduce identified original/port scenarios and inspect exactly what each native platform proves; unavailable execution remains an explicit incomplete acceptance dependency.</success_criteria>
<output>Create .planning/phases/01-reproducible-fidelity-baseline/01-07-SUMMARY.md with prepared versus accepted status, actual receipts and outstanding human dependencies.</output>