Skip to content

feat: Add verified household administration workspace (#27) - #28

Merged
efraespada merged 27 commits into
developfrom
feature/27-complete-the-household-administration-workspace-after-the-verified-api-and-controller-checkpoint
Nov 3, 2026
Merged

efraespada merged 27 commits into
developfrom
feature/27-complete-the-household-administration-workspace-after-the-verified-api-and-controller-checkpoint

Conversation

@efraespada

@efraespada efraespada commented Nov 2, 2026 •

Copy link
Copy Markdown
Member

Refs #27. Add the English/Spanish household administration workspace in native Ingress and standalone: verified identity/roster, public aliases, owner-private preferences, household settings, participant profiles/ordinary exceptions and HA administrator mapping. Every command uses current authority, the original exact revision/payload/key and stable participant reference. Changed or missing verified household proof retires private drafts and detached callbacks.

Deliver the workspace as Edge.7. The Supervisor recipe pins runtime 3200bd9278f57f142ed03b54843a38a4138fc0af and its verified archive; addon-edge/artifact.json declares all 151 Python and four UI fingerprints. Edge.5's installed recipe remains byte-identical in a separate non-discoverable compatibility fixture. Schema 9 upgrades preserve supported older data/history; old images refuse new data without changing it.

Edge.7 fixes the prior package's implicit hot-backup policy with a tests-first backup: cold contract. Supervisor stops Domus while copying private SQLite storage. The distinct package version keeps Edge.6's runtime/UI/schema, private listener and Core permission scope. Operator guidance distinguishes readable warm archives, stopped-app captures, prior-state-aware restart and restoration that retains later processing evidence.

Current test/evidence head: 3e10c3935c254115aa4066736d28415a135dc3a9. Five retained identity/profile acceptance boundaries now have explicit assertions: verified/neutral labels in both languages, the exact unavailable-source roster identity set, full actual task/performance authorship across archive/reactivation, no invented recurrence history for genuine pre-8 migrations, and deliberately persisted orphan-profile rejection without repair. Local full backend passes 4,404 tests at 100% supported global/per-module statement/branch coverage across 151 modules; Chromium passes 1,263 tests at 100% of all four metrics across 31 authored runtime files, with independent inventories. Strict frontend types, changed-test Ruff checks and documentation validation pass. Current CI Check passes all ten jobs. Current native review completes all 13 partitions with complete context and no findings; candidate/published/overflow/open/reopened/verification-required/unknown are zero and all seven historical threads remain resolved. The separate current progress scope-clause-limit failure is recorded in copilot#828.

Previous fully verified test/evidence head: e5f08ebe46f1ae3e2f81080746c0fd76c705b9fc. It added six explicit HA directory boundary cases. Runtime, Edge.7 installation definition and artifact fingerprints remain unchanged across both test-only increments. The following hosted results refer to that prior head:

  • CI Check 41700555842 passes all ten applicable jobs. Both amd64 and aarch64 pass 40 container checks and 34 actual-image administration journeys per CPU, zero skips/flakes and no surviving fixtures.
  • Frontend: 1,258 Chromium tests: all four supported metrics100% globally/per-file across 31 runtime files, independently audited; 89 compiled Python/SQLite journeys, 36 built catalog journeys and actual-wheel acceptance. Backend: 4,402 tests, 151 modules, 10,438 statements and 2,928 branches at 100% globally/per-module, independently audited. Tooling: 179 tests, 214 statements and 98 branches at 100%. Strict types, architecture, style, links and unchanged original SDD SDK pass.
  • Prior-head native review 41700555989/job 126142397778 completes 12/12 partitions with complete context and outcome no-findings. Candidate/published/open/reopened/verification-required/unknown counters are zero; all seven historical threads remain resolved.
  • The actual local aarch64 Edge.7 image independently matches all 155 product fingerprints and passes four installer/container checks plus 34 real browser cases. Tests first reproduced missing backup policy. Separate pending-alias journeys preserve canonical pending membership and private defaults, then require explicit activation. Original 19 Unicode boundary variants, 256-participant maximum-label catalog and four-per-CPU compatible application/data rollback cases remain required and passing.

The new provider acceptance covers exactly 256 distinct canonical accounts, preserving order, names, eligibility and the exact own subject at the final position. Distinct 257-account overflow or a malformed 256th account makes the entire directory unavailable. Native credentials never use their own current_user as human fallback; standalone may independently verify only its own subject. All six controls pass against the existing runtime: this strengthens household-admin-C47 and does not claim a new production bug or a complete UI selector acceptance.

On the owner's actual HA, the authorized Edge.7 package is now installed, configured with the local browser origin and running through Ingress with the existing HA sign-in. Chrome dogfooding exercised explicit fresh-household creation, an own-alias change and reversal, saved English/Spanish preferences and summary opt-in/out, a reversible household-name change, and original-result lookup after later changes. Full page reloads and one application restart retained the current household, independent revisions and private preferences; reopening reverified the current HA identity without another login. Participant and access-rule forms were inspected and cancelled without changing authority. With the owner's explicit development-data authorization, the old Edge.3 and Edge.5 app instances were uninstalled; Edge.7 is the only installed Domus app. The prior selected-app cold backup remains a temporary rollback input. This is fresh-install agent dogfooding, not a demonstrated owner-data upgrade, restored owner backup or second-human UX approval. Private owner identifiers and screenshots are not published.

The current assessment-text-limit failure, exact diagnostic and independent no-findings review are recorded in copilot#829. The recurring progress-publication scope failure is reported with exact commit/job/timestamp/reference and preserved state in copilot#828. The typed-JSON false premise and independent controls are in copilot#875. Neither report relaxes product acceptance. Copilot source/resources/configuration/workflows/models/credentials/bounds and gateway remain untouched.

Continue full acceptance on this issue/ref. All 20 owning documents and 186 required cases remain; complete semantic audit, remaining human UX and owner restore/adoption acceptance remain unfinished. The owner understands the initial alias/language/review flow but requests less visible technical detail and immediate access to tasks/calendar; no full UX approval is inferred. Tasks and calendar UI are the next priority in #23 / PR #29. Evidence and limits are in docs/evidence/household-administration-browser.json and docs/household-administration-operations.md. Issue #23 recurrence/calendar, remaining domains, HA services/entities and complete Stable/Edge product remain required. This PR does not claim full product completion.

@docs-page

docs-page Bot commented Nov 2, 2026

Copy link
Copy Markdown

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

docs.page/vypdev/domus~28

Documentation is deployed and generated using docs.page

@vypbot vypbot added the state:ai-processing A Copilot agent is analyzing or working on the issue or change. label Nov 2, 2026
@vypbot
vypbot self-requested a review November 2, 2026 22:08
@vypbot vypbot added this to vypdev Nov 2, 2026
@vypbot vypbot moved this to In Progress in vypdev Nov 2, 2026
@vypbot
vypbot changed the base branch from develop to master November 2, 2026 22:08
@vypbot
vypbot changed the base branch from master to develop November 2, 2026 22:08
@vypbot vypbot added the size: XXL Label to indicate a task of size XXL label Nov 2, 2026
@vypbot

vypbot commented Nov 2, 2026 •

Copy link
Copy Markdown

Bugbot: review complete

Current status: No active findings on 3e10c39.

Pull request · Verified commit · Workflow run

@vypbot vypbot added state:ready The change is ready for human approval or merge. state:awaiting-maintainer The next action requires a maintainer response or approval. and removed state:ai-processing A Copilot agent is analyzing or working on the issue or change. labels Nov 2, 2026
@vypbot vypbot added state:ai-processing A Copilot agent is analyzing or working on the issue or change. and removed state:ai-processing A Copilot agent is analyzing or working on the issue or change. labels Nov 2, 2026
@vypbot vypbot added state:ai-processing A Copilot agent is analyzing or working on the issue or change. and removed state:ai-processing A Copilot agent is analyzing or working on the issue or change. labels Nov 2, 2026
@vypbot vypbot added state:ai-processing A Copilot agent is analyzing or working on the issue or change. and removed state:ai-processing A Copilot agent is analyzing or working on the issue or change. labels Nov 2, 2026
@vypbot vypbot added the state:ai-processing A Copilot agent is analyzing or working on the issue or change. label Nov 3, 2026
@efraespada efraespada changed the title feat: Coordinate household browser lifetimes and recovery (#27) feat: Add verified household administration workspace (#27) Nov 3, 2026
@vypbot vypbot removed the state:ai-processing A Copilot agent is analyzing or working on the issue or change. label Nov 3, 2026
@vypbot vypbot added state:ready The change is ready for human approval or merge. state:awaiting-maintainer The next action requires a maintainer response or approval. and removed state:reviewing A pull request is being reviewed. state:ai-processing A Copilot agent is analyzing or working on the issue or change. labels Nov 3, 2026
@vypbot vypbot added state:ai-processing A Copilot agent is analyzing or working on the issue or change. state:blocked The workflow is blocked and needs human input. and removed state:ready The change is ready for human approval or merge. state:ai-processing A Copilot agent is analyzing or working on the issue or change. labels Nov 3, 2026
@vypbot vypbot added the state:ai-processing A Copilot agent is analyzing or working on the issue or change. label Nov 3, 2026

@vypbot vypbot left a comment •

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

🤖 Bugbot review snapshot

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

Findings

  • medium: Clear drafts when the verified household changes — frontend/src/presentation/domus-administration.ts:43

@vypbot vypbot left a comment •

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

🤖 Bugbot review snapshot

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

Findings

  • medium: Use value assertions for household draft inputs — frontend/tests/e2e/administration.spec.ts:204

@vypbot vypbot left a comment •

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

🤖 Bugbot review snapshot

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

Findings

  • low: Example links point to missing sections — specs/household-administration-browser.md:223

@vypbot vypbot left a comment •

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

🤖 Bugbot review snapshot

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

Findings

  • medium: Wrong-identity test includes the valid first sequence number — tests/python/test_image_channel.py:115

Comment thread tests/python/test_image_channel.py Resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size: XXL Label to indicate a task of size XXL state:verified The change has passed Copilot verification.

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

✨🧑‍💻 - Complete the household administration workspace after the verified API and controller checkpoint

2 participants