v0.2.0

Every bundled document is now reachable over MCP

SKILL.md directs the agent to the command playbook, the evidence policy, the connection guide, and the native guidance using relative filesystem paths. Only niblet://skill was registered, so a client reading it over stdio received four links it had no way to resolve — the entire 26-command playbook was unreachable.

All five documents are served as resources:

• niblet://skill
• niblet://skill/commands
• niblet://skill/connection
• niblet://skill/evidence
• niblet://skill/native

Their cross-links are rewritten to niblet:// URIs in the resource handler rather than in the files, because the same directory is also loaded as a filesystem skill where the relative paths are correct.

New tools

niblet_help — lists the four surface modes and all 26 commands with their purpose, or resolves a single command with command: "polish". Parsed from the documents at runtime, so the menu cannot drift from the playbook.

niblet_status — implements the doctor entry the playbook specifies but never shipped: configured origins, whether a usable token is present (length only, never the value), which bundled documents are readable, the tool inventory, and whether the API answers.

Both read bundled files, require no token, and are local-only. The find_ui_references and find_ui_materials contracts are unchanged and remain identical to the hosted service.

Notes

• Status treats any HTTP status as reachable. /v1/stats is not part of the hosted contract, so probing it as a health check would have reported a failure to every default-configured user on a healthy connection.
• No retries were added; "no retry was attempted" remains a deliberate stance.
• 62 tests pass, including live resources/list coverage — a resource that registers but never lists is the failure unit tests cannot catch.