Add architecture and gateway diagrams (used by the README)
9e6d9ab
Add the plugin settings page from a real editor
- Quick Start and Connecting Clients show the Native MCP section with
Enable Native MCP Server highlighted, at the step that asks for it
- Configuration shows the whole MCP Automation Bridge settings page
(label and value columns joined so it stays readable). This project has
Require Capability Token off, so the image and caption say it is on by
default.
3bc10fd
Document the native route from real replies
Checked against a live editor on the native HTTP route:
- the native gateway names capabilities by tool + action only; the
capability id selector exists on the stdio route alone, so examples now
use tool + action and the id is described as stdio-only
- native browsing starts from the 23 internal tools (describe with no
selector), and a native describe reply carries no nextCall
- native consent grants include a single-use nonce (replays answer
CONSENT_REUSED); stdio grants have none
- search rows, describe replies and errors on Using the Gateway are real
native replies; a new table lists every difference between the routes
- Connecting Clients shows real LogMcpNativeTransport lines: each call is
logged under the internal tool and action it was routed to
d080322
Home: absolute image URLs, so the page never depends on the /wiki/Home redirect
3266662
Add real editor screenshots and page header strips
- Home gets a "See it in action" section: a real Unreal Editor 5.8
screenshot with the plugin's status-bar indicator ringed
- a 2x close-up of the status bar (MCP :3000 (1)) at the connection
checkpoints on Quick Start, Connecting Clients and Troubleshooting
- every page opens with a slim header strip in the Home banner's
Blueprint-graph style: section colour, section and page name, a short
headline, and a small node graph that illustrates the page
- the Quick Start steps diagram is folded into its header strip
6b0c23b
Home: neutral editor group fill that suits light and dark themes
b23db0d
Stack side-by-side code examples so they fit narrower screens; plain tip inside the FAQ accordion
7255685
Development: stack the repository layout tables instead of nesting them
6c9ed30
Make the wide diagrams legible
Home and Security flowcharts now run top to bottom, so GitHub no longer
shrinks them to fit; the route question on Connecting Clients is a box
instead of an oversized diamond; the Development call flow has four
participants and short messages, and its repository tree became two
tables that wrap instead of scrolling sideways.
4dc6f5d
Redesign the wiki pages
The content stays; the presentation is rebuilt so pages can be scanned
instead of read top to bottom:
- Home is a landing page: an original banner (a Blueprint-style node
graph, no Epic marks), release/npm/engine badges, feature cards, a
styled architecture diagram, and a card grid for every page
- diagrams where a flow is easier to see than read: the quick-start
steps, route choice, the search/describe/execute sequence, the
security checks a request passes, the capability mindmap, and how a
call flows through the code
- GitHub callouts for tips and warnings, collapsible blocks for long
replies and per-client configs, a collapsible FAQ, a symptom index on
Troubleshooting, and before/after calls side by side on Upgrading
- one icon per page, shared by the sidebar, the Home cards and the new
previous/next navigation at the foot of every page
Also removes the temporary render test page.
97b46ad
Temporary render test page and banner asset
91e43b0
Drop page headings that repeat the wiki page title
GitHub already shows the page name above each page, so the H1 on every
page but Home appeared twice.
764ec81
Rewrite the wiki for the 0.6 line
The wiki described 0.5.18: 36 tools called directly, port 8091, WASM and
other settings that no longer exist. It now documents what dev ships:
- one public tool, `unreal`, with search / describe / execute / configure,
shown with real requests and replies
- both connection routes (native HTTP and stdio), per-client configs, and
the capability-token header native HTTP clients must send by default
- plugin settings and every environment variable the server reads, with
the defaults taken from the code
- security (tokens, LAN access, scopes, consent, refusal codes),
resources and prompts, troubleshooting by symptom, upgrading from 0.5.x,
and a contributor page
New pages: Connecting-Clients, Using-the-Gateway, Security,
Resources-and-Prompts, Upgrading, Development, plus a footer.
e132332
Refactor wiki: sync with codebase, simplify MCP config, add all 36 tools
97bc066
Remove old beta pages - keep only 7 core pages
82ca9b3
Add Quick Start and FAQ pages, update sidebar navigation
bf007d3
Replace wiki with main branch documentation - simplified 6 pages
8298e7f
Add 5 new wiki pages: Core Tools, World Building, Gameplay Systems, Utility Tools, API Documentation
21b01be
Fix sidebar - remove broken links to non-existent pages
6c6ca25