Skip to content

feat(tasks): start, block and unblock work from Tasks - #144

Merged
efraespada merged 9 commits into
developfrom
feature/143-start-block-and-unblock-tasks-from-tasks
Nov 19, 2026
Merged

efraespada merged 9 commits into
developfrom
feature/143-start-block-and-unblock-tasks-from-tasks

Conversation

@efraespada

@efraespada efraespada commented Nov 19, 2026 •

Copy link
Copy Markdown
Member

Let members start assigned work, explain a blocker and deliberately resume eligible tasks. Progress confirmation retains the proposed action and exact reason through conflicts and interrupted responses.

What changed

  • Add Start, Block and Unblock through the existing transition policy, current hints and exact reviewed revision. Preserve assignees and require a meaningful bounded multiline blocking reason.
  • Keep current-task review separate from saving. Refresh the list and selected detail after refused progress admission and retire stale rows if that refresh fails.
  • Recover task.transition through recorded authorization and bind each receipt to its frozen task, revision, target and exact reason. Preserve earlier journal entries.
  • Use published ha-ui 0.1.0-next.2 buttons, cards and feedback with English keyboard and Spanish 390 px native touch. Keep task columns within the available width across system fonts.
  • Pin immutable Edge.51 to source 4f79b75d65835037a51b51e3742cd372bc45edfe. Preserve schema 34, all earlier task owners and all nine supplied companion cases.

Validation

  • 1,917 frontend tests pass with all four coverage metrics at 100% globally and per authored file. Strict runtime/catalog typing and the independent coverage audit pass.
  • All 119 compiled source journeys and all 45 rebuilt catalog journeys pass with zero skips, unexpected results or flaky outcomes.
  • The preceding exact-head self-hosted backend campaign passes all 5,529 tests with 100% statement and branch coverage globally and across all 231 modules. The Edge.51 corrections retain those Python runtime bytes. The final package CI repeats the complete inventory.
  • Python tooling/architecture, Node policy, import boundaries, Ruff, mypy, documentation and official action-lock checks pass in the preceding campaign. Current local package acceptance passes all nine tests, including the normal wheel/asset/license guard, with Ruff and documentation checks passing again.
  • Source archive SHA-256 b57247ac5e62686f8ff42b1ac71cbcde5e47ea54ff873b543077db0102e865dc and Linux wheel SHA-256 3fe64c5c5d4d21d6c65538f276bf18805c44d04d084db57d964599b36d48ff0f are independently measured. Git, wheel and installed builder match all 231 Python modules. All four UI files and the complete wheel match local and Linux builds.
  • ARM64 image sha256:0af07f0bfc57d2333767df57c1888f6e9514a3a66419817762e2e21aa6d20680 passes nine actual-image cases in 152.96 seconds. These cover exact declared bytes, native authority and restart, private standalone delivery, actual Edge.5 upgrade/restore, four repeated-SIGTERM cases and all four real-Core compositions.
  • All eight assignment/progress journeys against this exact image pass in 96.53 seconds with zero skips, unexpected results or flaky outcomes.
  • Installed-owner 50-to-51 acceptance passes. The upgrade retains the Desktop task identity, revision 6 and exact saved multiline reason. Both competing-update paths refresh the list and detail together, preserve the proposed reason and require a separate permitted review/save or unavailable-target refresh/cancel. Spanish 390 px native touch covers creation, blocking, unassigned unblocking, assignment and Start. A full stop/start retains both task identities, revisions 11 and 5, the Desktop reason and the same recovered original Mobile operation. The app is stopped and scoped permanent cleanup awaits the owner's action-time confirmation.
  • Final head bf819d718f4986ba2e9ab11eb9afbdaf0b815eb3 passes CI 44518577252, Branch Sync 44518577240 and automated review 44518586121 with zero active findings. Both architecture images pass all 64 journeys.
  • Merged destination f2514e76c3b3e57d167392b873c5260e88bb27a6 retains the reviewed tree ce72f5d766a71c4234555d95841b180959f513be. Its CI 44525242283 and Branch Sync 44525242212 pass. Independently downloaded destination artifacts verify backend coverage, all four frontend metrics at 100% per authored file, 119 source journeys, 45 catalog journeys and 64 image journeys on each architecture, with zero skipped, unexpected or flaky outcomes. Issue ✨🧑‍💻 - Start, block and unblock tasks from Tasks #143 closed automatically.

Review notes

The installed Edge.50 two-tab journey exposed a stale task list after the selected detail had refreshed. Five controller regressions and four compiled journeys reproduced the issue. Edge.51 refreshes both surfaces and preserves the draft and explicit review. Edge.50 retains its original archive, wheel and image identity.

