Skip to main content
Project Notes is the first functional Webdock extension. Its repository is public under spitzli; its manifest uses kind: extension with top-level runtime fields.
The public 0.1.0-alpha.2 developer preview includes English screenshots, a public OCI image and a signed descriptor. Production installer, invocation transport and UI host integration remain release gates. The local authoring host is explicitly a fixture, not the production Console.

​
Features

  • Create, edit and delete notes within a project.
  • Project overview panel with a list, editor and optional reminder time.
  • Optimistic document revisions prevent stale updates.
  • BullMQ reminders mark notes as due in the panel. No email is sent.
  • A declared 60-second reconciliation job recovers pending or overdue reminders, including exhausted delivery retries.
  • Editing or deleting a note invalidates old reminder versions.
The plugin receives no PostgreSQL or Redis credentials. The Core data API uses the existing restricted roles and invocation-bound PostgreSQL RLS. The UI is a sandboxed iframe with a host-owned MessageChannel; host tokens stay outside the frame.

​
Limits

A project can hold 100 notes, with 100 characters per title and 5000 per body, within a 24 KiB total document. The smaller document bound keeps UI responses below the 32 KiB frame-message cap. Reminder dates are limited to seven days ahead. Deleting removes a note from the active document. Host idempotency receipts remain retained; final retention/purge policy belongs to the production host and must be completed before production rollout.

​
Local verification

Build the packed SDK and install it in the independent plugin repository as described in that repository’s README. Build and run its tests:
In the Webdock checkout, first create the owned local PostgreSQL/RLS fixture and a disposable Redis instance using the repository’s fixture workflow. Then:
The smoke test exercises actual Core HTTP services, PostgreSQL RLS, BullMQ and the plugin in an independent process. It covers project isolation, concurrent CAS writes, receipt replay, stale saves, reminders, plugin restart retention, deletion and revoked grants. Omit --smoke to keep a browser preview running; the tool prints its loopback URL. The fixture creates explicit development identities and grants. These must never be substituted for production authentication or counted as an installer verification.

​
Backend services

ctx.data.read(key) returns {value, revision}; a missing document returns both fields as null.
Writes are transactional and use a revision comparison plus immutable, operation-bound receipts. Retry unchanged input with the same request ID. Changed input with a reused ID or a stale revision is a conflict, not an overwrite. For reminders use ctx.jobs.enqueue({name, payload, idempotencyKey, runAt}) with an absolute ISO timestamp. The absolute time keeps the idempotency fingerprint stable across retries. runAt and a nonzero delaySeconds cannot be combined. See background jobs.