spike: expose derived parent status through the API

Open
  • Is something wrong?
#386 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp, openapi
Domain
api

Research direction

Read the Tasks page implementation and the API and MCP status behavior after the monorepo move (#397) and the MCP change ships. Compare how the journal and MCP represent derived parent status, decide how stored status and direct parent status changes should behave, and write a recommendation. Track any implementation as separate follow-up issues.

Written by the indexing model from the issue text.

Description

enhancement

Waits for the monorepo move (#397). This changes the API, so it is built after the assistant moves into this repo and the MCP change ships in the same PR (checked by the integration and error-code tests).

Summary

Decide whether derived parent status should move into the API once the Tasks page version has had real use.

Questions to answer

  • Should the journal and MCP show the same derived status?
  • What should happen to a parent's stored status?
  • Should the API reject direct status changes on parents with open subtasks?

Outcome

A recommendation, with any follow-up work in separate issues.

Part of #388. Depends on #385. From the #382 spike.

Dominant language
C#
Stars
1
Forks
0
Avg merge
2h 2m
Merged PRs (30d)
98

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nevridge/TaskFlow

All issues in nevridge/TaskFlow

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.