Remote-first refinements: target-limit ordering + git_log wipe interaction #112
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/repo-recall#112
Loading…
Add table
Add a link
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?
Remote-first refinements (follow-ups from #109)
Two non-blocking refinements surfaced while landing remote-first ingest:
remote_target_limitordering in remote-first.remote_targets()sorts by latest-committimestamp and trims to
remote_target_limit(default 25). Remote-first seeds have no localcommits, so they all tie at
i64::MINand the trim drops repos arbitrarily (repo-recall itselffell outside the top 25 in testing). In remote-first mode either default the cap higher, sort
seeds by
pushed_at, orlog()what was dropped so it isn't silently incomplete.git_logwipe vs remote commits. The per-source scheduler can rungit_log(whichwipe_git_logs the commit tables) withoutgithub_remotein the same tick, transientlydropping remote-ingested commits until the next remote pass. Give remote commits their own
source-ownership or fold into the Slice 3 cache (#110).
refs #109
Closing. The Claude-session observability tree (repo-recall / luca / session-lattice) is retired in the June 2026 surface reduction.