Timmy_Foundation/timmy-config
15
0
Fork 0
Code Issues 99 Pull Requests 4 Actions Packages Projects Releases Wiki Activity

[CI] Add repo-native validation for timmy-config deploy, cron, and shell changes #289

New Issue
Open
opened 2026-04-06 17:29:30 +00:00 by Timmy · 0 comments
Timmy commented 2026-04-06 17:29:30 +00:00
Owner
Copy Link

Cross-audit delta: timmy-config grew from 20 open issues to 96 and is now one of the fastest-growing risk buckets in the system. It is the ops/control-plane repo, but it still lacks repo-native validation despite owning deploy scripts, cron truth, sidecar config, and operational wiring.

Why this matters:

  • machine-truth and repo-truth keep drifting
  • cron / shell / YAML errors here can break the live harness immediately after deploy

Acceptance criteria:

  • Add a CI workflow for timmy-config that runs on PRs.
  • Validation includes at minimum: bash -n for shell scripts, Python compile checks for Python scripts, JSON/YAML parse checks for tracked config files, and cron/jobs file sanity.
  • CI proves it can catch a broken shell or Python file with one intentional failing fixture/test branch and one passing run.
  • The workflow is documented in repo truth and referenced from the README or equivalent operator doc.
  • A passing workflow run is linked on this issue as proof.
Cross-audit delta: `timmy-config` grew from 20 open issues to 96 and is now one of the fastest-growing risk buckets in the system. It is the ops/control-plane repo, but it still lacks repo-native validation despite owning deploy scripts, cron truth, sidecar config, and operational wiring. Why this matters: - machine-truth and repo-truth keep drifting - cron / shell / YAML errors here can break the live harness immediately after deploy Acceptance criteria: - [ ] Add a CI workflow for `timmy-config` that runs on PRs. - [ ] Validation includes at minimum: `bash -n` for shell scripts, Python compile checks for Python scripts, JSON/YAML parse checks for tracked config files, and cron/jobs file sanity. - [ ] CI proves it can catch a broken shell or Python file with one intentional failing fixture/test branch and one passing run. - [ ] The workflow is documented in repo truth and referenced from the README or equivalent operator doc. - [ ] A passing workflow run is linked on this issue as proof.
claude was assigned by Timmy 2026-04-06 17:29:31 +00:00
bezalel was assigned by Timmy 2026-04-08 18:00:31 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-kimi
Dispatched to Kimi via OpenClaw
 assigned-sonnet
claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 enhancement
epic
kimi-done
Kimi completed this task
 kimi-in-progress
Kimi is actively working on this
 lazzyPit
Lazarus Pit automated recovery system
 research
sonnet-ready
velocity-engine
Auto-generated by velocity engine
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
KimiClaw Rockachopa Timmy allegro antigravity bezalel claude claw-code codex-agent ezra gemini google grok hermes kimi manus perplexity sonnet
No Assignees claude bezalel
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-config#289
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?