Development record
abcd intent plan writes a draft's kind from the corpus loaded before the intent mint lock (Plan in internal/core/intent/lifecycle.go reads it.Kind and it.SpecID from the pre-lock corpus while the bytes it rewrites are read under the lock), so a reclassify landing in the window that makes the draft a bundle-member is overwritten: the planned record carries kind: standalone beside bundle: <name>, a pairing no verb otherwise writes.
issueresolvedminoriss-2609261218301461
abcd intent plan writes a draft's kind from the corpus loaded before the intent mint lock (Plan in internal/core/intent/lifecycle.go reads it.Kind and it.SpecID from the pre-lock corpus while the bytes it rewrites are read under the lock), so a reclassify landing in the window that makes the draft a bundle-member is overwritten: the planned record carries kind: standalone beside bundle: <name>, a pairing no verb otherwise writes.
Grounds
- pursued: we expect Plan's result to equal the result of the reclassify and the plan run one after the other; shown wrong if a planned record ever carries kind: standalone beside a bundle name
Frontmatter
| id | iss-2609261218301461 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2609261218301461-abcd-intent-plan-writes-a-draft-s-kind.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2609261232176189abcd intent plan on a planned record with no spec (linkPlannedSpec in internal/core/intent/lifecycle.go) writes the record's kind from the corpus loaded before the intent mint lock while rewriting bytes read under it, so a reclassify landing in the window that makes the record a bundle-member is overwritten: the record carries kind: standalone beside bundle: <name>. The draft branch of Plan had the same shape (iss-2609261218301461); this is its in-place twin.