feat: add contract-registry.yaml — OpenProse enforcement index #16
Closed
mumuni-bot
wants to merge 5 commits from
feat/contract-registry into master
pull from: feat/contract-registry
merge into: :master
:master
:fix/gitea-logger-docs
:fix/health-logs-to-gitea
:fix/mumuni-hermes-gateway
:fix/mumuni-ip-abiba
:fix/gpu-dense-q3-correction
:fix/gpu-dense-smartcode-fable5
:fix/update-health-check-remove-mumuni
:fix/remove-mumuni-ct114
:fix/agent-health-check-v2
:v16-contract-rules
:fm/mumuni-recovery-hwepve
:fix/pr-26-conflict
:fm/captain-decision-batch-2026-07-21
:feat/zulip-health-v3.1.0-koonimo
:fm/prose-contracts
:tune/compression-syslog-auto-v2
:tune/compression-syslog-auto
:fm/infra-maint-contract
:feat/zulip-resilience-audit-20260718
:feat/gpu-self-heal-refresh-20260718
:feat/hauhaucs-gemma4-qat-20260717
:feat/gpu-128k-genesis-hermes-v3-20260717
:fix/vault-cleanup-contract-sync
:feat/zulip-v3-resilience
:feat/gpu-fleet-rebuild-20260715
:feat/contract-registry
:feat/gpu-workload-compression-jul2026
:feat/data-source-integrity-rule
:feat/ra-h-os-custodianship-contract
:feat/delegation-prose-contract
:fix/cron-alignment-jul2026
:fix/testing-drift-jul2026
:feat/consolidate-litellm-contracts
:fix/litellm-contracts-jul2026
:fix/contract-improvements-jul2026
:feat/disk-gc-amdpve-2026-07-09
:fix/infra-update-v1.1.0-regressions
:feat/hermes-zulip-restore
:fix/ci-checkout-ip
:fix/mumuni-review-suggestions
:update-key-verification-jul2026
5
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
0e6efdb627 |
docs: add cron-prompts-review.md — all 10 generated prompts for review
PR Pipeline — Authorize → Validate → Review → Merge / auth (pull_request) Successful in 4s
PR Pipeline — Authorize → Validate → Review → Merge / validate (pull_request) Successful in 1s
PR Pipeline — Authorize → Validate → Review → Merge / lint (pull_request) Successful in 3s
PR Pipeline — Authorize → Validate → Review → Merge / ai-review (pull_request) Successful in 2s
PR Pipeline — Authorize → Validate → Review → Merge / gate (pull_request) Successful in 0s
|
||
|
|
484ea00597 |
fix: resolve registry issues — placeholders, missing postconditions, DAG/escalation/CB injection
PR Pipeline — Authorize → Validate → Review → Merge / auth (pull_request) Successful in 1s
PR Pipeline — Authorize → Validate → Review → Merge / validate (pull_request) Failing after 2s
PR Pipeline — Authorize → Validate → Review → Merge / lint (pull_request) Has been skipped
PR Pipeline — Authorize → Validate → Review → Merge / ai-review (pull_request) Has been skipped
PR Pipeline — Authorize → Validate → Review → Merge / gate (pull_request) Has been skipped
- Replaced <pve-api> placeholder with actual Proxmox API endpoint - Replaced <service-endpoints> with actual service URLs in infrastructure-monitoring - Replaced vague 'send test DM' with actual API call in zulip-health - Added 3 postconditions to hermes-agent-baseline (was empty) - Simplified verify commands in hermes-config-template and hermes-agent-baseline - Updated provision-cron-jobs.py to match actual registry schema for: - Circuit breaker: max_retries, trip_action, window - Escalation: severity levels (info/warning/critical/fatal) - DAG: depends_on array All 10 scheduled contracts now pass validation. |
||
|
|
8abbd6f001 |
fix: add multi-dimensional index to contract-registry.yaml
PR Pipeline — Authorize → Validate → Review → Merge / auth (pull_request) Successful in 1s
PR Pipeline — Authorize → Validate → Review → Merge / validate (pull_request) Successful in 1s
PR Pipeline — Authorize → Validate → Review → Merge / lint (pull_request) Successful in 1s
PR Pipeline — Authorize → Validate → Review → Merge / ai-review (pull_request) Successful in 1s
PR Pipeline — Authorize → Validate → Review → Merge / gate (pull_request) Successful in 0s
Adds index.by_domain with pm2-self-heal and disk-gc-threat-response in infrastructure group. All 28 contracts now accounted for in every index dimension: by_category, by_domain, by_owner, by_trigger, by_sensitivity. |
||
|
|
cca5a57265 |
feat: add contract-registry.yaml — OpenProse enforcement index
PR Pipeline — Authorize → Validate → Review → Merge / auth (pull_request) Successful in 5s
PR Pipeline — Authorize → Validate → Review → Merge / validate (pull_request) Successful in 2s
PR Pipeline — Authorize → Validate → Review → Merge / lint (pull_request) Successful in 1s
PR Pipeline — Authorize → Validate → Review → Merge / ai-review (pull_request) Successful in 1s
PR Pipeline — Authorize → Validate → Review → Merge / gate (pull_request) Successful in 1s
Maps all 28 prose contracts to enforcement categories (compliance, monitoring, remediation, build/deploy, maintenance, reference). Each entry includes: - Trigger mechanism (scheduled, event-driven, passive, on-demand) - Execution protocol (agent, timeout, requires, SOP) - Verification postconditions with commands - Receipt format and storage - Escalation tiers (info/warning/critical/fatal) - Circuit breaker configuration - Dependency resolution (DAG) - Last run status tracking MVP targets: hermes-key-enforcement (compliance) and proxmox-monitor (monitored → disk-gc-threat-response remediation) Related to relay #707: OpenProse Contract Enforcement Process — Draft for Review |
||
|
|
4dc29289bb | chore: remove orphan pre-merge file |