docs(api): TRA-816 — tag-cascade soft-delete docs#189
Merged
Conversation
added 4 commits
May 23, 2026 08:34
… tags Companion docs change for platform PR #397. Narrow scope: one changelog entry under v1.0 Launch and one Tag CRUD sentence in resource-identifiers.md noting that parent soft-delete cascades to attached tag rows in the same transaction. No errors.md, data-model.md, design-notes.md, or spec changes — the documented contract was already the post-fix shape; runtime is now matching it.
Two edits in docs/api/: one Tag CRUD sentence in resource-identifiers plus one new entry at the top of the v1.0 Launch section of the changelog. Plus build verification and PR open.
… rows One sentence added to the Tag CRUD section: when a parent asset or location is soft-deleted, its attached tag rows are soft-deleted in the same transaction with the same deleted_at, so the (org_id, tag_type, value) natural-key slot is released for immediate reattachment on another entity in the same org. Cross-links the existing soft-delete visibility section for the read-side counterpart.
New entry under v1.0 Launch: parent soft-delete now cascades to attached tag rows, the existing orphan footprint is swept by the release migration, and the conflict-detail join filter ensures soft-deleted parent names cannot leak into 409 detail strings. Frames the fix as bringing runtime in line with the existing soft-delete-frees-the-handle contract on the Tag CRUD page.
|
🚀 Preview Deployment Update ✅ This PR has been successfully merged into the preview branch. The preview environment will update shortly at: https://docs.preview.trakrf.id |
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
1 participant
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
Docs companion to platform PR trakrf/platform#397 (TRA-816, merged). Narrow scope:
## v1.0 — Launch (TBD)describing the parent-soft-delete cascade to attached tags, the one-shot sweep migration, and the conflict-detail join filter.docs/api/resource-identifiers.mdTag CRUD section noting the cascade and cross-linking the existing soft-delete-visibility paragraph.The documented contract on the Tag CRUD page already said the natural-key slot is freed on soft-delete; the platform was failing to match that on the parent-cascade path. These edits close the inference gap and log the fix.
Spec:
superpowers/specs/2026-05-23-tra-816-tag-cascade-design.mdPlan:
superpowers/plans/2026-05-23-tra-816-tag-cascade.mdCloses TRA-816.
Test plan
pnpm buildsucceeds with no broken internal links.git grepaudit: no stale prose contradicts the new cascade contract; the existing "cascade is not supported" hits onDELETE /locationsare about bulk hard-cascade, a separate concept.🤖 Generated with Claude Code