docs: use Deal terminology in official plugins
This commit is contained in:
+12
-12
@@ -4,22 +4,22 @@ Browser Inbox is one global queue of browser captures. New and changed records a
|
||||
stored in `captures:global`; previous `captures` and `captures:workspace:*` keys
|
||||
remain readable for migration compatibility.
|
||||
|
||||
Each capture contains `workspaceRootPath` and `processed`. An empty
|
||||
`workspaceRootPath` means the capture is **Unassigned**. The global view can filter
|
||||
all captures by assignment, workspace, processed state, and text search. A capture
|
||||
Each capture contains a durable `workspaceId`, its current or historical
|
||||
`workspaceRootPath`, and `processed`. An empty `workspaceRootPath` means the
|
||||
capture is **Unassigned**. The global view can filter all captures by assignment,
|
||||
Deal, processed state, and text search. A capture
|
||||
can be assigned, reassigned, made unassigned, marked processed or unprocessed, and
|
||||
deleted.
|
||||
|
||||
The local browser receiver adds the currently active workspace before publishing a
|
||||
capture event. When it has no active workspace, the capture remains unassigned
|
||||
The local browser receiver adds the currently active Deal before publishing a
|
||||
capture event. When it has no active Deal, the capture remains unassigned
|
||||
unless an explicit existing domain binding matches it. The frontend never assigns an
|
||||
untagged capture merely because a workspace view happens to be open.
|
||||
untagged capture merely because a Deal view happens to be open.
|
||||
|
||||
Workspace assignment currently uses the top-level vault folder path as the
|
||||
identifier because the core workspace model has no separate immutable ID. In the
|
||||
current model that path is also the displayed workspace name, so a workspace rename
|
||||
requires a later reassignment of existing captures.
|
||||
Deal assignment uses the immutable `workspaceId` stored in Deal metadata;
|
||||
`workspaceRootPath` is an address and display value. A rename updates the latter,
|
||||
while a newly created folder with the old name cannot take over existing captures.
|
||||
|
||||
Workspace Inbox and Overview show only captures whose `workspaceRootPath` exactly
|
||||
matches the selected workspace. Unassigned captures remain visible only in the
|
||||
Deal Inbox and Overview show only captures whose `workspaceId` matches the selected
|
||||
Deal. Unassigned captures remain visible only in the
|
||||
global Browser Inbox.
|
||||
|
||||
+14
-16
@@ -2,12 +2,12 @@
|
||||
|
||||
Todos are stored by the official `verstak.todo` plugin under the canonical
|
||||
`todos:global` settings key. A todo is global when `workspaceRootPath` is empty;
|
||||
otherwise that field identifies the top-level workspace folder that owns it.
|
||||
otherwise that field identifies the top-level Deal folder that owns it.
|
||||
|
||||
The global Todos view aggregates all records and supports workspace, status, text,
|
||||
and due/reminder/updated sorting filters. The workspace Todos view shows only
|
||||
records whose `workspaceRootPath` exactly matches the current workspace. This
|
||||
keeps unassigned and other-workspace records out of a workspace tab and its
|
||||
The global Todos view aggregates all records and supports Deal, status, text,
|
||||
and due/reminder/updated sorting filters. The Deal Todos view shows only records
|
||||
whose `workspaceRootPath` exactly matches the current Deal. This keeps unassigned
|
||||
and other-Deal records out of a Deal tab and its
|
||||
Overview signals.
|
||||
|
||||
## Stored fields
|
||||
@@ -20,15 +20,15 @@ Each record has a stable `id`, `title`, optional `description`, optional
|
||||
|
||||
## Reminders
|
||||
|
||||
The plugin stores reminder metadata and renders clear indicators for overdue,
|
||||
due-soon, and reminder-due todos. Verstak does not yet have a notification
|
||||
scheduler, so a reminder does not create a native desktop notification or run in
|
||||
the background.
|
||||
The plugin stores reminder metadata, renders clear indicators for overdue,
|
||||
due-soon, and reminder-due todos, and schedules native desktop notifications when
|
||||
the Desktop notification capability is available. Without that capability, the
|
||||
reminder remains visible in Todos but is not treated as an error.
|
||||
|
||||
## Completed Todo to Journal
|
||||
|
||||
From a workspace Todo tab, a completed todo exposes **Create Journal Entry**. It
|
||||
opens the current workspace Journal with a normal, editable form. The form copies
|
||||
From a Deal Todo tab, a completed todo exposes **Create Journal Entry**. It opens
|
||||
the current Deal Journal with a normal, editable form. The form copies
|
||||
only factual data from the todo: title, description, completion date, and zero
|
||||
minutes. It never generates a summary, duration, or billable status.
|
||||
|
||||
@@ -40,8 +40,6 @@ own record.
|
||||
|
||||
## Visibility
|
||||
|
||||
The Plugin Manager can globally enable or disable the Todo plugin. The current
|
||||
workspace host has no per-workspace or template-level contribution filter yet, so
|
||||
a globally enabled Todo plugin contributes its tab to every workspace. Template
|
||||
visibility will be handled with the workspace/template model rather than by a
|
||||
Todo-specific exception.
|
||||
The Plugin Manager can globally enable or disable the Todo plugin. A Deal template
|
||||
controls whether its Todos tab is available; disabling the plugin hides the tab
|
||||
without affecting stored todo records.
|
||||
|
||||
Reference in New Issue
Block a user