close_session is end_browser, and it keeps the session
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
b2c37bc
open_session: switching browser ends the one you are holding
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
b961d4d
Administration: End browser lives in the detail toolbar
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
12b0a7f
A flow session is the thing; a browser is something it holds
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
61d8fd9
Administration: ending a session by hand, and the browser marks
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
c1d0b4d
Regenerate: the spec is built in-process, not read from a file
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
3dc2ca2
Add notes/, and document choosing a browser
The hand-written prose moves back in here from the server repo's wiki-notes/,
now as notes/<tool>.notes.md. The suffix is what makes that safe: a wiki page
is addressed by basename whatever directory it sits in, which is why a bare
notes/<tool>.md shadowed the page it belonged to and had to be removed.
open_session gains a browser argument, so the pages regenerate with it and
notes/open_session.notes.md covers what the schema cannot: that a session
cannot switch browser, that the Grid has to offer the one you ask for, and
that a reaped session comes back as the same browser.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
300e4e0
Remove notes/ — it was shadowing the pages it belonged to
A GitHub wiki addresses a page by basename regardless of directory, so
notes/screenshot.md and screenshot.md both answered to /wiki/screenshot — and
GitHub served the fragment. The page looked like it had lost everything but its
prose while the file on disk, and the raw content GitHub served, were perfect.
The notes are generator input, not pages, so they now live in the repo at
wiki-notes/ and are folded in at generation time as before.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2a8fe94
temp: probe is now a verbatim copy of screenshot.md
f818f58
temp: probe with the exact generated banner
8a72d9e
temp: probe gollum rendering
53a158d
Add the manual: installing, deployment, sessions, administration, actions
Focused on using and installing this, not on notes about building it. The README
is the tour and is capped at Docker Hub's 25,000 bytes; this is where depth goes.
The fourteen action pages are generated by scripts/generate_wiki.py from
openapi.yaml, which is itself generated from the live MCP tool schemas. Hand
written, they would be wrong within a month and each would drift into its own
format; generated, they share one shape and cannot describe a server that is not
the one that shipped. Prose a schema cannot express goes in notes/<tool>.md and
is included into the page, so regenerating never flattens it.
_Sidebar.md and _Footer.md are the GitHub wiki special pages, rendered on every
page — the sidebar is the only navigation a wiki has, since pages cannot be
grouped into folders.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
0192cc9