feat(cli): add Kilo Code support

[waewoo]

🎯 What & why

Add native Kilo Code support so AIDD can be installed and released for Kilo instead of relying on the OpenCode layout that Kilo no longer discovers.

🛠️ How it works

The new Kilo tool adapter maps skills, agents, commands, rules, MCP configuration, and flat plugins to .kilo/ and kilo.json. A dedicated flat build contract namespaces skills and subagents, merges MCP servers, and feeds a new kilo:flat release cell. The README documents the generated archive and installation flow.

🔌 Required lifecycle-plugin completion

Before this PR is ready to merge, the Kilo flat contract must support the native lifecycle-plugin adapter now tracked by #744:

• translate relevant AIDD hooks.json definitions into generated project plugin code under .kilo/plugin/ instead of dropping hooks from the flat distribution;
• cover the aidd-context project-memory synchronization use case at Kilo's verified session-start equivalent, while reusing the existing shared synchronization behavior;
• validate Kilo's plugin API and event mapping independently — the OpenCode-generated bridge added by feat(cli): one shared framework source per machine, user scope and session telemetry #795 is prior art, not a runtime-compatible implementation to copy unchanged;
• preserve safe, non-blocking behavior when memory is absent or markers are malformed; and
• add unit, integration, golden, and real Kilo runtime smoke coverage proving plugin discovery and event delivery.

The existing Kilo agent output (.kilo/agents/) remains separate from this executable plugin bridge.

🧪 How to verify

• pnpm --dir cli typecheck
• pnpm --dir cli lint
• Run the 128 targeted unit tests covering Kilo, registries, assets, catalogs, and setup.
• pnpm --dir cli test:e2e tests/golden/framework-build-golden.e2e.test.ts
• Build kilo:flat, then run Kilo CLI debug skill and agent list; the smoke project discovers 47 skills and both AIDD subagents.
• Run the added Kilo plugin runtime smoke test, confirming that the generated project plugin loads and its session-start-equivalent event triggers the guarded project-memory synchronization exactly once.

🔗 Linked issue

Closes #744

✅ I certify

• I DO CERTIFY I READ EACH LINE OF THE PULL REQUEST BECAUSE I AM A SOFTWARE ENGINEER, NOT A AI PUPPY.

[waewoo]

Hi, and apologies for opening this pull request prematurely.
I realize now that I should have waited for the related issue to be reviewed and validated by a Certified Member or Maintainer, and for its status to be moved to Todo, before opening a PR.
I will of course wait for the issue to be validated and moved to Todo before proceeding further. Please consider this PR as an early draft opened ahead of the expected process.
Sorry for not following the contribution workflow, and thank you for your understanding.

[waewoo]

Follow-up scope: rules and commands

This draft only adds Kilo as a flat-build target. It deliberately retains the existing global framework-build decision for plugin rules/ and commands: every target currently warns and skips them.

That was an intentional YAGNI choice, recorded in the flat-build design: at the time, the framework shipped no plugin source in either directory. It was therefore not an omission specific to Kilo.

The situation is worth revisiting separately because aidd-context now guides users to generate rules and commands. Two follow-up issues will cover (1) Kilo/current-OpenCode guidance in those generators and (2) emitting those artifacts from OpenCode/Kilo flat archives.

This PR remains a draft and has not been reviewed, approved, or merged; neither follow-up assumes that it will be accepted.