The first package campaign detected stale current-navigation fingerprints. The normal packaging guard reproduced the failure. The current declaration now matches the measured bundle and its normal wheel acceptance passes. Linux mobile CI also exposed an intrinsic grid width exceeding the viewport. Both task grid levels now use zero-minimum tracks. The compiled reload journey waits for the hydrated workspace before selecting its language and follows the standalone authentication return through Overview.

The dark-theme primary-button regression reproduced a contrast ratio of 1.72. Public on-accent tokens correct it, and final journeys check card text and primary controls at 4.5 or above in both themes.

The native publication replaced all nine supplied case identities. Contributor correction 09401f49be3ad10e52c63f935b9355b960ea5c52 restores only the new companion. Independent checks with published SDK 3.10.13 accept its immutable format, reciprocal mapping, nine supplied identities and retained-owner consistency. The final native Commit fails before assessment with validation.evidence-unavailable, reference c68fcb84-14bd-4117-b7e5-ac4d88182c4b. The same job publishes failed Copilot Verification. The maintainer-authorized exception applies to this diagnosed producer failure while every product gate and valid review finding remains required. Producer record, final failed job

The qualification maps all nine supplied cases to executable evidence. Final installed and exact-head results are recorded below.

Closes #143

@docs-page

docs-page Bot commented Nov 19, 2026

Copy link
Copy Markdown

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

docs.page/vypdev/domus~144

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 19, 2026
@vypbot
vypbot self-requested a review November 19, 2026 10:39
@vypbot vypbot added this to vypdev Nov 19, 2026
@vypbot vypbot moved this to In Progress in vypdev Nov 19, 2026
@vypbot
vypbot changed the base branch from develop to master November 19, 2026 10:39
@efraespada efraespada linked an issue Nov 19, 2026 that may be closed by this pull request
1 task done
@vypbot
vypbot changed the base branch from master to develop November 19, 2026 10:39
@vypbot vypbot added the size: XXL Label to indicate a task of size XXL label Nov 19, 2026
@vypbot vypbot added state:reviewing A pull request is being reviewed. and removed state:ai-processing A Copilot agent is analyzing or working on the issue or change. labels Nov 19, 2026
@efraespada

Copy link
Copy Markdown
Member Author

Domus #143 / PR #144 retains the selection failure on the implementation head

Copilot - Commit run 44507910892 fails on 6b666055c94d5288988fc88d9a665c6674996160 before progress assessment. The pinned comparison correctly selects develop 50ddb2d60de4b4a53970ecdde70eb746ade38d30 and the current managed feature head. The final diagnostic is validation.evidence-unavailable, reference 561620bc-725e-4715-8a39-d67eed664c1f, with the action stating that the selected SDD draft could not be verified. The same run publishes the failed Copilot / Verification check. Push Bugbot correctly delegates to PR #144. Exact failed job

The preceding native publication replaced all nine supplied identities. Contributor correction 09401f49be3ad10e52c63f935b9355b960ea5c52 restored the six requirements and nine supplied cases in the new companion. Its content remains byte-identical on the current head, SHA-256 2d7365bc4516776a08ada49acda5a4a18e61d038846779fbdfddca614ec8c0e3. Independent checks with the published 3.10.13 SDK continue to accept format, reciprocal requirement/case mapping, exact supplied identities, repository references and all four retained task owners. The original native publication remains an ancestor and its bot-owned receipt remains present. Earlier producer/consumer reconciliation

The consumer continues under the maintainer-authorized Copilot defect exception while following all exact-head product CI and valid review findings. A separate real packaging failure on the preceding package head was reproduced and corrected by updating the stale current-navigation evidence. The normal wheel acceptance passes, and its checksum exactly equals the independently qualified Linux wheel. Edge.50 retains its exact runtime/archive/wheel/image bytes. Installed-owner acceptance, final product CI and final review are still being followed. Consumer PR

@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 19, 2026
@efraespada
efraespada marked this pull request as ready for review November 19, 2026 11:06
@vypbot vypbot added the state:ai-processing A Copilot agent is analyzing or working on the issue or change. label Nov 19, 2026
@vypbot

vypbot commented Nov 19, 2026 •

Copy link
Copy Markdown

Bugbot: review complete

Current status: No active findings on bf819d7.

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:reviewing A pull request is being reviewed. state:ai-processing A Copilot agent is analyzing or working on the issue or change. labels Nov 19, 2026
@vypbot vypbot added the state:ai-processing A Copilot agent is analyzing or working on the issue or change. label Nov 19, 2026
@efraespada

