Repository navigation
[Bug]: Vector-index health reports index-reindex-hourly scheduled (OK) when no cron entry is installed #99
Description
Bug Description
lib/vector_index_health.py:385-415 (check_cron) reads .context/cron-registry.yaml only. If the job index-reindex-hourly is listed with status active, it returns OK cron: index-reindex-hourly scheduled. It never checks that the registry was generated and deployed (fw cron install, /etc/cron.d by default, FW_CRON_INSTALL_DIR).
In the same fw doctor run, bin/fw:4472 prints WARN Cron registry present but not generated — run: fw cron install. The two lines contradict each other, and the OK one sits inside the vector-index block, where a reader looks to learn whether the index will be refreshed.
Steps to Reproduce
- Project created by
fw init, upgraded to 1.8.11;fw cron installnever run (it needs root). ls /etc/cron.d | grep agenticreturns nothing; the user crontab has no framework entry.fw doctorprints bothOK cron: index-reindex-hourly scheduledandWARN Cron registry present but not generated — run: fw cron install.
Expected Behavior
check_cron reports what will actually run: OK only when the job is deployed; otherwise WARN or FAIL such as index-reindex-hourly declared in the registry but not installed (fw cron install).
Actual Behavior
OK cron: index-reindex-hourly scheduled while nothing is scheduled.
fw doctor output
AI Agent
Claude Code
Operating System
Linux
Additional Context
1.8.11 (e42aa41), vendored consumer, Linux (Ubuntu 20.04, systemd 245), Claude Code.
Activity
DimitriGeelen commentedon Oct 18, 2026
[AEF intake] Received — 2026-10-18
Thank you. This issue has been ingested into the Agentic Engineering Framework's intake as INTAKE-0015. Next step: classification (type, affected area, severity, whether it reproduces on the current release and on bleeding-edge). You will get a comment here at each step: classified → decision → in progress → fixed on bleeding-edge → available for testing → released.
These status updates are automated, but Dimitri personally looks at every issue and decides what happens to it. Replies on this issue are read.
DimitriGeelen commentedon Oct 18, 2026
[AEF intake] Classified — 2026-10-18
Type: bug. Area: vector-index health. Severity: medium (an OK line for a job that will not run). Reproduces on v1.8.11: yes, in the code.
lib/vector_index_health.py:385(check_cron) reads.context/cron-registry.yamlonly and never checks that the job is installed. Duplicates: none. Related: T-3783 (introduced the check), T-4256 (a different WARN in the same check).Awaiting the maintainer's decision.
These status updates are automated, but Dimitri personally looks at every issue and decides what happens to it. Replies on this issue are read.
DimitriGeelen commentedon Oct 18, 2026
[AEF intake] Accepted — 2026-10-18
Tracked as T-4356, prioritised (horizon: now). Next update here: in progress.
These status updates are automated, but Dimitri personally looks at every issue and decides what happens to it. Replies on this issue are read.
DimitriGeelen commentedon Oct 19, 2026
[AEF intake] In progress — 2026-10-19
Work has started under T-4356. Next update here: fixed on bleeding-edge.
These status updates are automated, but Dimitri personally looks at every issue and decides what happens to it. Replies on this issue are read.
T-4356: GH #99 is the T-4390 defect — ACs, verification and RCA point…
DimitriGeelen commentedon Oct 19, 2026
[AEF intake] Fixed on bleeding-edge — 2026-10-19
Fixed under T-4356 in commit 3389c54 (on the
bleeding-edgebranch; not yet in a release).To test it before the release:
env -u PROJECT_ROOT -u FRAMEWORK_ROOT -u CLAUDECODE timeout 600 bats tests/unit/t3783_vector_index_health.bats > /tmp/.t4356 2>&1 && ! grep -q "^not ok" /tmp/.t4356 && grep -q "T-4390: registry-active but no deployed file is FAIL" /tmp/.t4356Feedback here is welcome. Next update here: released.These status updates are automated, but Dimitri personally looks at every issue and decides what happens to it. Replies on this issue are read.