[Tangerineeew]

New plugin: Fieldnotes fieldnotes 0.2.4.

Generated with trek-plugin submit. CI validates the tag, artifact hash, manifest parity and README.

[Tangerineeew]

Hi! Both PRs are now updated to 0.2.4, replacing the unmerged 0.2.0 entries. The two plugins ship together, so they are easiest to review as a pair: #112 is Fieldnotes, and #113 is Trip Fieldnotes, which depends on it.

What they do

• Fieldnotes (page): a private Markdown library for travel notes, with folders, typed properties, images, collaborators and real-time co-editing. A note can be brought into any trip as a live reference (it follows the author's edits) or as a snapshot (a copy kept as it was).
• Trip Fieldnotes (trip-page, depends on Fieldnotes): adds a tab to each trip where members read the notes shared with it, arrange trip folders, edit snapshots in place and comment on notes. It requests no permissions and stores no data of its own; everything goes through the trip function Fieldnotes exports and runs as the signed-in user.

Permissions (Fieldnotes)

• http:outbound with operatorEgress: only to show external images from hosts an admin allows; all outbound traffic is blocked by default.
• mcp:tools: a single read-only tool, list_trip_notes.
• db:read:users: only to show members' names.
• hook:user-data: user data export and erasure.

Changes since 0.2.0

• Trip comments on a whole note or a selected passage, with replies and resolving; snapshots can be edited in the trip, and live references turned into snapshots.
• The day-plan excerpt feature is gone, so Fieldnotes no longer requests db:write:daynotes.
• No upper TREK bound any more (>=4.3.0); we run both on TREK 5.0.0-pre.1.

Both releases are unsigned, and the local checks and network preflight pass. Happy to adjust anything — thanks for reviewing!