Move the vault graph rebuild off SessionStart #1558
Labels
No labels
P0
P1
P2
P3
bug
category/code-change
category/cross-repo
category/eval-run
category/investigation
category/no-test-target
category/owner-ruling
category/prose-artifact
category/recurring-chore
category/structure
category/umbrella
crc-refactor
create
delete
enhancement
filed-by/agent
filed-by/user
frozen
lint-rule
needs-info
needs-triage
next
plugin/cc-architect
plugin/os
plugin/os-adr
plugin/os-aidd-lint
plugin/os-backlog
plugin/os-context
plugin/os-doc-hygiene
plugin/os-sdlc
plugin/os-vault
project/cc-os
ready-for-agent
ready-for-human
recurring
review
rule-proposal
update
waiting
wayfinder:grilling
wayfinder:map
wayfinder:map
wayfinder:research
wayfinder:task
wayfinder:task
wontfix
worklist/deviations
worklist/lint-rule
worklist/new-implement-build
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
jared/cc-os#1558
Loading…
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?
Problem
The os-vault SessionStart hook starts a detached vault graph rebuild when
~/.cache/graphify/vault-rebuild.stampis older thanstale_threshold_days. The GPU load and fan noise begin just as the user starts to work, with no warning. The user questioned this on 2026-11-04.Observed
plugins/os-vault/hooks/session_start.pystarts the rebuild.plugins/os-vault/config.yamlsetsstale_threshold_daysto 7. This is an os-vault choice, not a graphify default.Extraction is incremental. The first run read 205 changed notes and skipped 128 unchanged notes. A later run costs less than the first run.
Reproduce
n/a: design change. Open a session when the stamp is older than 7 days, and the rebuild starts.
Approach
Run the rebuild from a systemd user timer at a fixed time, nightly or weekly. Remove the SessionStart rebuild. The user chooses the time.
Two tests pin the current hook behavior and must change with it:
plugins/os-vault/tests/test_session_start_rebuild.pyandplugins/os-vault/tests/test_session_start_lock.py.Required work:
_REBUILD_SCRIPTinplugins/os-vault/hooks/session_start.pyOrchestrator work: the user picks the timer time. Install the systemd user timer and service unit.
Acceptance criteria
stale_threshold_days, when a session starts, then no rebuild starts.Owner sketch
Origin
plugins/os-vault/hooks/session_start.py) ← os-vault chose a stamp-age trigger with a 7 day threshold (plugins/os-vault/config.yaml). DESIGN.Found during #1540.
VERDICT: CREATE