Skip to content

Add lightweight Claude operator layer and weekday Windows scheduler#23

Open
fowler128 wants to merge 2 commits into
mainfrom
codex/add-operator-layer-for-bizdeedz-automation
Open

Add lightweight Claude operator layer and weekday Windows scheduler#23
fowler128 wants to merge 2 commits into
mainfrom
codex/add-operator-layer-for-bizdeedz-automation

Conversation

@fowler128

Copy link
Copy Markdown
Owner

Motivation

  • Provide a thin Claude Code operator layer to automate existing BizDeedz run steps without rebuilding the pipeline.
  • Keep the system Windows-first and low cognitive load by adding simple wrappers and a scheduler installer rather than replacing scripts.
  • Preserve existing scripts and behavior while enabling local notifications and concise operator commands.

Description

  • Add project-level Claude defaults in .claude/settings.json with conservative local permissions, a BIZDEEDZ_LOG_DIR env default, and a Windows balloon notification hook for needs_input, run_completed, and run_failed events.
  • Add three Claude commands: run-content-intel (prefers scripts/run_pipeline_live_to_google_sheets.bat, falls back to scripts/run_pipeline_live.bat), sync-market-sheet (runs sheet sync path and checks artifacts), and daily-operator (runs wrapper, reviews outputs, and appends a concise status note to output/logs/daily-operator-status.log).
  • Add two subagents: repo-runner for running repository scripts and summarizing failures, and output-reviewer for CSV/sheet quality checks and missing-data flags.
  • Add scripts/daily_market_intel_to_sheet.bat which prefers the live-to-sheet wrapper, falls back to the live pipeline, writes dated logs to output/logs, and exits non-zero on failure, and add scripts/install_task_scheduler.ps1 which registers a weekday Task Scheduler job using repo-relative paths and documents edit/remove commands.
  • Add a concise, Windows-first docs/automation-runbook.md that explains what runs automatically, manual fallback commands, log locations, credential remediation, and scheduler edit/remove instructions.

Testing

  • python -m json.tool .claude/settings.json validated the JSON and succeeded.
  • Presence and contents of new files were inspected (.claude/*, scripts/daily_market_intel_to_sheet.bat, scripts/install_task_scheduler.ps1, docs/automation-runbook.md) and are present as added.
  • Created wrapper enforces output/logs creation and non-zero exit when underlying scripts are missing, verified by static inspection of scripts/daily_market_intel_to_sheet.bat logic.
  • Could not run Windows .bat execution or register the scheduled task in this Linux CI environment, so end-to-end .bat and Task Scheduler installation tests were not executed here and should be validated on a Windows host.

Codex Task

@vercel

vercel Bot commented Apr 9, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
claude-code-practice Ready Ready Preview, Comment Apr 9, 2026 0:40am

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant