feat: add vault-aware TOML publish manifest

[Restuta]

Summary

• add a vault-aware committed manifest at .pubmd/pages.toml for files published from inside an Obsidian vault
• detect the nearest .obsidian/ root automatically and store source paths relative to that vault root
• use the manifest as first-class publish state for namespace/page ID/slug reuse so republishing stays stable even from a different working directory
• keep the existing .pub file as local working-state cache
• document the new manifest in the README and progress log

Why

For Obsidian vault workflows, .pub is useful local state but not good shared repository knowledge. A committed TOML manifest makes it clear which vault notes map to which published pages and lets the CLI preserve those mappings across machines and working directories.

Verification

• npm run verify
• CLI smoke-tested on a local pubmd server:
  • published a note from vault/notes
  • confirmed .pubmd/pages.toml was created with source = "notes/vision.md"
  • republished the same note from the vault root with a different local mapping file
  • verified the published URL stayed the same and the served page returned the updated body content

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
publish-it	Ready	Preview, Comment	Mar 27, 2026 0:47am