contextlake 8.8.0
Added
-
contextlake schedule: a self-scheduler. Measures how long a run takes and how often your
repositories change, works out an interval from the two, and installs a systemd user timer or
a crontab entry that keeps the mirror and the knowledge layer current on its own, with no unit
file or cron line to write by hand. Core tier: works without the[kb]extra.
recommend,statusandlistread only;install,interval,resetanduninstall
write. Ad-hoc jobs run any contextlake command on their own interval:contextlake schedule interval 6h run -- kb wiki --force
Ten
schedule_*config keys, an honest split between what systemd and cron can each do, and a
container refusal for state that will not survive a restart. Discarding measured history
(--purge,reset --history) renames the history file to a.discardedsidecar instead of
deleting it, so a mistaken discard is recoverable. See Scheduling runs. -
branch_map: per-repository branch pins.branchputs the whole fleet on one branch,
which is the common case and not the only one.branch_maptakes comma-separated
pattern=branchpairs using the same globs asrepo_filter, so one team can track
developwhile a legacy tree sits onmaintenanceand everything else follows the
most-active selection. First match wins, so a specific entry can precede the glob that
would otherwise catch it. It beatsbranch, falls back to it, then to the selection.
A repository whose mapped branch does not exist is reported asunpinned, exactly as
branchalready does, rather than being switched to something else.branch_map = team/api=develop, legacy-*=maintenance
Changed
-
bootstrapgained--force. Rebuilds everything instead of only what changed: every
repository re-parsed, every node re-embedded. It did not exist as a flag before; it is what
schedule's periodic full cycle runs. -
configuration.md's example config now shows the scoping keys.repo_filter,branch
andbranch_mapwere documented in the settings table but absent from the example anyone
copies, so the two that already existed were easy to miss.