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

[GEMINI-HARDEN-05] Make architecture_linter_v2 repo-aware, test-backed, and CI-enforced #437

New Issue
Closed
opened 2026-04-09 14:32:40 +00:00 by Timmy · 0 comments
Timmy commented 2026-04-09 14:32:40 +00:00
Owner
Copy Link

Parent epic: #432

Why
architecture_linter_v2.py currently infers policy from repository basename (timmy-config vs hermes-agent) and ships next to merged scripts that violate its own hard-coded-IP doctrine.

If this linter is going to guard architecture, it must be trustworthy, configurable, and exercised in CI against realistic fixtures.

Acceptance criteria

  • Rule policy is driven by explicit configuration/fixtures, not only by folder basename.
  • Canonical-repo rules are documented and testable.
  • Add positive/negative fixtures for timmy-config, hermes-agent, and neutral repos.
  • The current scripts/ suite either passes lint honestly or documents any intentional exceptions in policy.
  • CI/guardrail integration blocks future architectural drift.
  • scripts/README.md or ADR docs explain what the linter enforces and how to extend it.

Related

Parent epic: #432 Why `architecture_linter_v2.py` currently infers policy from repository basename (`timmy-config` vs `hermes-agent`) and ships next to merged scripts that violate its own hard-coded-IP doctrine. If this linter is going to guard architecture, it must be trustworthy, configurable, and exercised in CI against realistic fixtures. Acceptance criteria - Rule policy is driven by explicit configuration/fixtures, not only by folder basename. - Canonical-repo rules are documented and testable. - Add positive/negative fixtures for `timmy-config`, `hermes-agent`, and neutral repos. - The current `scripts/` suite either passes lint honestly or documents any intentional exceptions in policy. - CI/guardrail integration blocks future architectural drift. - `scripts/README.md` or ADR docs explain what the linter enforces and how to extend it. Related - #432 - PR #418 - PR #430
Timmy added the enhancement label 2026-04-09 14:32:40 +00:00
ezra was assigned by Timmy 2026-04-09 14:45:24 +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 enhancement
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 ezra
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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