Skip to content

docs(storage): finalize the approved inspection and removal design - #2015

Merged
schlessera merged 2 commits into
mainfrom
t3code/issue-1782-dependents-blockers
Oct 16, 2026
Merged

schlessera merged 2 commits into
mainfrom
t3code/issue-1782-dependents-blockers

Conversation

@schlessera

@schlessera schlessera commented Oct 16, 2026 •

Copy link
Copy Markdown
Owner

Closes #1782

What changed

The approved Storage design is now a self-contained design-kit record, with desktop and 320px wireframes for overview, drill-down, filtering, file inspection, selected removal and mixed outcomes. It records the eighth Settings pane, allocated-size default, decimal units and the requirement to ship the first public pane with safe binary removal. The navigation record and design index link the decision.

The implementation chain is scoped as native #1779 children: #2009 core inventory → #2010 server inventory → #2011 maintenance / #2012 safe binary removal → #2013 complete pane. #2014 separately designs deferred growth and low-space guidance. None of those filings claims a shipped implementation.

Why this shape

This consolidates the maintainer's complete-design approval and S1=A/S2=A/S3=A/S4=B, without another approval round. It preserves the accounting/lifecycle/native-storage boundaries, distinguishes logical entry totals from physical-object union, keeps unknown measurements explicit, and does not equate untracked files with missing recovery coverage. The design's original read-only-first recommendation and optional binary display units are superseded by the controlling rulings.

Current source review corrected the issue's obsolete Settings citations. The separate attribution input correction #1787 is already merged through #2007.

Proof

  • Read current Settings, stats, cleanup, scratch, application, journal, writer-gate and principal boundaries at base 04ef3552190d8f56eab09dd6c3580101b6385ba4.
  • bun run check:pr --base origin/main: passed, including lint/leakage and 345 tests across 16 affected invariant files (1,248 assertions).
  • Walked the synthetic Odysseus cases through the map-independent list, inspection, exact-version review and mixed-result paths. Independently checked the 5,000,000-byte strict boundary, 101,500,000-byte entry total versus 53,300,000-byte hard-link object total, dense entry count and capacity arithmetic.
  • Desktop/320px annotated wireframes and dark/paper/browser/accessibility verification matrix are design deliverables. No production UI, cleanup endpoint or browser-runtime proof is claimed by this documentation PR; those receipts belong to core: expose bounded local storage inventory without changing corpus stats #2009–ui-react: deliver the complete Storage pane with treemap and recoverable file removal #2013.
  • No executable change or new guard test, so mutation proof is not applicable. Hosted CI run 38843501876, attempt 1 passed on head a16cf167d31a5d3a9a385bdd637249795229b762. Changeset job 116788684015, verify job 116788842949 (345 tests) and proof job 116788934725 all checked out 4c1ca69f316bbd82c0abc8aa7cefbce00a5ecd11, with parents 5e9854b2e53ab7cfb4364008cf9cd2065b369404 and the head, tree 53073377144c0660ed69f8d795c7b953cd6b02e9. Contract run 38843501643/job 116788682722 passed on the head. Remaining proof categories were intentionally excluded by the docs-only planner. Main advanced by the unrelated renderer phase-clock test change test(render): control registered renderer phase deadlines #2006 after local source review; the recorded hosted combined checkout already includes it. PR and issue milestones read back as 0.44.0; registry latest is 0.43.1.

Checklist

  • Focused local preflight/behavioral receipts and complete selected hosted proof passed; actual head/base/job checkout evidence is in Proof.
  • Acceptance criteria from the issue are all met, or the gap is named below.
  • The PR and completed/advanced issues have verified release milestones under docs/process/github.md.
  • A changeset is included, or this changes nothing a consumer can see.
  • No personal data anywhere in the diff — the leakage gate covers the whole tree.
  • The integration contract index or relevant component is updated in this same commit, or nothing in the machine surface moved.
  • Docs under docs/ reflect the change, or nothing documented moved.

Anything left open

Nothing for the design spike. Product implementation remains in #2009–#2013; growth/low-space design in #2014. Remote/provider usage, host/container stores, per-file Git attribution, derivative grouping, workspace cleanup and new retention defaults are explicitly deferred. #1779 stays open until its product definition of done is met.

@schlessera schlessera added this to the 0.44.0 milestone Oct 16, 2026
@schlessera schlessera added type: docs Documentation only. area: ui-server Hono app factory: turn coordinator, auth, session catalog, routes, cron. area: ui-react React chat/files/voice components, stores, WebSocket transport. labels Oct 16, 2026
@schlessera
schlessera merged commit 9fc02d5 into main Oct 16, 2026
11 checks passed
@schlessera

Copy link
Copy Markdown
Owner Author

Automatic main-push CI 38844260772, attempt 1, passed on squash 9fc02d5fc5a7f62f13063c04ce68b3cbe12948c9. Actual successful job checkouts all match that squash:

  • changeset: job 116791076033.
  • verify: job 116791203593.
  • proof: job 116791322295.

The squash parent/tree match the PR combined checkout documented above. #1782 is closed and both issue/PR retain 0.44.0. The storage implementation remains in native #1779 children #2009–#2014; #2009 and #2014 are unblocked, while the dependent implementation issues remain blocked on their open prerequisites. No product implementation or release publication is claimed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: ui-react React chat/files/voice components, stores, WebSocket transport. area: ui-server Hono app factory: turn coordinator, auth, session catalog, routes, cron. type: docs Documentation only.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ui-react: design the storage treemap and file cleanup workspace

1 participant