Copy link
Copy Markdown
Member Author

Domus #143 retains selected-SDD evidence failure on Edge.51 package head

Native Commit run 44518577062 fails on bf819d718f4986ba2e9ab11eb9afbdaf0b815eb3 before assessment with validation.evidence-unavailable, reference c68fcb84-14bd-4117-b7e5-ac4d88182c4b. Job 135540955757 states that the selected SDD draft cannot be verified and publishes the failed Copilot Verification check from the same attempt. Exact job

The corrected companion remains byte-identical at SHA-256 2d7365bc4516776a08ada49acda5a4a18e61d038846779fbdfddca614ec8c0e3. Independent published SDK 3.10.13 checks pass format, exact nine supplied identities, reciprocal requirements, repository references and retained-owner consistency. The initial Action publication and bot receipt remain in branch history. The consumer follows the authorized Copilot-only exception while all product CI and valid review findings remain required. An actual owner-observed stale-list defect in Edge.50 was reproduced and corrected in immutable Edge.51. Consumer PR, preceding occurrence

@vypbot vypbot removed the state:ai-processing A Copilot agent is analyzing or working on the issue or change. label Nov 19, 2026
@efraespada

Copy link
Copy Markdown
Member Author

Exact-head acceptance before ordinary merge

Reviewed head bf819d718f4986ba2e9ab11eb9afbdaf0b815eb3, tree ce72f5d766a71c4234555d95841b180959f513be, has successful complete product CI 44518577252 and Branch Sync 44518577240. Automated review 44518586121 is complete with zero active, reopened, verification-required or unknown findings. CI, Branch Sync, Review

Independent downloaded-artifact audits verify backend coverage and all four frontend metrics at 100% globally and per authored file. Both actual CPU images pass 64 journeys each. Linux passes all 119 compiled source and 45 catalog journeys. Every campaign has zero skipped, unexpected or flaky outcomes. The current backend inventory passes all 5,529 tests and the frontend passes all 1,917 tests.

The immutable installed Edge.51 source, archive, wheel and ARM64 image identities are recorded in this PR. Its separate nine image cases and eight task journeys pass. Actual Home Assistant acceptance covers the 50-to-51 update, current list/detail consistency after two competing updates, retained multiline drafts, separate review/save, unavailable-target refresh/cancel, English keyboard, Spanish 390 px native touch, empty and assigned unblocking, Start, full stop/start, both retained task identities and the same recovered original operation. The application is stopped. Permanent removal of the synthetic household and two tasks awaits the owner's fresh browser-policy confirmation.

The only failed checks are native Commit and its Copilot Verification projection. Their selected-SDD evidence failure occurs before assessment and is diagnosed on this exact head, independently validated and recorded upstream and here. The existing maintainer exception applies to this producer defect. All product checks and the complete automated code review pass. Exact-head producer record, consumer record

The merge uses the ordinary merge path and the exact reviewed head. Destination CI, Branch Sync and native issue closure will be followed before implementation of the next increment.

@efraespada
efraespada merged commit f2514e7 into develop Nov 19, 2026
13 of 15 checks passed
@github-project-automation github-project-automation Bot moved this from In Progress to Done in vypdev Nov 19, 2026
@vypbot vypbot added state:verified The change has passed Copilot verification. and removed state:ready The change is ready for human approval or merge. state:awaiting-maintainer The next action requires a maintainer response or approval. labels Nov 19, 2026
@efraespada

Copy link
Copy Markdown
Member Author

Verified destination acceptance

The ordinary merge is f2514e76c3b3e57d167392b873c5260e88bb27a6. Its tree ce72f5d766a71c4234555d95841b180959f513be is identical to the reviewed head. Issue #143 closed automatically.

  • Destination CI and Branch Sync succeed.
  • Independently downloaded destination artifacts pass the backend coverage guard and verify 100% for all four frontend metrics across all 106 authored files.
  • All 119 source, 45 catalog, 64 amd64 and 64 ARM64 journeys pass with zero skipped, unexpected or flaky results.
  • Installed Edge.51 acceptance and stop/start persistence are recorded above. Its synthetic installation is stopped while the fresh permanent-cleanup confirmation is pending. Edge.50 remains the schema-compatible rollback artifact.

The diagnosed Copilot selected-SDD producer failure and authorized exception remain recorded in the preceding report. Every product CI job and automated review passed before merge.

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.

✨🧑‍💻 - Start, block and unblock tasks from Tasks

2 participants