research: write up wiki-engines landscape scan; send IAM demand to netkingdom

- Add README.md + findings.md to research/260608-wikiengines-overview/ to
  match sibling research convention (was a bare Perplexity dump). findings.md
  synthesizes the engine landscape into adapter-contract implications and maps
  to INTENT (capability heterogeneity, L0->L4 ladder, backend-neutrality).
- Mark the netkingdom integration demand as sent: capability request
  3136a9e2 (auto-routed to netkingdom) + inbox message 46c60f17.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

research/260608-wikiengines-overview/README.md

@@ -0,0 +1,32 @@
+# 260608 — Wiki engines overview (landscape scan)
+
+Date: 2026-06-08
+
+## What this is
+
+A breadth-first **landscape scan of notable wiki engines** — Wiki.js, XWiki,
+MediaWiki, Semantic MediaWiki, DokuWiki, TiddlyWiki, TWiki, Foswiki, Confluence,
+C2, Federated Wiki, Fossil — captured to understand the design space
+`shard-wiki` orchestrates over (and deliberately does **not** re-implement).
+
+Complements the deeper-dive research:
+- `research/260608-c2-wiki-origins/` — pre-federation wiki culture
+- `research/260608-federation-concepts/` — Federated Wiki, git/AP federation models
+- `research/260608-yawex-prior-art/` — the specific Perl engine being superseded
+
+Focus: what each engine is *for*, its storage/permission model, and what its
+existence implies for shard-wiki's **adapter contract** — not engine selection.
+
+## Contents
+
+| Path | Role |
+|------|------|
+| `findings.md` | Synthesis: storage/permission axes, shard-wiki mapping, adapter implications, open questions |
+| `260608-perplexity-wikiengines-research.md` | Raw source dump (Perplexity), kept as provenance |
+
+## Status
+
+Initial scan complete. Reinforces the INTENT stance that shard-wiki is an
+**orchestrator, not an engine**: the heterogeneity below is the problem space,
+not a menu to pick from. Adapter-contract implications feed
+`workplans/SHARD-WP-0002-federation-architecture.md`.