What was decided, what was measured, and what is still open. None of this
ships: .vscodeignore keeps docs/ out of the .vsix. The code says how
things work; these notes say why, so read the one that covers an area before
changing it.
| Note | Covers | Read it before |
|---|---|---|
automation-boundary.md |
where each automated step sits on the "inert and reversible vs persistent or global" line, and what was measured about asking for shared memory | adding or changing anything GemDB does without asking |
grail.md |
how the Grail payload is built and staged, the Python↔GCI bridge (exit codes, input(), print(), encoding), and the gotchas found building on it |
touching the bridge or building an application on Grail |
mcp-server.md |
the bundled MCP server: payload, session cost and leak, read-only mode, stop order, client registration | changing how the MCP server is built, started, stopped or exposed |
repository-space.md |
the 10 GB cap, reserved on disk, and the free-space threshold; what the stone does below it (stops reclaiming garbage, refuses and ends gemdb sessions); the gemdb account and what needs DataCurator; why idle sessions are aborted; what a garbage collection has to wait for |
changing the stone's space settings, garbage collection, database accounts, or anything that holds a session open |
statistics.md |
GemDB Stats in a webview: why a webview, the message protocol with GemDB Stats, where the web build comes from and what bundle-stats.mjs checks and changes; how the database records its own statistics and how they are pruned; and what is still unmeasured |
changing how statmon files are opened, how the GemDB Stats build is bundled, or what the stone's statmonitor records |
reaching-windows.md |
the options for a Windows story (WSL, remote server, Docker) and what still needs a Windows machine | starting any Windows work |
demo/ |
one self-contained directory per demo, with measured findings | building something a demo already explored, or adding a demo |