kdd-gates: KDD methodology gates as native Tools

[MauricioPerera]

kdd-gates — KDD methodology as native Tools

Repo: https://github.com/MauricioPerera/kdd-gates

A composition plugin that exposes KDD (Knowledge-Driven Development)'s deterministic gate scripts as model Tools:

• kdd_validate — Level-1 core gates (validate_contracts + validate_okf)
• kdd_seal — freezes an oracle's hash for the task contract's tests_sha256
• kdd_perimeter — checks a diff against a contract's touch_only, catches TESTS_TOUCHED/OUT_OF_PERIMETER
• kdd_preflight — dry-run of all 19 gates, with real sandbox escalation (sandboxPermissions + justification, goes through the actual approval service — no bypass) and a run_in_background mode for the full-suite run

It also injects a systemPrompt section teaching the agent the oracle-first workflow (freeze the test before implementing, validate the contract before writing code, perimeter-check after), so it doesn't need to be re-explained per task.

It doesn't reimplement anything — it's a thin wrapper that shells out to the KDD template's own scripts/*.py on whatever repoRoot you point it at.

Built against two bugs found along the way

Building this surfaced two harness issues, documented and reported here:

• #4747 — object/oneOf tool-call params arriving as raw strings for some models. Worked around by keeping every kdd_* parameter schema fully typed (string/array/boolean, no bare oneOf, no untyped type: "json").
• #4796 — ctx.subprocess.spawn() hangs on Windows when the spawned process has its own nested subprocess children. kdd_preflight wraps preflight.py (which spawns ~19 grandchildren) through ctx.shell instead, which doesn't exhibit the hang.

Both are documented in more detail in the repo's README, along with a third fix (a .kdd-tmp recursive self-copy caused by putting the scratch temp dir inside the repo — moved it outside).

Verified end-to-end against both the KDD template repo directly and a project instantiated from it via scripts/init_project.py --apply — same result both times, including a full oracle → seal → contract → validate → implement → perimeter cycle.

MIT licensed, tagged dsh-plugin.

[MauricioPerera]

Cross-reference: the KDD methodology this plugin wraps is announced separately in #4799.

[MauricioPerera]

Follow-up: built a second plugin, gh-discussions, that lets the agent search/create/comment on GitHub Discussions directly instead of me shelling out to gh api graphql by hand — used it to file the announcement for that one.

[MauricioPerera]

Two more follow-ups in this batch: bench (LM Studio / Ollama latency+tok/s comparator) and kdd-scaffold (generates the task contracts this plugin validates).

[MauricioPerera]

Also documented here: enforcing the implementer/validator split mechanically with a toolFilter-restricted dsh-tool-subagent instance — not a new plugin, just config on top of this one's tools.