feat(vigil): core runtime and --vigil-once headless driver (slice 2 of 5) - #809
Closed
allen-munsch wants to merge 2 commits into
Closed
feat(vigil): core runtime and --vigil-once headless driver (slice 2 of 5)#809allen-munsch wants to merge 2 commits into
allen-munsch wants to merge 2 commits into
Conversation
First slice of the vigil phase-5 decomposition: config types + SQLite store + CLI CRUD, independent of the runtime/keeper/triggers. - vigil_db: VigilStore (open/upsert/get/remove/set_status, list_non_resting) with Active/Paused/Resting status - config: VigilEntry/VigilTrigger/VigilRite/VigilCommand/SocketMode, gated on the `vigil` feature (opt-in, NOT in default) - cli: `dirge vigil` subcommand with VigilAction + VigilAddTrigger - main: handle_vigil_command + build_vigil_entry dispatch - tests: vigil_db store CRUD/status + build_vigil_entry parsing + config serde shape - docs/config.md: document the `vigils` top-level key
…f 5) Toll/watcher/harbinger triggers, the reaper event loop, rite gate evaluation, commands-mode dispatch, and the VigilKeeper public API. Adds --vigil, --vigil-config, --vigil-once, --vigil-once-command CLI flags and wires the headless --vigil-once path (keeper startup, wake channel, on-vigil-observance dispatch, hook drain before exit). vigil remains opt-in (not in default features).
allen-munsch
marked this pull request as draft
August 23, 2026 15:16
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Slice 2 of 5 for the vigil runtime (issue #760, ELEGY-1). This adds the core runtime — triggers (toll/watcher/harbinger), the reaper event loop, rite gate evaluation, commands-mode dispatch, and the
VigilKeeperpublic API — plus the headless--vigil-oncedriver.Stacked on top of #807 (slice 1: persistence +
dirge vigilCLI), which must merge first. Because these are sequential fork PRs rather than a native GitHub stack, this diff currently includes slice 1's changes; it will shrink to just the runtime once #807 lands.Scope
src/extras/vigil/{mod,types,reaper,toll,watcher,harbinger,rite,dispatch,tests}.rs— runtime modules and their testssrc/main.rs— keeper startup, wake channel,on-vigil-observancedispatch,--vigil-onceheadless driver with hook drainsrc/cli.rs—--vigil,--vigil-config,--vigil-once,--vigil-once-commandCargo.toml/Cargo.lock—vigil = ["dep:notify"],notify7 optional.osv-scanner.toml— RUSTSEC-2024-0384 ignore forinstant(transitive via notify)Notes / known gaps
vigilstays opt-in (not indefaultfeatures).vigil_plugin_tx) and TUI observer wiring are deliberately deferred to later slices; the headless path has a live caller, so nothing here is#[allow(dead_code)]-gated beyond the pre-existingvigils_dir()helper slice 3 will consume.Self-review concerns
_bindings; if the reviewer would rather see those slices land before merging a runtime slice, I can reorder.notify7 is pulled in forwatcher; worth a second look at whether pulling a whole watch crate for one trigger type is justified versus a hand-rolled poll.