1.0.0

This is the companion plugin promised in Local REST API 5.0.2, which
removed periodic-note support from the core plugin so it could drop its
dependency on periodic-note plugin internals. It restores the /periodic/
REST endpoints and the periodic_note_get_path MCP tool using the host's
public API extension interface, so the functionality returns without the
dependency going back into the core.

Requires Local REST API providing extension API version 2 or later, plus
the core Daily Notes plugin and/or the community Periodic Notes plugin
configured for the periods you intend to use.

• Adds /periodic/{period}/ and
  /periodic/{period}/{year}/{month}/{day}/ for GET, PUT, POST, PATCH,
  and DELETE, where {period} is one of daily, weekly, monthly,
  quarterly, or yearly. A trailing path segment targets a heading or
  block within the note, exactly as it does under /vault/.
• Adds a periodic_note_get_path MCP tool returning the vault-relative
  path of the current periodic note for a period, creating the note if
  it does not exist.
• Delegates all folder, format, template, and creation logic to the
  Daily Notes (core) and Periodic Notes (community) plugins via
  obsidian-daily-notes-interface, the same model Local REST API used
  before its since-removed native implementation. Configure periodic
  notes in those plugins; a period that is not enabled there returns
  400.
• Note for clients migrating from Local REST API 4.x: the periodic
  routes now resolve the target note and redirect (307) to the host's
  /vault/{path} endpoint rather than serving content inline, so
  content negotiation and write semantics stay identical to /vault/
  and no host-private methods are reproduced here. Clients must follow
  redirects, which preserve the method, body, and headers.