Repository navigation
Persist the sweep's notices in the record, and let --ls read them #508
Description
Build the resolution of #480: the detached sweep's notices land in the record, and --ls reads them.
Scope, per the decision:
- A per-repo last-sweep note in
metadata.jsonbesidelast_fetched, overwritten on every sweep (bounded by construction, no rotation, no new file). A successful sweep clears it; a refused pack or failed fetch writes the repository and git's own words. dl --lsand--ls --jsonare the reading surface. The table gets a terse marker; the JSON carries the note verbatim. Nothing new prints on the launch path.- Not a
usize/string that conflates "no note" with "could not read": absence and presence are distinct states, per the map's constructive-modeling defaults. - Test shape, from the ticket: a sweep whose
pack-refsrefuses leaves the refusal readable in the record and visible in--ls, asserted end to end. Today no test can distinguish the notice being raised from being read; this closes that.
Facts already verified on the map (fact-finder trace, 2026-08-29): ProcessRunner::detach nulls all three fds (devlaunch-runner/src/lib.rs:660); the --update-cache child's say() is eprintln! into that null (dl/src/commands.rs:346, :355); there is no existing persist-and-print mechanism — the #481 retired-key notice re-derives from config.toml on every run and writes nothing — so this deliberately introduces the first background-learned condition that survives to a foreground run.
Activity
blooop commentedon Aug 29, 2026
Claimed 2026-08-29: build in progress from an interactive session (agent in an isolated worktree), managed by session devlaunch-2b as part of closing out map #444. PR to follow. If you are another session looking at this ticket, pick a different one.
blooop commentedon Aug 29, 2026
Built in #519.
The record is
BaseRepository.last_sweep: aSweepTroublearm plus git's ownwords,
said: nullwhere nothing spoke. Overwritten on every pass that acts on arepository, cleared by a clean one, left alone by a pass that attempted nothing
(not due, contended, lock unavailable) so silence about an untouched repository
never reads as a clean sweep.
Three states rather than two, as the ticket asked: the key is absent when
there is nothing to say, an object when there is, and a stored value this build
cannot read is a
NotRebuiltand goes the way an unparsablelast_fetchedalready goes (#67), reported with the original preserved. No empty string
standing in for silence.
dl --lsprints one line per troubled repository under the table, on stderr:Per repository rather than a column, because the note is about a bare clone: two
workspaces of one repository share a note, and a repository with no workspace
still has one to report and no row to report it in.
dl --ls --jsoncarries itas
lastSweepon the rows whose repository has one, appended and absent unlessthere is a note, so wf's document is byte for byte unchanged on a clean cache.
The red test is end to end at the binary boundary
(
a_pack_the_sweep_could_not_do_is_readable_when_somebody_next_lists): agiton the run's PATH that refuses
pack-refs,dl --update-cache --force, then therefusal read back out of
metadata.json,dl --lsanddl --ls --json.Verified red with the record write disabled.
One property given up and named in the PR:
dl --ls's table now readsmetadata.json, through a newsession::open_storagethat still skips theconfig and the cache migration.
docs/cleanup.md's "That notice reaches nobody today" paragraph is rewritten:the notice still reaches nobody, and the record is what does.
Persist the sweep's notices in the record, and let --ls read them
Persist the sweep's notices in the record, and let --ls read them