fix(aidd-context): generate native Kilo and current OpenCode artifacts

[waewoo]

Problem

The aidd-context artifact generators promise to write rules, agents, commands, and skills for the AI tools detected in a host project.

Their per-tool references omit Kilo. In addition, 05-rule-generate says OpenCode has no rules surface, although OpenCode supports project rules through AGENTS.md and instructions in opencode.json[c].

As a result, a project containing .kilo/ is not proposed as a target, and a Kilo user receives no native location or format when generating an artifact. This is independent from the pending Kilo support draft: PR #745 is neither reviewed nor merged.

Scope

• Add Kilo detection (.kilo/, kilo.json, or kilo.jsonc) to the relevant aidd-context generators and onboarding/memory references.
• Update 05-rule-generate:
  • OpenCode: offer AGENTS.md or an instructions entry in opencode.json[c].
  • Kilo: write Markdown rules under .kilo/rules/ and merge their path/glob into kilo.json[c].instructions, preserving user entries.
• Update 06-agent-generate to render Kilo agents in .kilo/agents/<name>.md with compatible frontmatter.
• Update 07-command-generate to render Kilo workflows in .kilo/commands/<name>.md.
• Update 04-skill-generate to recognize Kilo. It may explicitly offer shared .agents/skills/ when both OpenCode and Kilo are selected, but must not select it silently.
• Update 08-hook-generate to state that OpenCode and Kilo hooks require a JavaScript/TypeScript plugin, not declarative hooks.json.
• Update 02-project-memory and onboarding detection so a Kilo project can be wired through AGENTS.md.

Acceptance criteria

• A project containing only .kilo/ is detected and Kilo is proposed by each applicable generator.
• A Kilo rule is written under .kilo/rules/ and referenced by kilo.json[c] without deleting existing instructions entries.
• An OpenCode rule is written to AGENTS.md or to a Markdown file referenced from opencode.json[c].instructions.
• A Kilo agent is discoverable from .kilo/agents/ and uses documented Kilo frontmatter.
• A Kilo command is discoverable from .kilo/commands/.
• Kilo is detected by project-memory and onboarding.
• Each factual tool-path claim carries a current official source and verification date.

Prior art in this repository

• 05-rule-generate rule paths contain the outdated OpenCode row and fallback guidance.
• 06-agent-generate agent paths define the existing per-tool agent rendering pattern.
• 07-command-generate command paths define the existing command output and detection pattern.
• 04-skill-generate tool detection is the skill-host detection table to extend.
• 02-project-memory tool wiring owns project tool detection and context-file selection.

Context: the intentional build limitation

The framework-build decision to skip plugin rules/ and commands was global and intentional, not a Kilo-specific omission. See the scope note on draft PR #745. This issue concerns direct generation guidance only; archive emission belongs to a separate CLI issue.

Out of scope

• Emitting plugin rules/ and commands/ in framework flat archives.
• Implementing OpenCode or Kilo hook plugins.
• Assuming that PR feat(cli): add Kilo Code support #745 will be merged.