Repository navigation
Description
Is there an existing issue or feature request for this?
- I have searched the existing issues and feature requests.
What area does this improvement affect?
User Interface
What actions does this improvement affect?
No response
Description of the idea or improvement
Expose the existing protected assignment command in the Tasks workspace. A member
with current task-management authority can select one or more active household
members, review an existing assignment, replace its planned assignees, and release
work to the shared pool where the task state permits an empty assignment.
Use the existing task detail and its server-derived assign action to discover
the control. Present household member names through authorized member discovery
and use the current selected task revision for every deliberate save. Use the
published @vypdev/ha-ui@0.1.0-next.2 controls and the existing task request journal.
Implement the accepted assignment behavior in specs/household-tasks.md
(household-tasks-R3) and specs/task-execution-foundation.md (TEF-03, assignment
and role-default sections). A focused owning companion such as
specs/task-assignment-interface.md can describe the UI and recovery delta and its
case inventory. Retain the existing owning contracts and case identities.
Current limitations or challenges
The rendered Tasks workspace currently focuses on self-claiming and completion.
Assignment management requires the typed backend API, whose task detail advertises
assign. Household task managers need discoverable controls for distributing work
and releasing an assignment in that workspace.
The selected source already provides the relevant command, authorization,
revision checks, atomic operation receipts and member reads. The increment should
connect those normal entry points to a usable, recoverable interface.
Expected impact
Household task managers can distribute and rebalance planned work using the same
workspace in which members claim, perform and review it. The interface explains
the current responsibility, handles a competing update deliberately, and preserves
a recoverable original request after an interrupted response.
Required behavior follows the accepted task contracts.
- Offer the editor when the selected task's current server-derived actions permit
assignment. Load authorized household member options and show the current
selection using readable names and accessible labels. - Submit canonical household member identities through the existing assignment
endpoint with the selected expected revision. Support multiple assignees and
the accepted unique-member limit of 32. Apply current state-machine rules to
release, including the existing in-progress constraint. - Resolve current task-management authority at the command boundary, including
revocation, member/profile exceptions and household scope. Use the established
self-claim journey for eligible restricted members. - When another change wins, show the current task and retain the local selection
for an explicit review and deliberate retry. A saved request freezes its key,
body and scope so recovery identifies the original operation. - Distinguish loading, empty member discovery, a read failure, denied access,
invalid selection, conflict, an uncertain response and a confirmed assignment.
Retain the selected members when recovery is available. - Make the complete English/Spanish desktop-keyboard and narrow-screen touch
journeys usable, including focus, labels, cancellation, retry and status
feedback.
The minimum companion acceptance inventory contains nine distinct cases.
| Case | Observable acceptance |
|---|---|
| task-assignment-interface-C01 | An authorized task manager selects one or multiple active members and observes the committed planned assignment after refresh. |
| task-assignment-interface-C02 | The manager replaces an existing assignment and releases a supported task to the shared pool. An in-progress task enforces its required assignee set. |
| task-assignment-interface-C03 | Current authority and scope govern the editor and direct command. Restricted, denied, revoked and foreign-household attempts receive the appropriate denial. |
| task-assignment-interface-C04 | Member options and current selections use authorized discovery. Empty, unavailable, inactive and outdated options have explicit recovery and admission outcomes. |
| task-assignment-interface-C05 | A competing revision produces a conflict. Reviewing the current task retains the draft selection and requires a deliberate save using the refreshed revision. |
| task-assignment-interface-C06 | A lost response is resolved through the same frozen key and body. Retrying or recovering returns the original recorded assignment once. |
| task-assignment-interface-C07 | Supported member-count boundaries and malformed, duplicate or foreign identities are validated through the normal entry points. |
| task-assignment-interface-C08 | English keyboard and Spanish mobile touch journeys cover editing, cancellation, save, conflict review and retry with understandable focus and feedback. |
| task-assignment-interface-C09 | Ingress and standalone retain the assigned task and original operation after restart, with an inspectable audit and the accepted completion/performer behavior. |
Alternatives considered
No response
Version of copilot
v3.10.13
Additional context or comments
The intended base is develop at
6c7428dd7101a375802b67c3c7e8c2513b2c2053, with the exact gates qualified below.
Its exact CI and Branch Sync have passed, and #139 is closed at 100%.
Base CI,
base Branch Sync
Wait for native admission and the Action's exact managed branch and SDD publication
before implementing.
Verified source entry points provide the implementation context.
backend/src/domus/entrypoints/task_http.pyexposes
PUT /api/v1/tasks/occurrences/{occurrence_id}/assignment.TaskCommands.assignandTaskCommandAuthorizationown the protected write.TaskQueries._actionsadvertisesassignfor currently eligible task managers.HouseholdRosterQueries.rosterand
GET /api/v1/administration/rosterprovide bounded, permission-scoped members,
presentation aliases and availability-aware provider names.AdministrationServer.roster, the existing roster decoder and the public
Rosterrepresentation provide reusable frontend discovery boundaries.frontend/src/presentation/domus-tasks.tsrenders self-claim, completion and
review.TaskServer,TaskController,TaskJournalPortand the HTTP adapter
provide the existing request and recovery boundaries to extend.
Maintain complete global and per-file supported coverage, both deployment targets,
English and Spanish, actual amd64/ARM64 images and installed Edge acceptance.
Qualify concurrent updates, original-operation recovery, denied writes, restart
and restore through the existing durable task command. Determine migration needs
from the implementation evidence. Keep the workflow placement and released action
version policy and the exact published ha-ui dependency.
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity
[-]Assign and release household tasks from the Tasks workspace[/-][+]✨ - Assign and release household tasks from the Tasks workspace[/+]vypbot commentedon Nov 19, 2026
Hi! I’m @vypbot, the Copilot assistant for this repository.
I can answer questions, explain the codebase, propose implementation and test plans, review issues and pull requests for potential bugs or security problems, and help authorized maintainers apply changes.
Try
/copilot helpto see the available commands, or mention @vypbot with your question.vypbot commentedon Nov 19, 2026
SDD work status
Current status: The SDD is published. Implementation requires active admission and verified branch readiness.
SDD:
specs/task-assignment-interface.md· Branch:feature/141-assign-and-release-household-tasks-from-the-tasks-workspace· First commit:2f08cc89d91749d8a07d9870c9133bd25aa21553Links: SDD · Branch · Commit
26 remaining items
Merge pull request #142 from vypdev/feature/141-assign-and-release-ho…
vypbot commentedon Nov 19, 2026
Issue closed: synchronization recommendation retired
No branch synchronization is required for this closed issue.
The previous recommendation is historical. Issue closure does not certify that the branches are synchronized.
efraespada commentedon Nov 19, 2026
Destination verification and installed acceptance
PR #142 merged normally into develop as
50ddb2d60de4b4a53970ecdde70eb746ade38d30. Its tree480913a93a3fd4818109c2134d5a4a9d49601751exactly matches reviewed head960431df0b682be6d97292837f11f9daf08faf12. All 16 applicable checks passed on that reviewed head with zero review threads. Native review marks the unchanged-assignment finding fixed.Destination CI passes, including both CPU container and actual-image browser suites. Destination Branch Sync passes on the same merge commit. Issue #141 is closed at 100%. CI, Branch Sync
Installed Edge.49 passed English keyboard and Spanish 390 px touch assignment journeys, unchanged-selection guards, cancellation, replacement, release, two-tab conflict review and light/dark legibility. Upgrading the existing QA installation preserved both original task identities. After stop and restart, the desktop task retained assigned revision 8 and the mobile task assigned revision 6. Saved-request recovery returned its original assignment operation. The final controlled stop reached Home Assistant's
Detenidostate. Nine isolated pinned-image cases separately require explicit cleanup and zero process exit.Fresh action-time confirmation authorized removal of the upgraded Edge.49 installation and the locally encrypted Edge.48 rollback backup created during update. Cleanup removed the three owned Edge.46, Edge.47 and Edge.49 QA apps, their three synthetic households, six test tasks and three issue sources. The owned 50.53 MB backup
dcea32a3was removed. Home Assistant shows its original four Domus sources, fourteen installed apps and six app-update backups.The local current Edge.49 image and one-generation Edge.48 rollback remain pinned with their verified source archives and wheels. Completed test fixtures, downloaded browser profiles, old Edge.46/47 images, stopped wheel containers and unused builder tags were retired with protected source and evidence hashes rechecked.
An earlier local browser campaign omitted the shared browser lock and collided with the historical ARM64 CI campaign. Subsequent local browser commands acquire the shared lock. The final reviewed head and destination commit both pass the complete architecture suites.