[CHORE] Delete the core-import-media review bucket S-C59 recorded as gone - #431
Open
justin13888 wants to merge 3 commits into
Open
Conversation
S-C59 recorded core-import-media as deleted without deleting it: the directory quarantined capsule_core::exif and the import executor's cancellation/progress halves, all three of which were rebuilt live and newer than the snapshot beside them, making it a stale twin rather than a quarantine. Remove the directory, its ROADMAP.md row, and reword the two import/pipeline.md citations that named it in the present tense to point at the live modules instead.
Follows the repo convention of citing the landing commit's short sha in a slice's detail block once the work described actually happened.
5 tasks
…map-398' into chore/delete-core-import-media-bucket-423
Deploying capsule with
|
| Latest commit: |
8486a5c
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://6017059e.capsule-22k.pages.dev |
| Branch Preview URL: | https://chore-delete-core-import-med.capsule-22k.pages.dev |
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.
Description
S-C59decided thelegacy-review/core-import-mediabucket should be deleted — it quarantinedcapsule_core::exifand the import executor's cancellation/progress halves, all three of whichwere rebuilt live and are newer in
capsule-corethan the snapshot beside them — and recordedthe decision as done without performing it. PR #422 corrected the tracker to say the bucket
exists rather than delete it, because deletion needed edits outside that lane's manifest. This
PR performs the deletion
S-C59recorded:git rm -r legacy-review/core-import-media.capsule-docs/src/content/docs/design/import/pipeline.mdcitations (theStatus noteand theexecute()contract bullet) to name the live successor modules(
capsule_core::exif,capsule_core::import::{executor_cancellation, progress}) instead ofthe now-deleted review bucket.
SLICES.md's intro paragraph, theRETIREDArea-table cell,S-B2's deliverablesentence, and the
S-C59detail-block correction note to describe the deletion in the pasttense and cite the deleting commit's short sha.
ROADMAP.md'slegacy-review/core-import-mediareview-bucket row —check-roadmap.mjskeys review-bucket rows on
legacy-review/*/directories, so an orphan row would failcheck-docs-truth.legacy-review/README.mddoes not list buckets by name (it is a generic policy notice), so itneeded no change.
A repo-wide grep for
core-import-mediaafter these edits turns up only past-tense, commit-likenarrative (the
S-C59history inSLICES.mdand the historicalS-G4"was moved to" note),which the issue's "done when" explicitly allows.
Validation
mise run check-docs-truth— pass.roadmap: 46 package(s) checked, all rows resolve.(matches the issue's stated expectation of 46 packages once the orphan row is gone).
mise run lint-check-md— pass.0 issues in 0 files(171 files linted).mise run architecture-check— pass.Rust architecture boundaries are intact.mise run check-docs— pass (format-check-docs,lint-check-docs,test-docs— 97 tests,build-docs— Astro build + link validation, all green). Requiredbun installincapsule-docs/first; the worktree had nonode_modules.mise run check-rust— pass. fmt, clippy (workspace + FFI, strict flags),i18n-check,i18n-guard,openapi-check-kynos,architecture-check,license-check,translate-readme-check,build-rust,build-check-wasm,build-ffi,lint-check-ffi,gen-bindings(surface check passed),verify-examples(28 tests passed acrosscapsule-core/capsule-sdk) all green, exit code 0.mise run test-rust— pass.160 tests run: 160 passed, 0 skipped.Risks and rollout
Docs/tracker-only change plus a
legacy-review/deletion; no Rust, client, or generated-artifactcode is touched.
legacy-review/is explicitly non-buildable reference material with disabledCargo manifests, so its removal cannot affect any build. Rollback is a straight
git revert.Related Issues
Closes #423
Decisions taken
Issue 423 - cleanup: delete legacy-review/core-import-media, the stale twin S-C59 recorded as gone
Plan: v1 (orchestrator, from lane #398's stop report: the deletion dangles present-tense citations at capsule-docs/src/content/docs/design/import/pipeline.md:54 and :129 and SLICES.md:708, which were outside #398's manifest)
Branch: chore/delete-core-import-media-bucket-423
Base: docs/reset-trackers-and-add-roadmap-398 (head of PR #422, 1043a41), stacked; the PR targets that branch
Worktree: /var/mnt/scratch/golem/dev/Capsulsaurus/Capsule.worktrees/Capsule-chore-delete-core-import-media-bucket-423
Cause: S-C59 (SLICES.md:13-21) records the core-import-media bucket as gone because its contents (capsule_core::exif, import/{executor_cancellation,progress}.rs) were rebuilt live; the directory was recreated or never removed. PR #422 corrected the tracker to say it exists; this lane makes the tracker's original claim true instead.
Touches: legacy-review/core-import-media/** (deleted), capsule-docs/src/content/docs/design/import/pipeline.md (:54, :129 — the two sentences that cite the bucket in the present tense; reword to name the live modules), SLICES.md (:708 sentence in the S-B10/lane-B prose that cites the bucket; the S-C59 detail-block note PR #422 added saying the bucket exists → say it was deleted in this change), ROADMAP.md (remove the core-import-media review-bucket row — the roadmap check keys review buckets on legacy-review/*/ so the row must go with the directory), legacy-review/README.md if it lists the buckets
Will not: touch any other legacy-review bucket, capsule-core/**, or any other SLICES.md row
Lane: serialised behind #398 (ROADMAP.md, SLICES.md S-C59 note). Parallel with #400 (both edit ROADMAP.md rows — distinct rows; and SLICES.md — distinct regions).
Settled: Base = head of PR #418 → stacks on #398.
Decisions taken.
Deliverable boundary — delete the bucket and repoint its three citations.
Taken: Whole issue; it is one git rm plus three prose edits and one ROADMAP row.
Rejected: Keep the bucket and leave the tracker saying it exists (the state PR [DOCS] Reset the trackers to the tree, and add a checked ROADMAP.md #422 left) - quarantining a stale twin of live code is what S-C59 argued against, and the tracker's Sequencing section already tells the reader the twin is gone.
Reverses: git revert.
Filed: -
Scope of the SLICES.md reword — corrected every present-tense citation of the bucket found by grep, not only the two the record's
Touchesline names.Taken: Also reworded the intro paragraph (the "Four buckets" sentence) and the
RETIREDArea-table cell, both of which named the bucket as still existing / awaiting deletion, in addition to the S-B2 deliverable sentence and the S-C59 correction note.Rejected: Editing only the two sentences the record's
Touchesline lists verbatim — that would leave two other present-tense claims ("Four ... buckets sit in the tree", "awaiting deletion (cleanup: delete legacy-review/core-import-media, the stale twin S-C59 recorded as gone #423)") false the moment this PR merges, and the issue's "done when" requires no present-tense citation anywhere.Reverses: git revert (or re-apply the narrower two-sentence edit and drop the other two).
Filed: -
S-C59 note's commit-sha citation — recorded the actual short sha of the deleting commit as a second commit, rather than leaving a placeholder or omitting it.
Taken: Committed the deletion + all prose except the sha citation first (
b51639b1), then added a second commit that fills the sha into the S-C59 note, matching the repo's existing convention of citing landing commits by short sha in a slice's detail block.Rejected: Squashing into one commit with a placeholder or self-referential sha (a commit cannot cite its own sha before it exists).
Reverses: git revert of the second commit only, if the citation itself is unwanted.
Filed: -
Base moved out from under this PR — merged forward by merge commit, not rebase, and resolved the one resulting conflict by keeping both sides' intent.
Taken:
docs/reset-trackers-and-add-roadmap-398advanced to09b95705(W0's review-repair round) while this PR was open, andgit merge-treeshowed a conflict inSLICES.md's Area-meaning table: W0's side narrowed theACTIVErow's parenthetical from "media/exif trees" to "media tree" (removingexif, since S-C59 already recordedcapsule_core::exifasACTIVEin theRETIREDrow's own carve-out); my side had retensed theRETIREDrow'score-import-mediaclause to the past tense this deletion makes true. Rangit merge origin/docs/reset-trackers-and-add-roadmap-398(merge commit, not rebase, so the base's own history and this branch's history both stay intact and neither is rewritten) and resolved the single conflict block by taking W0's wording for theACTIVErow verbatim and my own already-committed wording for theRETIREDrow verbatim — the two rows are independent claims about disjoint areas, so neither side's edit needed to touch the other's row. Everything else in the merge (the newS-C59intro sentence pointing atROADMAP.md, theS-B2Landed-bullet EXIF/derivative split, the row-count line,S-D1/S-D2/S-D7/S-D8status-suffix corrections,ROADMAP.md's six narrowed rows) auto-merged with no further conflicts, since none of it overlaps the four spots this PR edits. Re-ranmise run check-docs-truth(roadmap: 46 package(s) checked, all rows resolve),mise run lint-check-md(0 issues in 0 files), andgrep -rn core-import-media(still only past-tense, commit-like citations) against the merged tree; pushed the merge commit8486a5c3a7ab7883e9d0070753ee915bd1b2de34;gh pr view 431 --json mergeablereportsMERGEABLEand a fresh CI run passed (requiredgreen).Rejected: Rebasing onto the new base — rewrites this PR's already-reviewed commit history and the sha the S-C59 note in decision 3 cites (
b51639b1), which would then need re-citing after every base move; a merge commit preserves both.Reverses:
git revertof the merge commit, or resolve the same conflict the other way (keep the pre-09b95705ACTIVEwording) if W0's narrowing is later reversed.Filed: -
Unresolved review notes