feat(recurrence): link a relapse to the same issue's timeline (R-05/E-01)#44
Open
ChelseaKR wants to merge 1 commit into
Open
feat(recurrence): link a relapse to the same issue's timeline (R-05/E-01)#44ChelseaKR wants to merge 1 commit into
ChelseaKR wants to merge 1 commit into
Conversation
…-01)
A relapsed condition should attach to the SAME issue's history as a
recurrence and reopen that issue, instead of forcing a new orphan issue.
This fits entirely within the existing CRDT shapes, so there is no schema
or version change and merge semantics are untouched.
- model: `CaseDocument.record_recurrence(issue_id, text="")` appends a
`kind="recurrence"` timeline entry and sets the issue's LWW status
register back to "open" with a fresh clock stamp; raises on unknown id.
- cli: new `habitable recur --vault ... --issue ID [--text ...]` command.
- appserver: `AppServer.recur` action + `POST /api/issues/<id>/recur`
route returning {entry_id, status: "open"}; 4xx on unknown issue.
- app: "This happened again" button on each issue that POSTs to the recur
endpoint and refreshes status; EN/ES strings (issue_recur,
msg_recur_added) kept at parity.
- tests: model (append + reopen + unknown-issue + merge round-trip),
appserver (endpoint + status reflects reopen/recurrence + 4xx), and a
CLI test for `recur`.
- docs: mark R-05/E-01 done in the persona feedback tables and move them
from deferred to code-validated in the execution log.
Validated: make test (203 passed), make type (mypy --strict clean),
make i18n (G1/G3/G5/G6 green). Ruff clean on all touched files.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
2 participants
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.
A relapsed condition should attach to the SAME issue's history as a
recurrence and reopen that issue, instead of forcing a new orphan issue.
This fits entirely within the existing CRDT shapes, so there is no schema
or version change and merge semantics are untouched.
CaseDocument.record_recurrence(issue_id, text="")appends akind="recurrence"timeline entry and sets the issue's LWW statusregister back to "open" with a fresh clock stamp; raises on unknown id.
habitable recur --vault ... --issue ID [--text ...]command.AppServer.recuraction +POST /api/issues/<id>/recurroute returning {entry_id, status: "open"}; 4xx on unknown issue.
endpoint and refreshes status; EN/ES strings (issue_recur,
msg_recur_added) kept at parity.
appserver (endpoint + status reflects reopen/recurrence + 4xx), and a
CLI test for
recur.from deferred to code-validated in the execution log.
Validated: make test (203 passed), make type (mypy --strict clean),
make i18n (G1/G3/G5/G6 green). Ruff clean on all touched files.
Co-Authored-By: Claude Fable 5 noreply@anthropic.com
Backfill PR for a completed roadmap item (
roadmap/recurrence-modeling-r-05-e-01, 1 commit(s) overmain). Part of the portfolio roadmap batch.