chore: publish from main

agents/gem-devops.agent.md

@@ -36,7 +36,7 @@ MANDATORY: Adhere strictly to the defined workflow and rules below:no improvisat
 
 IMPORTANT: Batch/join dependency-free steps; serialize only true dependencies while still covering every listed concern.
 
-- Start with `context_envelope_snapshot` as active execution context:
+- Start with `plan_context_snapshot` as active execution context:
   - Use `research_digest.relevant_files` as the initial file shortlist.
   - Use `reuse_notes` (path + trust level) to guide which files to trust vs re-verify.
   - Apply config settings: Read `config_snapshot` for:
@@ -58,7 +58,7 @@ IMPORTANT: Batch/join dependency-free steps; serialize only true dependencies wh
   - Dry-run before apply: For infra changes (kubectl, terraform, helm), run diff/plan first, review, then apply.
 - Verify:
   - Health checks, resource allocation, CI/CD status.
-- Failure: Apply mitigation from failure_modes. Log to `docs/plan/{plan_id}/logs/`.
+- Failure: Apply mitigation from failure_modes.
 - Output
   - Return minimal JSON per `output_format` below.
 
@@ -139,7 +139,7 @@ JSON only. Omit nulls/empties/zeros. Prose fields MUST use dense bullet format.
   "approval_reason": "string",
   "approval_state": "not_required | pending | approved | denied",
   "health_check": "pass | fail",
-  "learn": ["string: max 5"]
+  "learn": [{ "text": "string", "confidence": "0.0-1.0" }]
 }
 ```
 
@@ -171,6 +171,7 @@ MANDATORY: These rules are mandatory for every request and apply across all work
 
 ### Constitutional
 
+- Library-first: Prefer well-established, actively maintained libraries (official or already in the stack) over custom implementations.
 - All ops idempotent. YAGNI, KISS, DRY.
 - Atomic ops preferred.
 - Verify health checks pass before completing.