File browser redesign (Claude Design): visual + multi-select + grid + owner/chips #311
Closed
opened 2026-08-25 20:27:33 +00:00 by Cordy
·
9 comments
No Branch/Tag specified
main
b12v07
b11v07
b10v07
ci-rc-publish
fx15-s3dry
b9v07
b8v07
bench742
b7v07
legal-texts-v0.2
b6v07
b5v07
b4v07
b3v07
sx1139
st742
b2v07
ix1102
fu1098
zp1097
wd1099
tr1100
qf1077
nc1070
ci1
rp1072
lk1073
ab1071
fi1074
si1070
ra1054
wo1056
oc1057
tf1055
sv1063
fg1059
st1058
fs929
mu1039
ls1033
cf975
lf835
dx1023
ml896
a11y2
av1022
r913
r7
r6
r5
r45
r23
r1
b10
b9
fix-b5
fix-b4
fix-b3
fix-b2
fix-b1
fix-922
fix-923
fix-911
fix-343b
batch-a
v0.6.413
v0.6.412
v0.6.411
v0.6.410
v0.6.409
v0.6.408
v0.6.407
v0.6.406
v0.6.405
v0.6.404
v0.6.403
v0.6.402
v0.6.401
v0.6.400
v0.6.399
v0.6.398
v0.6.397
v0.6.396
v0.6.395
v0.6.394
v0.6.393
v0.6.392
v0.6.391
v0.6.390
v0.6.389
v0.6.388
v0.6.387
v0.6.386
v0.6.385
v0.6.384
v0.6.383
v0.6.382
v0.6.381
v0.6.380
v0.6.379
v0.6.378
v0.6.377
v0.6.376
v0.6.375
v0.6.374
v0.6.373
v0.6.372
v0.6.371
v0.6.370
v0.6.369
v0.6.368
v0.6.367
v0.6.366
v0.6.365
v0.6.364
v0.6.363
v0.6.362
v0.6.361
v0.6.360
v0.6.359
v0.6.358
v0.6.357
v0.6.356
v0.6.355
v0.6.354
v0.6.353
v0.6.352
v0.6.351
v0.6.350
v0.6.349
v0.6.348
v0.6.347
v0.6.346
v0.6.345
v0.6.344
v0.6.343
v0.6.342
v0.6.341
v0.6.340
v0.6.339
v0.6.338
v0.6.337
v0.6.336
v0.6.335
v0.6.334
v0.6.333
v0.6.332
v0.6.331
v0.6.330
v0.6.329
v0.6.328
v0.6.327
v0.6.326
v0.6.325
v0.6.324
v0.6.323
v0.6.322
v0.6.321
v0.6.320
v0.6.319
v0.6.318
v0.6.317
v0.6.316
v0.6.315
v0.6.314
v0.6.313
v0.6.312
v0.6.311
v0.6.310
v0.6.309
v0.6.308
v0.6.307
v0.6.306
v0.6.305
v0.6.304
v0.6.303
v0.6.302
v0.6.301
v0.6.300
v0.6.299
v0.6.298
v0.6.297
v0.6.296
v0.6.295
v0.6.294
v0.6.293
v0.6.292
v0.6.291
v0.6.290
v0.6.289
v0.6.288
v0.6.287
v0.6.286
v0.6.285
v0.6.284
v0.6.283
v0.6.282
v0.6.281
v0.6.280
v0.6.279
v0.6.278
v0.6.277
v0.6.276
v0.6.275
v0.6.274
v0.6.273
v0.6.272
v0.6.271
v0.6.270
v0.6.269
v0.6.268
v0.6.267
v0.6.266
v0.6.265
v0.6.264
v0.6.263
v0.6.262
v0.6.261
v0.6.260
v0.6.259
v0.6.258
v0.6.257
v0.6.256
v0.6.255
v0.6.254
v0.6.253
v0.6.252
v0.6.251
v0.6.250
v0.6.249
v0.6.248
v0.6.247
v0.6.246
v0.6.245
v0.6.244
v0.6.243
v0.6.242
v0.6.241
v0.6.240
v0.6.239
v0.6.238
v0.6.237
v0.6.236
v0.6.235
v0.6.234
v0.6.233
v0.6.232
v0.6.231
v0.6.230
v0.6.229
v0.6.228
v0.6.227
v0.6.226
v0.6.225
v0.6.224
v0.6.223
v0.6.222
v0.6.221
v0.6.220
v0.6.219
v0.6.218
v0.6.217
v0.6.216
v0.6.215
v0.6.214
v0.6.213
v0.6.212
v0.6.211
v0.6.210
v0.6.209
v0.6.208
v0.6.207
v0.6.206
v0.6.205
v0.6.204
v0.6.203
v0.6.202
v0.6.201
v0.6.200
v0.6.199
v0.6.198
v0.6.197
v0.6.196
v0.6.195
v0.6.194
v0.6.193
v0.6.192
v0.6.191
v0.6.190
v0.6.189
v0.6.188
v0.6.187
v0.6.186
v0.6.185
v0.6.184
v0.6.183
v0.6.182
v0.6.181
v0.6.180
v0.6.179
v0.6.178
v0.6.177
v0.6.176
v0.6.175
v0.6.174
v0.6.173
v0.6.172
v0.6.171
v0.6.170
v0.6.169
v0.6.168
v0.6.167
v0.6.166
v0.6.165
v0.6.164
v0.6.163
v0.6.162
v0.6.161
v0.6.160
v0.6.159
v0.6.158
v0.6.157
v0.6.156
v0.6.155
v0.6.154
v0.6.153
v0.6.152
v0.6.151
v0.6.150
v0.6.149
v0.6.148
v0.6.147
v0.6.146
v0.6.145
v0.6.144
v0.6.143
v0.6.142
v0.6.141
v0.6.140
v0.6.139
v0.6.138
v0.6.137
v0.6.136
v0.6.135
v0.6.134
v0.6.133
v0.6.132
v0.6.131
v0.6.130
v0.6.129
v0.6.128
v0.6.127
v0.6.126
v0.6.125
v0.6.124
v0.6.123
v0.6.122
v0.6.121
v0.6.120
v0.6.119
v0.6.118
v0.6.117
v0.6.116
v0.6.115
v0.6.114
v0.6.113
v0.6.112
v0.6.111
v0.6.110
v0.6.109
v0.6.108
v0.6.107
v0.6.106
v0.6.105
v0.6.104
v0.6.103
v0.6.102
v0.6.101
v0.6.100
v0.6.99
v0.6.98
v0.6.97
v0.6.96
v0.6.95
v0.6.94
v0.6.93
v0.6.92
v0.6.91
v0.6.90
v0.6.89
v0.6.88
v0.6.87
v0.6.86
v0.6.85
v0.6.84
v0.6.83
v0.6.82
v0.6.81
v0.6.80
v0.6.79
v0.6.78
v0.6.77
v0.6.76
v0.6.75
v0.6.74
v0.6.73
v0.6.72
v0.6.71
v0.6.70
v0.6.69
v0.6.68
v0.6.67
v0.6.66
v0.6.65
v0.6.64
v0.6.63
v0.6.62
v0.6.61
v0.6.60
v0.6.59
v0.6.58
v0.6.57
v0.6.56
v0.6.55
v0.6.54
v0.6.53
v0.6.52
v0.6.51
v0.6.50
v0.6.49
v0.6.48
v0.6.47
v0.6.46
v0.6.45
v0.6.44
v0.6.43
v0.6.42
v0.6.41
v0.6.40
v0.6.39
v0.6.38
v0.6.37
v0.6.36
v0.6.35
v0.6.34
v0.6.33
v0.6.32
v0.6.31
v0.6.30
v0.6.29
v0.6.28
v0.6.25
v0.6.24
v0.6.23
v0.6.22
v0.6.21
v0.6.20
v0.6.19
v0.6.18
v0.6.17
v0.6.16
v0.6.15
v0.6.14
v0.6.12
v0.6.11
v0.6.10
v0.6.9
v0.6.8
v0.6.7
v0.6.6
v0.6.5
v0.6.4
v0.6.3
v0.6.2
v0.6.1
v0.6.0
v0.5.7
v0.5.6
v0.5.5
v0.5.4
v0.5.3
v0.5.2
v0.5.1
v0.5.0
v0.4.12
v0.4.11
v0.4.10
v0.4.9
v0.4.8
v0.4.7
v0.4.6
v0.4.5
v0.4.4
v0.4.3
v0.4.2
v0.4.1
v0.3.30
v0.3.29
v0.3.28
v0.3.27
v0.3.26
v0.3.25
v0.3.24
v0.3.23
v0.3.22
v0.3.21
v0.3.20
v0.3.19
v0.3.18
v0.3.17
v0.3.16
v0.3.15
v0.3.14
v0.3.13
v0.3.12
v0.3.11
v0.3.10
v0.3.9
v0.3.8
v0.3.7
v0.3.6
v0.3.5
v0.3.4
v0.3.3
v0.3.2
v0.3.1
v0.3.0
v0.2.7
v0.2.6
v0.2.5
v0.2.4
v0.2.3
v0.2.2
v0.2.1
v0.2.0
v0.0.3
v0.0.2
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".
No due date set.
Dependencies
No dependencies set.
Reference: Cordy/Cairn#311
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Port the Claude Design file-browser redesign (
design_handoff_file_browser/: README +files-mockup.html) intoweb/static/index.html, functionally and visually. High-fidelity handoff; exact tokens/spacing/states specified.Status
192.168.10.245/cordy/cairn:v0.6.64@sha256:932aa2af…, live on the dogfood (cairn-enc, 192.168.10.249, pod healthy 1/1, no restarts). Visual confirmation still pending an operator login (password entry is out of scope for the agent).GET /api/v1/files), which can't be integration-tested from CI alone; recommended to do with the operator available. Not started autonomously.Key finding (shapes the sequencing)
Against the current code this is more than a restyle. The file-listing API (
GET /api/v1/files) returns onlyname / size / modTime / path / isDirper item. The mockup depicts features/data we don't have yet:Also: current token system is
--snow/--surface/--slate-*/--lichen/--glacier; the mockup introduces--paper/--ink/--accent/--rule/--sunk. The redesign is scoped to the file browser, so the new tokens must coexist with the old ones (still used by preview/admin/dialog panels). Accents already exist as a pref (glacier default + moss/ember/graphite); the mockup's default is moss and adds a 4th (glacier as a named accent) — reconcile at port time.Plan (incremental PRs)
.top/ sidebar→.side+navscroll+quotastorage meter / toolbar / breadcrumb / empty state; rewriterenderRows(~1774) from<table>to CSS-grid.lrrows; add multi-select (aSet+ singleapplySelwriter, survives sort & list↔grid) with the selection bar wired to existing single-item ops; add grid view toggle. Columns for now: name / size / modified / actions (owner + chips hidden until PR2/3). No backend change. (shipped: #312, v0.6.64)GET /api/v1/files. Add per-itemowner,itemCount(dirs), and status flagsshared/link/hold/lock, sourced from the existing shares/holds/locks subsystems. Keep it cheap (batch lookups, not N+1). (deferred — do with operator available)applyPrefs3-value theme + Appearance-dialog third option; CSS block already in the port.Constraints (from the handoff)
data-i18nkey, event binding, andlocalStorage["cairn-prefs"]value.svgIcon/ICON_FOLDER/FILE_BASE/ICONS/EXT_GROUPS/iconFor) reused verbatim.--check+ Go build/test as the CI gate; PRs for review (no auto-ship to the dogfood).Design handoff files live in the operator's
design_handoff_file_browser/folder (not committed). Working branch:feat/files-redesign.Phase 2 shipped — v0.6.65 (PR #313, squash-merged)
Live on the dogfood:
cairn-encon192.168.10.245/cordy/cairn:v0.6.65@sha256:db68c142…, pod Ready 1/1, 0 restarts,/healthzgreen.PR1 gaps the operator flagged
SharedandThis instancesub-headers (.navgrp), each auto-hiding when all its items are hidden.blackvalue end-to-end: Appearance-dialog option,applyPrefs()promoted to tri-state, new-token palette + per-accent overrides (handoff values), plus an old-token fallback block so admin/preview/dialog surfaces stay dark. (The accent picker + moss/ember/graphite already existed and worked — Ebony was the one genuinely-missing option.)PR2 —
GET /api/v1/filesenrichment (internal/api/listmeta.go)shared— caller has an active public link on the path.hold— a legal hold covers the path/ancestor.Resolvebefore matching (no I/O). Best-effort; a disabled subsystem or unresolvable path just yields no flag.owner(storage.FileInfohas no uploader — files carry no creator metadata),lock(the only lock is the instance boot-guard instatestore, not per-file),itemCount(aListper subdir = N+1 on the main-screen hot path). Fabricating owner/lock in a product with real legal-hold semantics would be worse than omitting them. The owner column therefore stays hidden; making it real needs a storage-layer schema change, not a UI change.PR3 — status chips
Shared+On holdchips from the PR2 fields. Owner column remains hidden (no data).Gate: anchored splices (assert count==1),
go vet ./...clean,go test ./internal/api/...green (newapplyFlagstests),go build ./cmd/cairndOK,node --checkOK, and CI (ci.yml) green on the PR head.Left for the operator (bulk visual check, needs a fresh login — in-memory sessions): nav group labels, the Ebony theme option, and the chips on shared/held files. Also worth an eyeball: whether the file-nav buttons correctly hide in admin mode (a pre-existing PR1 structural question, not touched here).
Follow-up fix shipped — v0.6.66 (PR #314)
Members button missing in spaces. Root cause was a PR1 stopgap, not the redesign logic: PR1 added
document.body.setAttribute("data-space", "personal")at init (to keep the empty Owner column hidden "until PR2/PR3") and never updates it per-view. That made the CSS rulebody[data-space="personal"] #spacemembers{display:none}fire in every view, hiding the button even inside a space. The button's JS gate (feat.spaceMembers && at a /spaces/<name> root) was byte-identical before PR1, in PR1, and now — so before PR1 (nodata-spaceattribute) the rule never matched and the button showed.Fix: dropped the redundant
#spacemembersCSS rule; the JS gate alone hides it correctly in personal space and shows it in a space. Owner column stays hidden (thedata-space="personal"default is left in place intentionally, since there's still no per-item owner data). CI green on the head commit; live on the dogfood as v0.6.66.Redesign phase 3 is shipped and live on both dogfoods (v0.6.75), ported from the new
files-mockup.htmlhandoff in five slices:Themes are now five, per the operator's call: Light, Night (the existing blue dark — stored value stays
darkso no saved preference orphans), Dusk (new, the mockup's green-cast dark), Ebony, Slate (new). Both token systems (--paper/--ink/--accentand the legacy--snow/--glacier) carry all of them plus every accent variant, so legacy panels theme along.Two real bugs surfaced while porting, both fixed:
pvsel) was still styled astr.pvsel > td— dead since the table became.lrgrid rows, so "you are previewing this" has rendered nothing in the shipped app.@media-keyed, but the preview panel takes width away without the viewport changing: the breakpoints never fired and the shortfall landed entirely on the filename track. Now@container list.The pointer-capture divider supersedes the v0.6.67 iframe workaround (agreed with the operator); that patch is removed.
Not ported / deliberately open:
#membersdlg-idp(IdP-managed membership notice) ships hidden with i18n, waiting on a backend flag — that's #129.Fidelity spot-check across the five themes and the four accents is the operator's visual pass on the dogfood.
Admin redesign slice A shipped — v0.6.77, live on both dogfoods. PR #326.
Rail regroups to three (Instance / Access, sharing & federation / Billing — operator's call: Federation merges into access and sharing rather than standing alone, Billing keeps its own group). "← Files" leaves the rail and becomes "Exit to files" in a labelled header band with a crumb and a height-reserved description. Overview drops three equal stat cards for two meters (the only quantities with denominators — storage, seats) plus grouped status rows on the shared
chipcomponent.Remaining admin slices: B settings-row pattern + switches + save bar + segmented tabs (Basic/Storage/Sharing/Users/Encryption) · C data-heavy topics (Deleted files, Audit log, Spaces inventory) · D Retention & holds, Updates, Licensing, Peering.
Deferred items — running list
To be swept in one pass once the UI port is complete. Numbering continues across the whole redesign.
#membersdlg-idpships hidden, i18n done)tr.pvselandaside > buttonwere both silently orphaned by the redesign; likely more.notice, "an update is available") — needs the Updates check to run on Overview.ovcard/.ovcards/.ovlabel/.ovnum, possibly.kvbadgeItems 6 and 7 are the ones that need a product decision rather than just cleanup: either the endpoints grow to serve them, or those Overview rows stay out. I've omitted rather than faked them.
Admin slice B shipped — v0.6.78, live on both dogfoods. PR #327.
Settings rows (name + explanation left, control right), checkboxes render as switches, underline tabs become a segmented control, and Save becomes a sticky bar that appears only when something changed, counts the pending changes and offers Discard.
Implementation note worth keeping: this is presentation only.
SET_SLOTSstill relocates the same field elements, every field id / value binding / save handler is untouched, and all the CSS is scoped to#adminviewso the settings dialog and other.field/.dlgactionsusers are unaffected. The save bar is selected with:has(button[id^="adm-save-"])so the Updates topic's "Check for updates" bar is not swallowed. Baseline for the dirty state is captured right afterloadSettingsValues()and re-captured after a successful save by wrapping the existingonclick.Remaining: C data-heavy topics (Deleted files, Audit log, Spaces inventory) · D Retention & holds, Updates, Licensing, Peering.
Deferred items — running list (updated)
#membersdlg-idpships hidden, i18n done)tr.pvsel,aside > buttonclass of bug).notice) — needs the Updates check on Overview.ovcard/.ovcards/.ovlabel/.ovnum, possibly.kvbadgeSET_DESCrender without one rather than getting invented copy — the map covers what I could name with confidenceItems 6, 7 and 10 need a product decision; the rest are cleanup or content.
Admin slice C shipped — v0.6.79, live on both dogfoods. PR #328.
Deleted files split into Eligible now / Protected with each protected row carrying its reason; audit log becomes an aligned time/actor/action/path grid with an action filter and a stated 200-event cap; the spaces hint paragraph becomes an inventory that surfaces deactivated spaces still holding storage.
Two findings worth recording:
eligible,holdandkeepUntilper item. Eligibility was never missing data — it was only ever rendered as a disabled button. No backend change was needed for the split.ownerLblundefined before it shipped;t()returns the key verbatim when missing, so the spaces list would have read "ownerLbl nikola". Now defined in all four languages. This check is worth keeping as a CI step — added as item 12 below.Remaining: D — Retention & holds (the resolver), Updates (version comparison), Licensing (seat meter with the free-tier line), Peering (two-halves cards). That closes the admin port.
Deferred items — running list (updated)
#membersdlg-idpships hidden, i18n done)tr.pvsel,aside > buttonclass of bug).notice) — needs the Updates check on Overview.ovcard/.ovcards/.ovlabel/.ovnum, possibly.kvbadge; now alsofmtEvtis near-unusedSET_DESCentry render without a descriptionItems 6, 7, 10, 13 and 14 need a product or API decision; the rest are cleanup, content or CI.
Slice D shipped (v0.6.80, #329) — the admin port is complete. Updates, legal holds and licensing done; peering deliberately untouched.
Three new deferred items, plus one correction to the plan:
GET /api/v1/admin/retention/resolve?path=that returns the effective rule and its source; then the UI just displays the server's answer instead of computing a rival one.peerCardElalready joins the inbound key we issued with the outbound peer entry and handles either half being absent (v0.6.32–41). The mockup's "two halves" card is what is already shipping. Restyling would have re-litigated a design that already landed.Process note for the one-shot house style (not a product item, but it cost four failed runs across slices C and D): the hand-written
grep -c … ; test "$X" = "N"verification block adds nothing over the splices' ownassert count == 1plusnode --check, and every one of its four failures was my count being wrong while the edit itself was correct — the file was written, then the job aborted before pushing. Causes seen: element created viaclassNamein JS so the class string appears once not twice; a symbol legitimately appearing 2× not 3×. The last workflow drops the greps entirely and keepsnode --check+ the i18n key audit, which are the two checks that can actually fail for a real reason. Recommend that as the standing pattern.Item 12 (add the i18n key audit to
ci.yml) is now more clearly worth doing: it has caught one real bug (ownerLbl, slice C) and passed cleanly on every slice since, so it is cheap and it works. It only runs because I paste it into each one-shot; in CI it would guard every contributor's change.Deferred-items sweep complete — v0.6.81, live on both dogfoods. PRs #330, #331, #332, #333.
16 of 17 items closed. One deferred by decision, and it is the only one that needed deferring.
The finding that matters most
Four items recorded as "blocked on a missing endpoint" were already served. I had written them up from intent rather than from the code:
auditQueryhas parsedfrom/toas RFC3339 since it was written. Only the inputs were missing./admin/infoalready returnedstorageDriverandshareCount.RetentionPeriodsis amap[string]string. My stated blocker ("rules are free text, the grammar is unverified") was simply wrong; the textarea is a serialisation of structured data.Net: cluster C needed one endpoint and one boolean, not seven endpoints. Worth remembering next time I record something as blocked — "I have not read this" and "this does not exist" are different claims, and I filed the first as the second.
Two live bugs found by the new guard
internal/webcheckwas written first, and everything else in #330 is something it found rather than something I went looking for:classList.add("dragrow"); the CSS still saidtr.dragrow. No grab cursor, no drag opacity, no drop highlight, for weeks./api/v1/filesevery 60 seconds to decide the visibility of an elementdisplay:none !importanthad made unreachable. Found because the removal script refused to proceed on an unrecognised reference — the abort was the discovery.Deferred, deliberately
Item 2 (per-item notification read state) → #138. It needs per-user persistence, and every runtime state file is exactly what #138 moves into the storage backend. Building it now hands that milestone one more thing to migrate, and picks the schema before the new layout exists.
Audit event count on Overview stays out: no count endpoint exists, and a number inferred from a capped query would look authoritative without being so.
Standing notes
aside > button) — that needs a real DOM and therefore a login. Written into the package doc so nobody assumes more coverage than exists.TestUnusedClassesReportlogs and never fails, and this run proves why: it flagstealandgray, which are real and applied via"kvbadge " + badgeCls.t(SET_DESC[id])is a dynamic lookup the i18n guard cannot check; the splice validates those keys separately.set-quotafieldstill has no description — I cannot confirm from the frontend whether it caps the instance or sets a per-space default, and a confident wrong description on a quota control is worse than a blank.For your visual pass
Everything below needs a login, which I cannot do:
IdP-managed spaces enabled (power mode), soidpManagedis true and Add/Remove/role should be disabled with the notice showing.Closing as complete/superseded (operator decision, 2026-09-03).
The two unchecked plan boxes (PR2 listing enrichment, PR3 owner/chips) were delivered by v0.6.65 (
shared/holdflags + chips), and every field deliberately dropped there for lack of data has since become real and shipped through later work: the owner column (ownermeta sidecars), folder item counts, and lock chips (#315). The redesign itself completed through the admin slices A–D (v0.6.77–v0.6.80) and the 17-item deferred sweep (v0.6.81); the one item deferred by decision — per-item notification read state — lives on under #138/#402, where the watermark model now covers it.The UI has been iterated on repeatedly since (five-theme system, bell rework, Locks admin page, General settings card), all in daily dogfood use — nothing actionable remains on this issue.