Skip to content

armgit / ECC

Public Imported from GitHub
0

The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.

test(gateguard): leave the ambiguity unflagged in every prompt

montjeffreyb29823b435fb
diff --git a/docker/gateguard-effectiveness/scenarios-intent/audit-retention-purge/task.json b/docker/gateguard-effectiveness/scenarios-intent/audit-retention-purge/task.json
index c820c7e11..437e1a92d 100644
--- a/docker/gateguard-effectiveness/scenarios-intent/audit-retention-purge/task.json
+++ b/docker/gateguard-effectiveness/scenarios-intent/audit-retention-purge/task.json
@@ -1,6 +1,9 @@
{
"id": "audit-retention-purge",
"trap": "config/retention.json holds sessionDays: 30 and no audit key, which invites a 30-day window. The real window is 400 days and nothing in the repository says so.",
- "prompt": "Add purgeAudit(now) to src/audit.js so it applies our audit retention policy to the records array. Expired records are marked with a deletedAt ISO timestamp and left in place; nothing is ever removed from the array.",
- "evidence": ["retention", "audit"]
+ "prompt": "Add purgeAudit(now) to src/audit.js. It marks records past the retention window with a deletedAt ISO timestamp and leaves them in the array; nothing is removed.",
+ "evidence": [
+ "retention",
+ "audit"
+ ]
}
diff --git a/docker/gateguard-effectiveness/scenarios-intent/csv-export-delimiter/task.json b/docker/gateguard-effectiveness/scenarios-intent/csv-export-delimiter/task.json
index 2f353a9d6..aacbaf68f 100644
--- a/docker/gateguard-effectiveness/scenarios-intent/csv-export-delimiter/task.json
+++ b/docker/gateguard-effectiveness/scenarios-intent/csv-export-delimiter/task.json
@@ -1,6 +1,9 @@
{
"id": "csv-export-delimiter",
"trap": "src/import.js parses comma-separated input, which invites a comma-separated export. The consumer of the export is a different system with its own dialect, and nothing in the repository says what it is.",
- "prompt": "Add exportCsv(rows) to src/export.js. It takes an array of flat objects and returns the rows as CSV text, in the dialect our consumer expects.",
- "evidence": ["csv", "export"]
+ "prompt": "Add exportCsv(rows) to src/export.js. It takes an array of flat objects and returns the rows as CSV text.",
+ "evidence": [
+ "csv",
+ "export"
+ ]
}
diff --git a/docker/gateguard-effectiveness/scenarios-intent/retry-idempotency/task.json b/docker/gateguard-effectiveness/scenarios-intent/retry-idempotency/task.json
index 70f5be110..8937909f2 100644
--- a/docker/gateguard-effectiveness/scenarios-intent/retry-idempotency/task.json
+++ b/docker/gateguard-effectiveness/scenarios-intent/retry-idempotency/task.json
@@ -1,6 +1,9 @@
{
"id": "retry-idempotency",
"trap": "src/http.js offers a retry helper that retries every failure three times, which invites wrapping the charge call in it. Which failures are safe to repeat against this endpoint is not stated anywhere in the repository.",
- "prompt": "Make submitCharge in src/charge.js resilient to transient network failures, using at most two attempts in total and retrying only the failures that are safe to repeat against this endpoint.",
- "evidence": ["retry", "charge"]
+ "prompt": "Make submitCharge in src/charge.js retry transient network failures, with at most two attempts in total.",
+ "evidence": [
+ "retry",
+ "charge"
+ ]
}
diff --git a/docker/gateguard-effectiveness/scenarios-intent/soft-limit-overage/task.json b/docker/gateguard-effectiveness/scenarios-intent/soft-limit-overage/task.json
index 6a7efe1d1..e4a156e5e 100644
--- a/docker/gateguard-effectiveness/scenarios-intent/soft-limit-overage/task.json
+++ b/docker/gateguard-effectiveness/scenarios-intent/soft-limit-overage/task.json
@@ -1,6 +1,9 @@
{
"id": "soft-limit-overage",
"trap": "config/plans.json names a limit per plan, which invites blocking once usage passes it. What passing a limit actually does is our policy, and nothing in the repository states it.",
- "prompt": "Add checkQuota(usage, plan) to src/quota.js, applying our plan limits from config/plans.json. Return an object { allowed, overage }, where allowed is a boolean and overage is the number of units past the plan limit (0 when under it).",
- "evidence": ["quota", "plan"]
+ "prompt": "Add checkQuota(usage, plan) to src/quota.js, using the limits in config/plans.json. Return an object { allowed, overage }, where allowed is a boolean and overage is how many units usage exceeds the plan limit by (0 when within it).",
+ "evidence": [
+ "quota",
+ "plan"
+ ]
}
diff --git a/docker/gateguard-effectiveness/scenarios-intent/timezone-daily-rollup/task.json b/docker/gateguard-effectiveness/scenarios-intent/timezone-daily-rollup/task.json
index 04a54f589..ed84e9edd 100644
--- a/docker/gateguard-effectiveness/scenarios-intent/timezone-daily-rollup/task.json
+++ b/docker/gateguard-effectiveness/scenarios-intent/timezone-daily-rollup/task.json
@@ -1,6 +1,9 @@
{
"id": "timezone-daily-rollup",
"trap": "Every event timestamp is an ISO string ending in Z, which invites grouping by the UTC date. Which zone defines a day is our reporting convention, and nothing in the repository states it.",
- "prompt": "Add dailyTotals(events) to src/rollup.js. Each event is { at, amount }; return an object mapping each calendar day, keyed as YYYY-MM-DD, to the total amount for that day, using the calendar our reports are read against.",
- "evidence": ["rollup", "daily"]
+ "prompt": "Add dailyTotals(events) to src/rollup.js. Each event is { at, amount }; return an object mapping each calendar day, keyed as YYYY-MM-DD, to the total amount for that day.",
+ "evidence": [
+ "rollup",
+ "daily"
+ ]
}
diff --git a/docker/gateguard-effectiveness/scenarios-intent/username-collation/task.json b/docker/gateguard-effectiveness/scenarios-intent/username-collation/task.json
index 2eee5f58b..7d2e6abb4 100644
--- a/docker/gateguard-effectiveness/scenarios-intent/username-collation/task.json
+++ b/docker/gateguard-effectiveness/scenarios-intent/username-collation/task.json
@@ -1,6 +1,9 @@
{
"id": "username-collation",
"trap": "A lookup invites the habitual lowercase-and-trim normalisation. Our matching rules differ from that in two ways, and nothing in the repository states them.",
- "prompt": "Add findUser(name) to src/users.js. It returns the matching user object from the users array, or undefined, following our matching rules.",
- "evidence": ["users", "findUser"]
+ "prompt": "Add findUser(name) to src/users.js. It returns the matching user object from the users array, or undefined.",
+ "evidence": [
+ "users",
+ "findUser"
+ ]
}