菜单
Durable cron job store for BAS automation: jobs.json, scheduler gateway, isolated Codex wakes vs worker scripts; not inside Codex or BACnet drivers.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | workspace-cron |
| description | Durable cron job store for BAS automation: jobs.json, scheduler gateway, isolated Codex wakes vs worker scripts; not inside Codex or BACnet drivers. |
bas_build_spec/cron/jobs.json — durable job definitions (cron, every, at schedules).bas_build_spec/cron/jobs-state.json — last-run + running reconciliation (gitignored).bas_build_spec/cron/runs/<job_id>/ — per-run JSON (gitignored).When the human wants no scheduled Codex or workers (Cursor-led iteration, UX review):
bash cron_codex/bin/bas_remove_cron_marked.sh — removes # BAS_CODEX_WAKE crontab lines.enabled": false on every job in cron/jobs.json (discovery poll, point scrape, bas-wake-hourly, etc.).touch cron_codex/state/waiting_human — bas_wake.sh skips API if invoked manually without intent.BUILD_CHECKPOINTS.md Current sprint so critique does not assume fresh scrape JSON.Resume: re-run bas_install_cron.sh, re-enable only the jobs needed, run bas_validate_cron_services.sh. Discovery/scrape data will be stale until workers run again.
Do not set REMOVE_CRON_WHEN_COMPLETE=true for a temporary pause — that is for acceptance-complete teardown.
cron_codex/bin/bas_cron_scheduler.sh run-due — user crontab entry (marker # BAS_CODEX_WAKE).cron_codex/bin/bas_cron_engine.py (reconcile stale running after grace window).jobs.json defines the wake job; the scheduler is what actually launches bas_wake.sh. A crontab line that only names the scheduler does not run Codex if the scheduler script is absent.bas_app edits)When hourly automation “should” run but nothing changes:
crontab -l should show bas_cron_scheduler.sh run-due (or a direct bas_wake.sh line) with # BAS_CODEX_WAKE.bas_cron_scheduler.sh and bas_cron_engine.py must exist under cron_codex/bin/ and be executable. If cron invokes a missing path, syslog shows hourly CMD (... bas_cron_scheduler.sh run-due ...) but cron_codex/logs/wake-*.log stays empty, BUILD_CHECKPOINTS.md does not advance, and there is no bas_wake / codex exec process — that is a failed gateway, not Codex “stuck mid-wake.”wake-*.log with === bas_wake start / === bas_wake end and usually updates BUILD_CHECKPOINTS.md. jobs-state.json and cron/runs/ update only when the scheduler engine ran.grep BAS_CODEX_WAKE /var/log/syslog confirms the daemon fired; it does not prove the gateway succeeded.bas_wake.sh with BAS_CODEX_ENV_FILE tests Codex without cron; if manual wakes log but cron does not, suspect the scheduler/crontab path.bas_full_reset.sh — expect empty bas_app/, no wake logs until the next successful wake, and possibly a stale dev listener on :5173 from before the nuke (HTTP up, app tree gone). Do not treat spec demo passwords as valid until bas_app/README.md exists and smoke passes.bas_wake.sh runs POST_WAKE_HOOK from cron_codex/.env after minis + critique. If the hook’s bas_post_wake_stack.sh exits early (skip wrong gate, wrong start command, or health URL mismatch), hourly Codex can still “succeed” while :8000 stays empty — that is not a missing skill; it is runtime orchestration drift.cron_codex/logs/wake-*.log for --- POST_WAKE_HOOK ---; tail cron_codex/logs/post_wake_stack.log for post_wake_stack: lines.BUILD_CHECKPOINTS.md Tier A Path A or B + memory/architecture/working-divergence.md; Codex adds bas_app/scripts/ + README / POST_WAKE_HOOK; humans loginctl enable-linger when needed. Patching bas_post_wake_stack.sh is optional ops, not a Codex-mini gate.When a scheduled or manual wake should not spend more Codex API:
| Condition | Expected behavior |
|---|---|
state/DONE_AUTOMATION present | bas_wake.sh exits immediately — no mini, no critique, no hook |
MIN_MINUTES_BETWEEN_WAKES not elapsed | Debounced exit 0 |
/tmp/bas_codex_wake.lock held by another wake | Exit 0 — do not start overlapping codex exec |
MINI_ALLOW_EARLY_STOP + state/stop_mini_loop | Skip remaining minis; critique still runs unless bash exited earlier |
| Mini blocked / queue empty for safe work | Mini touches stop_mini_loop and ends the slice — no extra minis “to try again” |
Crontab fires but bas_cron_scheduler.sh missing | No bas_wake, no API — fix gateway before blaming Codex |
Critique should record gateway gaps (missing scheduler, empty wake logs despite syslog) in BUILD_CHECKPOINTS.md rather than assuming product work continued overnight.
Full redo: spec-validation/references/full-reset-redo-checklist.md — Caddy/orphans, lock file, manual wake proof.
| Style | BAS examples |
|---|---|
| isolated | bas_wake.sh (Codex minis + critique) |
| worker | bas_systemd_manage.sh, bas_smoke.sh, bas_bacnet_lab_verify.sh |
Register new recurring work in jobs.json and mirror a one-line note in memory/stack/<service>.md when operators need it.
bas_build_spec/cron_codex/bin/bas_workspace_cli.sh cron list
bas_build_spec/cron_codex/bin/bas_workspace_cli.sh cron dry-run
bas_build_spec/cron_codex/bin/bas_workspace_cli.sh cron runs [job_id]
spec-validation, workspace-memory, systemd-live-devUse when working on Open FDD Vibe Coder Streamlit FDD demo: streamlit_app.py, 50-rule pandas cookbook, building folder browse, Haystack-like column map JSON, RCx Plots, analytics, occupancy calendar, unit toggle. Triggers on: Streamlit, streamlit_app, BUILDING tree, Haystack points, column map, RCx, 50 rules.
Use when onboarding HVAC CSV data for App 19: DATA_ROOT layout, manifest.json, grid_minutes, validate_data.py, data_paths.local.yaml, BUILDING_* switching, weather parity, VAV folders. Triggers on: import, CSV tree, manifest, poll interval, HVAC_DATA_ROOT, validate data, new building, sidecar export.
Use when implementing HVAC fault rules in pandas for App 19 with Open-FDD cookbook parity: confirm_fault, poll_seconds, operational gates, ECON free-cool (web weather), VAV fixed flow, CW wet-bulb. Triggers on: FDD, fault, rule, cookbook, confirm_fault, economizer, ECON-3, VAV-7, CW-OPT, OAT-METEO, pandas rule.
Use for Plotly charts in the Streamlit demo: rule fault plots, RCx multi-equipment overlays, box plots, OAT scatters, mech-cooling histograms. Triggers on: Plotly, chart, RCx, zone temps, duct static box, scatter, Streamlit figure.
Use when validating MQTT→cloud telemetry, calling Vibe12 Dashboard Lambda APIs for commissioning status, BRICK time-series refs, points registry, or auth from Codex/Cursor/OpenClaw. Triggers on: commissioning API, cloud_ingest_ok, telemetry flow, brick_timeseries_ref, external_ref, validate_cloud_pipeline, series_flowing, DashboardUrl, Bearer token, demo bens-office.
Use when deploying Vibe12 to Raspberry Pi or gateway via Ansible, vibe12-bacnet-read, points.csv, AWS IoT certs, GPIO DS18B20, or bacnet_pi host vars. Triggers on: ansible deploy, bacnet_pi, read driver, 192.168.204.12, points.csv, enable_bacnet_read_driver.