feat(desktop): add Work Board Phase 3 start-task spike - #4598
Open
somewan820 wants to merge 2 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Implements the thin Work Board Phase 3 validation spike for #2560.
Start taskpath for project-scoped Work Board items whose target resolves to one available, non-archived Host/project target.linkedSessionsreference only after a projected first-send outcome.The experiment is enabled only in a development renderer with:
This is intentionally not a persisted user setting. The goal is maintainer/contributor dogfooding before deciding whether to productize the entry and continue later Work Board phases.
Verification
npm test: 1580 passed, 12 skipped; runtime-host and other relevant suites passed.npm --workspace @maka/desktop run build:main: passed.git diff --check: passed.The storage workspace test run remains affected by the existing sandbox
EPERM chmodrestriction under~/Library/Application Support/Maka/~/Library/Caches/Maka; this is environmental and unrelated to the changed Work Board behavior.Generated-by: Codex
AI use
Codex assisted with implementation, review, and test execution. The contributor reviewed the resulting changes and owns the final PR.