Skip to content

[EMB-463] Bootstrap python-quality-control for Quad-Agent development parity - #22

Draft
Jelle Spijker (jellespijker) wants to merge 4 commits into
masterfrom
EMB-463_improve_code_base_for_agentic_development
Draft

[EMB-463] Bootstrap python-quality-control for Quad-Agent development parity#22
Jelle Spijker (jellespijker) wants to merge 4 commits into
masterfrom
EMB-463_improve_code_base_for_agentic_development

Conversation

@jellespijker

@jellespijker Jelle Spijker (jellespijker) commented Jun 26, 2026

Copy link
Copy Markdown
Member

Jira ticket: EMB-463

Why

This PR bootstraps and synchronizes the python-quality-control repository for Quad-Agent (Antigravity, Claude Code, GitHub Copilot, OpenCode) development parity, and applies thorough remediations discovered during an adversarial RED team review to tailor all orientation context, rules, and hooks strictly to the repository's role as a shared CI quality control submodule.

What

  • Quad-Agent Configuration & Parity:
    • Full configuration parity established across .agents/, .claude/, .opencode/, and .github/.
    • Audited and verified with audit_quad_agent_parity.py.
  • Accurate Orientation Context (AGENTS.md, GEMINI.md):
    • Eliminated generic firmware/device residue (such as .swu firmware packaging, on-printer execution, and Qt/QML UI references).
    • Clarified that python-quality-control is mounted as a git submodule at ci/ across 14+ UltiMaker services and libraries.
  • Repository-Specific Custom Rules:
    • 15-shipped-runner-and-consumer-rules.md: Clarified that runner scripts (run_*.sh) and linter configs (cfg/) are the shipped surface executed in consumer checkouts rather than a local standalone test suite.
    • 34-library-consumer-contract-rules.md: Updated trigger glob to *.sh, cfg/*, local/*, and expanded documentation to list all 14+ downstream consumers (okuda, opinicus, dbus-interface-lib, libLogger, libCharon, print-process-reporting, misp-service, ultiLib, libSmeagol, mqttHandler, ebpf-io-logger, UMBusService, etc.).
  • Empirical Observation Integration:
    • Rule 01 (01-jira-commit-standards.md): Added explicit requirement for commit message bodies detailing why and how.
    • Rule 08 (08-scoped-changes-and-minimal-diffs.md): Documented empirical commit scope baseline (median 1 file per commit, 90th percentile 8 files).
    • Rule 06 (06-pull-request-lifecycle-rules.md): Aligned upstream base branch target to origin/master.
  • Pre-Push Bisect & Branch Guard Hardening:
    • check_atomic_bisect_history.py: Cleared false-positive test commands so git bisect pre-push validation passes without false failures on empty local test suites.
    • git-branch-guard.py: Harmonized regex to support both hyphenated and underscore branch naming formats (EMB-463_name and EMB-463-name).
    • .talismanrc: Synchronized and refreshed checksums.

How

  • Executed multi-agent adversarial RED team audit across rule context specificity, hook triggers, and ecosystem contracts.
  • Rewrote AGENTS.md and compiled down to GEMINI.md via scripts/sync_agentic_configs.sh.
  • Recompiled rule frontmatter indices and verified quad-agent parity (python3 .agents/hooks/audit_quad_agent_parity.py .).
  • Verified all pre-commit hooks and pre-PR quality gate checks via bash scripts/verify_and_create_pr.sh.

Verification & Validation (V&V)

  • Pre-commit static checks pass 100% cleanly on branch diff (scripts/verify_and_create_pr.sh)
  • Quad-agent parity audit passed (python3 .agents/hooks/audit_quad_agent_parity.py .)
  • Rule frontmatter compile check passed (python3 .agents/hooks/compile_rule_frontmatter.py --check)
  • Adversarial security & quality audit passed (python3 .agents/hooks/run_adversarial_audit.py)
  • Fireproofing test suite verified all wired guard hooks block violating fixtures:
Hook Fired Blocked violation When
audit-quad-agent-parity yes n/a (advisory) 2026-08-20T08:27:48+00:00 (ca4947b)
block-absolute-paths yes yes 2026-08-20T08:27:48+00:00 (ca4947b)
block-name-matched-kill yes yes 2026-08-20T08:27:48+00:00 (ca4947b)
block-secrets yes yes 2026-08-20T08:27:48+00:00 (ca4947b)
check-rule-frontmatter yes n/a (advisory) 2026-08-20T08:27:48+00:00 (ca4947b)
check-upstream-alignment yes n/a (advisory) 2026-08-20T08:27:49+00:00 (ca4947b)
pretool-guard yes yes 2026-08-20T08:27:48+00:00 (ca4947b)

PR Checklist

  • Initiating developer reviewed AI-generated code
  • No hardcoded absolute local paths or secrets introduced
  • Standing file-size and complexity budgets respected

Merge upstream master and bootstrap python-quality-control for Quad-Agent (Antigravity, Claude Code, GitHub Copilot, OpenCode) development parity.

- Wire pre-commit hooks and talisman scanning
- Establish rules bands in .agents/rules/ including custom rules for shipped runners and library consumer contracts
- Configure hooks and exclusion files across all agent platforms
@jellespijker Jelle Spijker (jellespijker) changed the title [EMB-463] Improve developer and agent experience for python-quality-control [EMB-463] Bootstrap python-quality-control for Quad-Agent development parity Aug 20, 2026
Why:
- The initial agentic bootstrap included generic firmware and hardware deployment residue (such as .swu image packaging and on-printer test execution) that does not apply to python-quality-control, which is purely a shared CI quality control submodule.
- Pre-push bisect hook was failing due to false-positive test command assumptions (pytest finding 0 tests in cfg/).
- Sibling consumer documentation in Rule 34 omitted 10+ consumers and did not trigger on runner scripts or linter configs.

How:
- Updated check_atomic_bisect_history.py to clear false test commands.
- Rewrote AGENTS.md and GEMINI.md to accurately document python-quality-control as a shared CI submodule mounted across 14+ consumers.
- Aligned Rule 04, Rule 15, and bootstrap-profile.json to reflect the quality verification workflow.
- Updated Rule 34 (Library Consumer Contract) trigger paths and documentation to cover shell runners and linter configs across all consumers.
- Integrated repository empirical observations (commit message bodies and commit size profiles) into Rule 01 and Rule 08.
- Harmonized branch naming regex in git-branch-guard.py and refreshed .talismanrc checksums.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant