[efraespada]

Overview shows the signed-in member’s completed tasks and posted earned points for the current Family week. The server derives the week in the household’s time zone and applies the same read permissions as Family. The card offers a retry when its read fails and links to Family for the full report, including points pending verification or posting.

Edge.27 pins runtime 979319d1a874f21f2dbe525a3108034ecd0ff0d4. In a disposable Home Assistant Ingress household, Overview started at zero and showed one completed task and 2.25 points after the award posted. The same summary displayed 2,25 in Spanish at 390 px. Both the English keyboard link and the Spanish touch link focused Family. Reopening the task produced a linked −2,25 reversal. Overview retained the historical completion count and returned to 0,00 earned points. The disposable app, its private data, and its repository source were removed.

All six specification cases ran independently in Ingress and standalone, plus the separate scope-revocation test in both modes. All 14 tests passed. The synchronized frontend passed 1,716 tests with full coverage of 82 files. The independently built wheel matched the current UI fingerprints and passed the packaging checks.

Edge.28 adds a refresh when the household week changes while Overview is open. A mounted-page regression crosses Monday midnight in Europe/Madrid and checks that the summary rereads exactly once while the session stays open. The corrected Edge.28 package also ran in a fresh Supervisor household using Europe/Madrid. It showed the empty summary, then one completed task and the posted award in English and Spanish. The temporary app, data, and source were removed after the check.

Closes #105

Published specification · Candidate CI · Code review

[docs-page]

To preview the documentation for this pull request, visit the following URL:

docs.page/vypdev/domus~110

Documentation is deployed and generated using docs.page

[efraespada]

CI Check passed at 7f9726a327bf9f23e006172315f71da410bb79ac, including all 54 actual-image browser journeys on amd64 and ARM64. The Branch Sync merge preserved the installed Edge.22 runtime, artifact pins and published SDD.

The commit and pull request wrappers exited early for the Branch Sync PAT actor. Actual verification and review remain pending after the earlier selected-SDD verification failure linked in this PR.

[vypbot]

Bugbot: review complete

Current status: No active findings on 74ba1a5.

Pull request · Verified commit · Workflow run

[efraespada]

At 149bf2443909067c41921eb98a92ab46298b11bd, CI Check
passed all suites, including 54 actual-image journeys on each architecture.
The review completed with no findings.
The current develop merge and installed-evidence commit preserved the
Edge.22 runtime and the Action-published SDD.

Verification repeated
the selected-SDD validation.evidence-unavailable failure linked above.
The pull request is waiting for that verification.

[efraespada]

The candidate Branch Sync is waiting in the queue affected by the stranded workflow run, which remains queued with zero jobs. The temporary exception documented for Domus applies while GitHub Support clears that run. The stalled develop Branch Sync was cancelled to release its runner after confirming that develop CI had passed. The native synchronization receipt confirms that the managed branch includes the verified develop commit 3ea1ac0a464c8487b00fa25371db72625804c94e. The base CI passed, and the expected merge tree matches candidate tree 3d0c9106d1890ce2315cdee8d7aedf4ec86f92f8.

The Commit progress check on 74ba1a529fde548723639e2ee9025ed884e67f60 reproduces Copilot #959. Issue #105 retains an optional unselected seed. The Action publication receipt records the generated SDD at f4b8699e8cc423c07fb1dc3de20f1181fa82f574. That commit is an ancestor of the candidate and both revisions have the same specs/points-rewards.md blob f83a06e86dd9e6894878c16ed4c77d5b8eb602f4. The specification catalog and executable qualification passed locally. The Commit failure applies to progress assessment. Full candidate CI and the independent code review remain the implementation gates.

[vypbot]

Current status: All findings originating in this review are resolved.
Last reconciled on 74ba1a5. See aggregate Bugbot status.

🤖 Bugbot review snapshot

Bugbot reported 1 potential problem when commit 26dc3dd was analyzed. This snapshot is historical; use the status block above for current state. 1 finding is linked to changed code.

Findings

• low: Weekly summary can remain on the previous week after rollover — frontend/src/composition/entry-page.ts:462

[vypbot]

Current status: All findings originating in this review are resolved.
Last reconciled on 74ba1a5. See aggregate Bugbot status.

🤖 Bugbot review snapshot

Bugbot reported 1 potential problem when commit 58a2361 was analyzed. This snapshot is historical; use the status block above for current state. 1 finding is linked to changed code.

Findings

• low: Six Overview cases are covered by one test — tests/backend/test_family_overview.py:50