agentic-engineering-harness 0.6.21 → 0.6.23

package/skills/audit-consolidation-protocol/SKILL.md

@@ -0,0 +1,16 @@
+---
+name: audit-consolidation-protocol
+description: Consolidate audit reviewer evidence into one provenance-complete prioritized result.
+license: Apache-2.0
+---
+# Audit Consolidation Protocol
+
+Use only for semantic consolidation after bounded audit reviewers finish.
+
+1. Account for every source finding ID exactly once at set level; semantic duplicates may be merged.
+2. Preserve the strongest concrete evidence, impact, and severity when merging duplicates.
+3. Keep findings separate when root cause or remediation differs.
+4. Treat deterministic validation outcomes as authoritative evidence and never rewrite them.
+5. Surface conflicting reviewer conclusions and missing evidence explicitly.
+6. Prioritize remediation by severity, blast radius, lifecycle risk, and dependency order.
+7. Produce a compact phased roadmap from the consolidated findings; do not invent work unsupported by evidence.

package/skills/structured-output-delivery/SKILL.md

@@ -1,22 +1,23 @@
 ---
 name: structured-output-delivery
-description: Deliver machine-consumed AEH agent results as valid JSON that satisfies the runtime output contract.
+description: Deliver machine-consumed AEH agent results through the controller-owned structured result channel.
 license: Apache-2.0
 ---
 # Structured Output Delivery
 
-This skill governs delivery format only. It never changes the task conclusion, findings, evidence, or lifecycle authority.
+This skill governs delivery only. It never changes the task conclusion, findings, evidence, or lifecycle authority.
 
 When AEH supplies an output contract or JSON Schema:
 
 1. Treat the schema as authoritative and machine-consumed.
-2. Return exactly one JSON value matching that schema as the final result.
-3. Use ordinary ASCII JSON syntax. String delimiters must be U+0022 (`"`); never use typographic quotes such as `“` or `”`.
-4. Do not wrap the JSON in Markdown fences, headings, bullets, or explanatory prose.
-5. Do not omit required fields, rename fields, or invent undeclared fields to make serialization easier.
-6. Preserve the semantic result already established by the task. Formatting repair must not add findings, remove findings, rerun tools, or change conclusions.
-7. If the transport cannot return native structured output and AEH explicitly requests the marker fallback, return exactly one line in this form:
+2. Preserve the semantic result already established by the task. Delivery repair must not add findings, remove findings, rerun tools, or change conclusions.
+3. If the capability-scoped `aeh_submit_result` tool is available, call it exactly with the final contract object. Do not supply operation ids, agent ids, contract names, paths, or lifecycle state; those are controller-bound.
+4. A successful `aeh_submit_result` call is the authoritative delivery. Do not call it again with a different payload. If the provider requires a native structured final response, it may repeat the same object only for transport compatibility.
+5. If the tool rejects the payload, correct only the reported schema/serialization defect and resubmit the same semantic result.
+6. If no result-sink tool is available, return exactly one JSON value matching the schema. Use ordinary ASCII JSON syntax; string delimiters must be U+0022 (`"`), never typographic quotes.
+7. Do not wrap JSON in Markdown fences, headings, bullets, or explanatory prose.
+8. Only when AEH explicitly requests the legacy marker fallback and no result-sink tool is available, return exactly one line:
 
 `AEH_RESULT_JSON=<valid compact JSON>`
 
-Before completing the turn, check syntactically that the payload could be parsed by a standard JSON parser and that enum values and required fields match the supplied contract.
+Before completing a fallback delivery, check syntactically that a standard JSON parser can parse the payload and that enum values and required fields match the supplied contract.