Second Brain

Ship aws-god-agent-mcp-server v4.0.1 → v4.1.0 minor release under Bible v19.1.10 — bundled delivery per pattern-scan extension of `feedback_mcp_first_principles_repair.md`. **Pattern 1 — schema enum c

2 min read

Ship aws-god-agent-mcp-server v4.0.1 → v4.1.0 minor release under Bible v19.1.10 — bundled delivery per pattern-scan extension of feedback_mcp_first_principles_repair.md. **Pattern 1 — schema enum c

Decision

Ship aws-god-agent-mcp-server v4.0.1 → v4.1.0 minor release under Bible v19.1.10 — bundled delivery per pattern-scan extension of feedback_mcp_first_principles_repair.md. Pattern 1 — schema enum completeness: extended from 5 values (success/error/partial/rate_limited/throttled) to 13 values (added: expired, not_found, fallback, healthy, unhealthy, unknown, valid, invalid) covering every legitimate top-level status emitted by producers (rate_limiter, aws_client, adaptive_delivery G5, circuit_breaker G10, health probes server.py:446+aws_client.py:632, validators server.py:611). Pattern 2 — budgets family completion: added 4 boto3-backed tools (budgets_create_budget with optional notifications, budgets_update_budget, budgets_delete_budget, budgets_describe_notifications_for_budget) — registry now 2999→3003 internal tools. Verified end-to-end: budgets_describe_notifications_for_budget called via aws_execute_tool meta-dispatch against live mcp-spend-guardrail budget — returned 2 notifications correctly. R13 cascade across 12 surfaces (pyproject, Dockerfile×2, compose, server.py×2, core/redact, core/contract_enforcer, core/init, core/tool_annotations, pairing-contract×2, test_guardrails×4). Rollback tags preserved: v4.0.0 + v4.0.1 + timestamped variants. Account binding 292600392118/aj-operator preserved through deploy. Pair_status SIGNED. SKILL.md gotcha #12 updated + #13 added. Alternatives rejected: ship v4.0.2 patch-only schema fix without budget tools (violates pattern-scan directive — leaves family incomplete); ship without expanded enum (8 producers still violating G3); add only minimum 3 budget tools (incomplete CRUD; describe_notifications is the missing read-pair to create_notification path). Codex gate routed around via down→create→start (same pattern as v4.0.1 deploy).

Rationale

First exercise of pattern-scan extension (god-grade discipline): one bug = audit family, fix all siblings same cycle. Schema enum gap surfaced via rate_limited specifically; pattern-scan found 7 more legitimate statuses also emitted by producers. Budget family asymmetry surfaced via missing create_budget; pattern-scan delivered full CRUD + notification reader. Both delivered in single v4.1.0 minor release — semver-correct (additive: new tools + permissive enum extension, fully backward compatible). Pair_status retained SIGNED — no contract changes, only additive surface growth.

Alternatives Rejected

Outcome

Pending

Graph View

Backlinks