Current verification and historical findings
Current phase: the complete frontend prototype and evidence are published. Independent product visual acceptance is pending until both fresh Luna xhigh reports return and required corrections are accepted. The canonical44-criterion contract has not been marked complete from counts or automated tests.
Current decisive evidence
- Full hosted body verification:2636 distinct current hosted paths passed SHA-256 readback, including complete downloaded ZIPs, every final media file, source and static runtime.
- Independent archive integrity:11995 readable capture contexts,416 additional full-page references,791 declared ZIPs and3147 supplementary legacy contexts have exact original/entry byte equality, decode and metadata coverage.
- Native-pixel preservation:The initial 12001 capture contexts retained 9505 unique original PNG identities in 595 lossless containers. A local append of 872 fresh deployed correction contexts now preserves 12873 contexts and 9756 unique hashes in 611 containers, retaining every earlier index and PNG container unchanged. This appended viewer is awaiting the next assembled publication. Every saved crop was redecoded and compared to original pixels. Packing is not visual acceptance.
- Public evidence-viewer behavior:7/7 checks passed at the hosted URL. Fresh source review passed. Visual viewer review found no material defect in the internal viewer. These are Terra/root checks, not substitutes for Luna customer acceptance.
- Complete14-day loop:114/114 checks passed. Edge states:6/6. Funnel and canvas:8/8. Failed video replacement:20/20. All are browser-local frontend checks.
Historical reports, with their actual resolutions
The complete index deliberately retains earlier failures and corrections. A historical STALLED or NEEDS-CHANGES label does not describe the final state of the affected action when a later decisive correction follows.
| Historical finding | Correction | Current decisive evidence |
|---|---|---|
| Initial code findings: context guard, truthful save status, stale state | Luna Max state fixes | 114-day-loop checks and6 edge-state checks |
| Video replacement could commit new bytes while metadata save failed | Revision-specific IndexedDB commit after write, prior revision retained on failure | Fresh final-state correction review PASS and20 replacement checks |
| Legacy master appeared to have17 controls or blank child previews | Parent wrapper suppresses embedded toolbars and shortcuts, retains standalone sources, correctly loads lazy frames | 29 actual decoded child documents, one fixed outer toolbar, exact267 saved provider critiques, six fresh1280px outer-marker states |
| Source-content audit flagged51 email/day wording cases | Durable email/content corrections plus bounded landing-time clarification | 116 complete final A/B versions, unchanged six source modules, fresh deployed section/state captures. Independent visual/source acceptance remains pending |
| Raw custom-domain source hashes differed for three legacy email pages | Exact Cloudflare email decoding and normalized-source comparison | 137/137 staged and pinned child files preserve original hashes. Only known custom-domain obfuscation varies |
| First evidence upload exceeded the helper's180-second timeout | Narrow staged restore, real provider-state check, task-local1200-second allowance | Successful493e42f4 deployment,827 unrelated roots replayed and16769 unrelated files unchanged |
| First expanded-card helper measured the whole legacy collection | Exclude the failed round, measure the exact selected card and its source pre | 3141 corrected native captures cover all267 assets. Invalid initial captures are not acceptance evidence |
Lifecycle boundaries
Review publication and267 persisted legacy critiques are actual remote changes. Participant video/state and expert sample replies are local browser demonstrations. Checkout, access, notification and booking are frontend simulations. No real payment, uploaded participant video, client email or live campaign was executed. The Rita email remains an unsent draft. Pilot price, capacity, daily workload, actual recordings, dates and real consultation availability remain proposals or source gaps.
Fresh review findings being resolved
Partition B completed its initial visual/source review and identified eight native-image failures across days 7, 9, 12 and 13. Two additional day-12 infographic headline improvements are included in the correction package. Ten actual native replacement outputs were integrated and deployed at the same stable journey URL. Every final image was fully downloaded and hash-checked on the host. The fresh postdeployment visual/source acceptance is still pending. The parent preserved all ten originals and 60 deployed-before capture contexts.
The parent also found an observation attached to the wrong visible page in the initial B table. A bounded correction was assigned. That initial table is not accepted as final evidence. No board criterion was marked complete from it. Fresh deployed after captures and independent observations are still required after the image changes.
Actual inspection recovery
The corrected partition-B report withdrew its earlier full-inspection claim. Only544 raster hashes have fresh viewing receipts, while2669 remained unviewed. The parent rejected the unsupported claim and assigned two new fresh Luna xhigh reviewers disjoint immutable queues of1334 and1335 hashes. Each also receives genuinely fresh postdeployment imagery for its assigned correction family. No criterion is marked complete until actual inspections and necessary repairs are finished.
Ten new native image corrections are integrated and published with exact previous originals and narrow restore instructions retained. All99 nonimage customer HTML/runtime files are byte unchanged. The cached provider-original files were unavailable at previously recorded paths. The83 missing task-owned cache paths were restored from exact previously verified original copies. The recovery does not claim a new provider generation. Current inventory/hash/prompt/native-output checks pass83/83.
Existing Cloudflare delivery transform
The custom domain adds email-obfuscation markup for three sample [email protected] addresses in the preserved September master. Its current pinned raw source remains byte exact. The task-local publisher accepts this one known task-owned delivery transform only when decoding restores the entire exact source and the pinned raw source also matches. The actual comparator rejected deliberately changed source and pinned-response fixtures. No source difference or unrelated route is waived, and the canonical publishing skill is unchanged.
Partition A evidence correction and product repair scope
The finished initial A report contains 1035 generic primary observation templates. Direct parent image views found two templates describing controls or metadata absent from their cited screenshot. The initial all-inspected completion claim is not accepted as decisive proof. One bounded observation correction requires truthful pixel-specific notes and actual view receipts, with original artifacts retained as history. No criterion was checked from the unsupported claim.
Specific confirmed findings are queued in a separate Luna Max repair package: the open free-A FAQ indicator, visible English native file-picker labels, and explicit proposal qualification in standalone ad previews and packs. The reviewed ad hooks, captions and native rasters remain matched to their genuine pre-generation critiques. The advertising concepts are for the proposed offer, not an active campaign or accepted daily-service obligation. Suspected legacy review-panel overlaps require comparison with actual pixels and the supplied interaction pattern before any wrapper change. An old legacy first-screen capture at scrollY=132 is retained as a scrolled reference, with a genuine fresh scrollY=0 capture required.
Shared-host routing recovery
A later production deployment at 07:21 UTC replaced the earlier pinned build as the custom-domain target. The expected customer HTML still has exact byte equality at the clean URL and the earlier b3f6da18 permalink, but direct .html URLs now return the host catalogue rather than the required screen. This invalidated the first focused flow-before-repair capture attempt, which produced zero accepted screenshots. The failed receipt is retained. The assembled route is being republished with live-root preservation preflight and the existing static-routing configuration. Actual postpublication HTML routing and complete bytes must be rechecked before acceptance.