Replacing a stale directory tree diagram with where it installs
The Framework artifact tab on the MemStack Pro site showed a project directory structure with a .claude/ junction, .claude/rules/ as always-on rules, a project .mcp.json, and a start-memstack.bat link command. The premise was wrong. MemStack installs once globally and a project keeps CLAUDE.md.
Killed the tab instead of patching it
Patching individual rows would have preserved a project-shaped diagram for a product that is not project-shaped. I replaced it with a tab named "Where It Lives" showing two blocks: the install and the project. The contrast is the content.
Free skills are SKILL.md under the plugin marketplace skills directory. Pro skills download to ~/.memstack/pro-skills/<slug>/SKILL.md. The MCP server is registered at user scope so no .mcp.json lands in the project. The only files MemStack puts in a project are CLAUDE.md, plus .claude/STATE.md if the State skill is used and memory/sessions/*.md if the Diary skill is used. All three are skill-written on demand, none are installed.
The start-memstack.bat claim
I almost reported that start-memstack.bat link does not exist. It does. It still ships in the plugin and still runs mklink /J. What is true is narrower: it is not the documented install path, is Windows-only, and junctions a .claude/ full of agent-runner internals. The site now stops advertising it.
First-run index build
Getting Started never mentioned the first-run index build. Its only troubleshooting entry told a user who saw silence that they had installed onto the wrong Python. A healthy install following that advice gets torn down. I added a first-run note inside Step 4 where the user is actually waiting, added a "hangs on first start" entry, and put it above the interpreter-mismatch entry.
Other corrections
I verified three more claims against loader source. Skills are SKILL.md in the plugin and ~/.memstack/pro-skills, not .claude/rules/. No installer handles symlinks because there is no installer. The dashboard is 8 pages, counted from the nav in dashboard.html. Opus 4.8 is no longer the newest model now that Fable 5, Opus 5 and Sonnet 5 ship in the selectors.
I removed the TokenStack pillar's "20% over the last 30 days" instead of dating it. Nothing in the repo records which window the figure came from, so dating it would have meant inventing a month to make an unverifiable claim look verifiable.
FAQ audit
I audited the other six FAQ answers and found the flagged one was partly the opposite of what the audit assumed. Pro skills do auto-update. A startup version probe under a 24h TTL force-re-downloads on a version change. What is incomplete is the reindex half. One answer is outright wrong, two have minor gaps, two are clean. I shipped the wrong answer as its own commit after the first deployed, scoped to that single entry. The upgrade FAQ said to set a licence key and run the installer. There is no installer. The path is activate_license with key and email.
Verification
First verification pass looked like a total failure. All nine retired phrases still present in .next. They were all in .next/cache/webpack/*.pack, the build cache, not shipped output. I deleted .next, rebuilt clean, then grepped .next/static and .next/server only.
The homepage HTML did not contain "Where It Lives" after deploy. FrameworkArtifact is a dynamic() import, so the tab label lives in a lazily-loaded chunk. Verifying it shipped meant extracting the 13 chunk URLs the live page references, fetching each, and finding the string in app/page-*.js with the old label absent from all 13.
First live poll after the second deploy still served the old FAQ text. The deploy had not cut over. Second poll 25s later had it. A single fetch after a push proves nothing.