@nocobase/app-plugin-projects 0.1.0-beta.2 → 0.1.0-beta.20

package/README.md

@@ -1,6 +1,6 @@
 # @nocobase/app-plugin-projects
 
-Projects, issues, workflows, labels and members for a NocoBase application.
+Projects, issues, fixed statuses, labels and members for a NocoBase application.
 
 ## What it provides
 
@@ -17,15 +17,18 @@ Projects, issues, workflows, labels and members for a NocoBase application.
 - **Labels**: a shared label list.
 - **Kinds**: who acts on issues or is named in them. `user` (people) and `system` (the plugin's own rules) are built
   in; another plugin registers more through `projectsKindsToken` (`server/kernel/kinds.ts`): a key, a title, how its
-  ids are named, whether it may execute issues (and who may give it work), whether it may be mentioned, and which
-  moves a workflow may let it make. Executors, activity, mentions, checklist checkers, approval requesters and
-  workflow transitions name a kind by its key; the browser reads the list from `GET /api/projects/me` (`kinds`). A kind may
+  ids are named, whether it may execute issues (and who may give it work), whether it may be mentioned, the status
+  moves its principals may make (`moves`, with an optional `mayMove` check per principal and issue), and the executor
+  a new issue gets when it names none (`defaultExecutor`). Executors, activity, mentions and status moves name a kind
+  by its key; the browser reads the list from `GET /api/projects/me` (`kinds`). A kind may
   also do work (`work`, an `IssueWorkHandler`, `server/kernel/work.ts`): unless a plugin binds `projectsTriggersToken`,
   every change, comment and release is handed, in its transaction, to the work handler of each kind it concerns (the
   executor before and after, the kinds a comment mentions or answers), which answers what it started (`RunAttempt[]`;
-  `collectRunAttempts` gathers them around a call). A handler asks `projects.subtasks.blockersOf` whether the issue
+  `collectRunAttempts` gathers them around a call). A handler that opts into `observesIssueChanges` also receives creations and updates with an empty or different executor kind, once per change. Service writes pass their already authorized viewer to the observer, so nested routing need not acquire a second connection for permission reads. Issue responses and update events use the final snapshot after these transactional handlers. Creation in `in_progress` or a transition into it starts work; there is no separate start option. A handler asks `projects.subtasks.blockersOf` whether the issue
   waits for unfinished issues and then starts nothing (`skipped: 'blocked'`); it starts nothing either for an issue in
-  backlog (`BACKLOG_STATUS`, `skipped: 'dormant'`). When a new `blockedBy` holds the issue, every kind's
+  backlog (`BACKLOG_STATUS`, `skipped: 'dormant'`), or for a principal's comment past a limit the kind keeps
+  (`skipped: 'limited'`). A comment of anyone but the system reaches the handlers, with the person it
+  was written for (`CommentChange.userId`). When a new `blockedBy` holds the issue, every kind's
   `onBlocked` withdraws the work it had not taken up yet. These skips and withdrawals are recorded on the issue's
   activity as the principal's (`work_skipped`, `work_withdrawn`, with the issues it waits for). It may name the business actions a principal of the kind may be
   given at most (`actions`) and describe executors for a picker (`executor.describe`). `projects.issueContext`
@@ -34,58 +37,30 @@ Projects, issues, workflows, labels and members for a NocoBase application.
   `projects.issues.releaseExecutor(executor, { actor, name })`: every live, unfinished issue it executes is left with
   no executor, recorded as `executor_changed` with `reason: 'executorRemoved'` and the executor's name ("Executor X was
   removed" on the timeline), and handed to the triggers like any change of executor.
-- **Workflows**: the statuses of a project's issues and which kinds may move an issue between them. Every workflow
-  keeps the nine built-in statuses (backlog, todo, analysis, proposal review, in progress, in review, blocked, done,
-  cancelled); it may rename and recolour them, add its own and restrict the moves. A project picks one; a project without one, and an issue without a project, use the default workflow. The
-  plugin ships no workflow: until one is the default, they use the built-in statuses, people move freely and the
-  system closes merged work. Workflows are edited in the app (`/config/workflows`, "Workflow templates"). A
-  status may carry rules run when an issue enters it: a checklist the issue must complete before moving on (except to
-  a closed status), and a notification to the issue's owner. A move may need an approval by the issue's owner, the
-  project lead or an admin: it waits as a request until one of them approves it (the issue moves) or rejects it.
-- **Contributed status rules and templates**: other plugins add status rule types through `projectsStatusRulesToken`
-  (a key, settings validation, what entering the status does in the move's transaction, and a sentence for change
-  summaries) and workflows that use them through `projectsWorkflowTemplatesToken` (installed once each; a template
-  with `makeDefault` becomes the default when none is). The plugin installs templates in the background from its
-  `boot()` and awaits `templates.installed()` in its `ready()`, so the application serves no request before the
-  templates added while the plugins booted are workflows; code that needs them earlier awaits `installed()` itself. The
-  plugin's own types (`checklist`, `notifyOwner`, `subtasksDone`, `blockersDone`, `startOption`) follow the same contract
-  (`server/domains/workflows/built-in-rule-types.ts`) and are looked up in the same registry, in front of the
-  contributed ones; `projects.statusRules.list()` lists both. In the browser, `StatusRuleTypesContext` (`client/kit`)
-  gives each contributed type its title and hint, the categories it may sit on, its group in the editor's "Add rule"
-  menu (`action`, the default, or `condition`), an icon, the settings a new rule starts with, a settings editor and a
-  one-line summary; the plugin describes its own types the same way (`client/lib/built-in-rule-types.ts`), and the
-  editor has no case of its own for any type. The rules dialog lists the rules a status has as cards, collapsed to
-  their title and summary, and adds one from the menu ("When entering", "Entry conditions", "Automatic moves");
-  `PmExpandableTextarea` (`client/kit`) is the compact text area for long settings such as an instruction. A rule
-  whose plugin is gone stays in the definition: the editor shows it as unavailable and entering the status skips it.
-  `POST /api/projects/workflows/{workflowId}/preview` lists what saving a definition would change in the rules, and which rules wake
-  someone without anybody confirming it. A contributed type may also hold an entry condition (`canEnter`): every move
-  into a status carrying it asks it first, whoever moves (a person, an agent, a plan, an applied approval, the system
-  on an event), and a refusal is 400 with the type's own code. An exit condition (`canLeave`) is asked the same way
-  before an issue leaves a status carrying the rule.
-- **Contributed workflow events and issue marks**: other plugins register workflow events through
-  `projectsWorkflowEventsToken` (a dotted key such as `acme.merged`, and the status categories a transition on it may
-  leave and enter) and fire one for a batch of issues with `projects.workflowEvents.fire({ event, issueIds, actor?,
-note?, details? }, tx?)`: each issue moves along its workflow's `on` transition, as the system, and the activity names
-  `actor`. `projects.workflowEvents.target(event, issueId)` says where firing it would take one issue without moving it
-  (for a confirmation that says what an action will do). The plugin never knows what an event means. A transition on an event whose plugin is gone stays in the
-  definition and shows as unavailable. In the browser, `WorkflowEventsContext` (`client/kit`) titles the events for the
-  editor and the timeline. The issues pages show the list and the board, the board by default.
-- **Ways to start an issue**: a status carrying a `startOption` rule (with an optional label and hint, text or i18n
-  keys) is offered by the New issue form as a process to start in, such as "Design first" on Analysis or "Straight to
-  development" on Todo; `GET /api/projects/issues/starts?projectId=` lists them, the workflow's initial status first, and
-  nothing while no status carries the rule (the form then shows no choice). `POST /api/projects/issues` takes the choice as
-  `statusKey`.
+- **Statuses**: six, fixed for every project (`shared/statuses.ts`): `backlog` (nothing starts), `in_progress`,
+  `blocked` (waiting for a person), `in_review` (waiting to be accepted), `done` and `cancelled`. People move an issue
+  between any two of them; a principal of another kind only along its kind's `moves`, and only when its `mayMove`
+  agrees; the system only along a status event. Entering `blocked` or `in_review` tells the issue's owner, unless the
+  owner moved it (`owner_notified`). The moves go through `server/lifecycle` (below), compiled from the statuses, the
+  registered kinds' moves and the registered status events (`domains/statuses/`).
+- **Status events**: other plugins register status events through `projectsStatusEventsToken` (a dotted key such as
+  `acme.merged`, the statuses it moves an issue out of, `from`, and the status it moves it to, `to`) and fire one for a
+  batch of issues with `projects.statusEvents.fire({ event, issueIds, actor?, note?, details? }, tx?)`: each issue in
+  one of `from` moves to `to`, as the system, and the activity names `actor`. `projects.statusEvents.target(event,
+issueId)` says where firing it would take one issue without moving it (for a confirmation that says what an action
+  will do). The plugin never knows what an event means. In the browser, `StatusEventsContext` (`client/kit`) titles the
+  events for the timeline. The issues pages show the list and the board, the board by default.
+- **Starting an issue**: a new issue starts in `backlog` or `in_progress` (`START_STATUSES`; `backlog` when the request
+  names none, `DEFAULT_START_STATUS`), and the New issue form asks "Start now" or "Later". Created in `in_progress`, or
+  moved there, an issue's work starts.
 - **Projects**: a lead, members, visibility (`workspace` or `members`), status, dates and linked resources.
-- **Issues**: an owner, an executor (nobody, a member, or a principal of another registered kind), a status from the
-  project's workflow, priority, dates, a parent, labels and an activity history. Admins can soft-delete and restore.
+- **Issues**: an owner, an executor (nobody, a member, or a principal of another registered kind), a status,
+  priority, dates, a parent, labels and an activity history. Admins can soft-delete and restore.
 - **Sub-issues and dependencies**: a sub-issue may have a stage (0–1000); a later stage waits until every earlier
   stage of its siblings is finished (done or closed). An issue may be blocked by others; a link that would make issues
   wait for each other in a cycle is refused. When an issue finishes, the issues waiting only on it are released (their
   executor, or with nobody working on them their owner, is told), and the parent's owner is told when a stage or all
-  sub-issues are finished. A workflow may move the parent then: a transition with `on: 'subtasks.done'` and the
-  `system` actor. A status may also refuse issues whose sub-issues are open (`subtasksDone`) or that are blocked
-  (`blockersDone`). A project may have a setup issue (`Project.setupIssueId`, an issue created with
+  sub-issues are finished; the parent's own status does not move on its own. A project may have a setup issue (`Project.setupIssueId`, an issue created with
   `projectSetup: true` by someone who manages the project, one unfinished at a time): every issue created in the
   project after it, except its own sub-issues, is created blocked by it until it is finished. `IssueTriggers` (`onUnblocked`, `onBlocked`, `onSubtasksFinished`) let other plugins react, and
   `subtasks.visibleBlockers(viewer, issueIds)` tells another plugin's board what holds each issue now, in a fixed number
@@ -116,10 +91,10 @@ note?, details? }, tx?)`: each issue moves along its workflow's `on` transition,
   so an inbox can merge it.
 - **Batch reads for boards**: `issueQueries.matching(viewer, query, { executorType?, issueIds?, limit? })` answers, in
   a fixed number of reads, the viewer's issues within the list's filters that an executor of a kind works on (unless
-  finished) or that are among the ids given (whatever their status), with `truncated` past the limit;
-  `approvals.pendingOn(issueIds)` the pending approval requests on them, and `subscriptions.followedBy(conn, userId,
-issueIds)` those of them a person follows. An application's board of work joins its own records to issues with
+  finished) or that are among the ids given (whatever their status), with `truncated` past the limit, and
+  `subscriptions.followedBy(conn, userId, issueIds)` those of them a person follows. An application's board of work joins its own records to issues with
   them, without a query per issue.
+- **Hierarchy reads**: `issueQueries.hierarchy(viewer, query)` returns the complete independently authorized live issue scope, filtered matching IDs and internal dependency-wait facts before paging. It is an uncapped input for application-owned grouping, never a substitute for authorization. `hierarchyItems(viewer, ids)` hydrates at most 100 independently reauthorized rows with visible child/dependency counts; callers must replace raw parent IDs at unreadable boundaries. Applications own attention policy, grouping and continuation consistency. No new task statuses or persistence are required.
 - **Operation plans** (`shared/plans.ts`, `server/domains/plans/`): a short list of changes (create or update an
   issue, comment, add or remove a dependency, create a project; 1–50 rows, later rows may refer to what earlier ones
   create) that one person, the decider, reviews and executes as a whole. Creating, editing and retrying a plan
@@ -134,7 +109,7 @@ issueIds)` those of them a person follows. An application's board of work joins
   made through a plan, or by an agent for a person (`Actor.via = 'agent'` with its trace), show on the timeline as
   "via ‹Agent›" or "via ‹Agent›'s plan" (`Activity.via`). Other plugins use `projects.plans` (`PlanService`) and hear
   decisions through `projectsPlanHooksToken` (`PlanHooks.onPlanDecided`). A plan is visible to its decider and, for a
-  status rule's plan about an issue, to the issue's owner and editors.
+  status rule's plan about an issue (from earlier versions), to the issue's owner and editors.
 - **Intake with AI** (`shared/intake-ai.ts`, `server/domains/plans/intake/intake.ai.*`): as the old NocoProject, AI
   splits requirements into drafts ("AI split"), revises the drafts by one instruction ("Ask AI to revise", with the
   rows it added or changed highlighted and an undo), and breaks an issue down into sub-issue drafts ("AI breakdown" on
@@ -151,6 +126,10 @@ issueIds)` those of them a person follows. An application's board of work joins
 
 Everything is under `/api/projects` and needs a session (401 otherwise). Responses are `{ data }`, lists `{ data, meta }`; inputs are validated (400 `INVALID_INPUT`, domain `app`, with `fieldViolations`; JSON bodies are strict). Fixed segments come before `/{projectId}`.
 
+Invitation create/resend results include a shareable `inviteUrl` for an authorized original inviter using an unscoped person credential, regardless of email delivery. An invitation closed or rotated before its queued send returns `emailSent=false` without a link; other recipients, including existing accounts joining projects, still complete. Global user creation or role assignment permissions are not needed to copy a project invitation. `POST /api/projects/invitations/{invitationId}/resend?sendEmail=false` generates a new link without email, invalidating the old invitation. Member settings confirm this before generating a link, then offer a separate Copy action. Current project access is checked again; other managers can resend email but do not receive links, and scoped credentials remain email-only. Lists never expose tokens.
+
+New accounts register directly from the invitation link with a name and password; acceptance leaves `emailVerified=false`. Email delivery is optional: authorized original inviters can privately forward the link when the email channel is absent or fails. Links use `app.publicOrigin` when configured, otherwise the invitation request origin. Existing accounts must sign in with the invited email. Acceptance consumes only the supplied invitation and applies only its grants; handlers run in its transaction and roll back account creation on failure.
+
 | Method and path                                                                    | What it does                                                |
 | ---------------------------------------------------------------------------------- | ----------------------------------------------------------- |
 | `GET /me`                                                                          | The caller with their permissions                           |
@@ -159,15 +138,12 @@ Everything is under `/api/projects` and needs a session (401 otherwise). Respons
 | `GET/POST /invitations`, `POST …/{invitationId}/resend`, `DELETE …/{invitationId}` | Member invitations                                          |
 | `GET /settings`, `PATCH /settings`                                                 | Workspace settings                                          |
 | `GET/POST /labels`, `PATCH/DELETE /labels/{labelId}`                               | Labels                                                      |
-| `GET/POST /workflows`, `GET/PATCH/DELETE /workflows/{workflowId}`                  | Workflows; a new one is a copy (`copyFrom`)                 |
-| `POST /workflows/{workflowId}/preview`                                             | What saving a definition would change                       |
-| `POST /workflows/{workflowId}/setDefault`                                          | Makes a workflow the default                                |
 | `GET/POST /` , `GET/PATCH/DELETE /{projectId}`                                     | Projects                                                    |
 | `POST /{projectId}/members`, `DELETE …/members/{userId}`                           | Project members (201 the member added; 204)                 |
 | `POST /{projectId}/resources`, `PATCH/DELETE …/resources/{resourceId}`             | Project resources                                           |
 | `GET /issues?…&orderBy&pageSize&pageToken`                                         | A page of issues, cursor-paginated                          |
 | `GET /issues/board`                                                                | The board: a column per status, each a first page           |
-| `GET /issues/statuses`, `GET /issues/starts`                                       | A workflow's statuses; the ways to start an issue           |
+| `GET /issues/statuses`                                                             | The fixed statuses                                          |
 | `POST /issues`, `GET/PATCH/DELETE /issues/{issueId}`                               | Issues, by id or identifier (`PM-12`)                       |
 | `POST /issues/{issueId}/restore`                                                   | Restores a deleted issue                                    |
 | `GET /issues/{issueId}/activities?pageSize&pageToken`                              | Older activities                                            |
@@ -177,16 +153,13 @@ Everything is under `/api/projects` and needs a session (401 otherwise). Respons
 | `POST /comments/{commentId}/resolve`, `…/unresolve`                                | Resolves or reopens a thread (on its root)                  |
 | `POST /issues/{issueId}/subscribe`, `…/unsubscribe`                                | Follows or unfollows the issue                              |
 | `GET/POST /issues/{issueId}/attachments`                                           | The issue's own files; uploads one onto it                  |
+| `GET /issues/{issueId}/screenshots`                                                | Latest 100 live Agent comment images and comment provenance |
 | `POST /attachments`                                                                | Uploads one file, attached to nothing yet                   |
 | `GET /attachments/{attachmentId}`, `…/content`, `DELETE`                           | A file, its bytes (`?download=true`), removing it           |
-| `GET /issues/{issueId}/checklists`                                                 | Every checklist the issue has had                           |
-| `PATCH /issues/{issueId}/checklists/{statusKey}/items/{itemKey}`                   | Checks or unchecks an item (`{ checked }`)                  |
 | `POST /issues/{issueId}/dependencies`                                              | Adds a link (`{ dependsOnIssueId, type }`)                  |
+| `PATCH /issues/{issueId}/dependencies/{dependencyId}`                              | Changes a link type (`{ type, expectedType }`) atomically   |
 | `DELETE /issues/{issueId}/dependencies/{dependencyId}`                             | Removes a link                                              |
 | `POST /issues/{issueId}/removeDependency`                                          | Removes the link to an issue (`{ dependsOnIssueId, type }`) |
-| `GET /approvals`                                                                   | Status changes waiting for the caller's approval            |
-| `POST /approvals/{approvalId}/approve`, `…/reject`                                 | An approver decides (`{ comment? }`)                        |
-| `POST /approvals/{approvalId}/withdraw`                                            | Whoever asked withdraws the request                         |
 | `POST /plans/rehearse`                                                             | Rehearses a plan and stores nothing                         |
 | `GET/POST /plans`, `GET/PATCH /plans/{planId}`                                     | Operation plans: list, create, read, edit rows              |
 | `POST /plans/{planId}/execute`, `…/retry`, `…/void`                                | Decides a plan (`{ revision }`)                             |
@@ -196,36 +169,31 @@ Everything is under `/api/projects` and needs a session (401 otherwise). Respons
 | `GET /intake/aiAvailability`                                                       | Whether AI can be asked                                     |
 | `POST /intake/aiJobs`, `GET …/{jobId}`, `POST …/{jobId}/cancel`                    | A request to AI; cancelling it                              |
 
+Relationship conversion preserves the link ID and checks the type the caller read (`expectedType`). A stale change returns 409 `DEPENDENCY_CHANGED`; if the target relationship already exists, it returns 409 `DEPENDENCY_EXISTS` and keeps both links. A related link may be converted from either end: the current issue becomes the waiting issue when changed to `blockedBy`.
+
+Operations that add explicit or implicit waits (dependencies, conversions, issue creation, parent/stage changes and restores) share a dedicated database graph revision row. Its conditional increment protects cycle detection and writes until the outer transaction commits, across processes and projects. An outdated transaction snapshot returns 409 `DEPENDENCY_GRAPH_CHANGED`; reload and retry the whole operation. Every issue creation takes this protection before allocating its number, so plans that create issues and add dependencies use the same lock order. Standalone creates without dependencies lock the row without advancing the graph revision, so independent parallel creates still succeed without retrying each other. The revision is separate from settings/counters so MySQL reads of those rows after writing them cannot disguise an old graph snapshot. Restoring an issue is rejected if its waits would now create a cycle. Every relationship write, including both removal endpoints, acquires this protection before reading its type and endpoints, keeping duplicate checks, activity and release notifications consistent with conversions. Issue status and project changes, status events and deletion take the same guard before writing an issue, so concurrent changes cannot each see an old blocker and miss the last release. Automatic parent/stage completion keeps the originating guard; ordinary edits that cannot change waits do not acquire it. Plans acquire the guard without advancing its revision before their first row, including rehearsal and undo, so earlier issue edits cannot reverse the lock order of a later graph write.
+
 Cursor lists (issues, activities, comment threads, plans) take `pageSize` (20 by default, at most 100; plans 50) and `pageToken`, and answer `meta.nextPageToken` until the last page. `orderBy` on issues is `updatedAt`, `createdAt`, `number` or `priority`, optionally followed by `asc` or `desc` (`updatedAt desc` by default). The other lists are answered whole with `meta.total`. A scoped API key may not use `/intake` or `/plans` (403 `SCOPED_KEY_FORBIDDEN`).
 
-Errors are the standard error body with domain `projects`; clients branch on `reason`, and `metadata` carries the details. A missing resource the URL names is 404 `<RESOURCE>_NOT_FOUND` (such as `ISSUE_NOT_FOUND`); a project or issue named in the query that does not exist is 400 with a field violation. `PATCH /issues/{issueId}` and `PATCH /workflows/{workflowId}` need the `revision` the caller read; a stale one is 409 `ABORTED` `REVISION_CONFLICT`. An invalid workflow is 400 `INVALID_WORKFLOW` with every problem in `metadata.issues` (`{ path: 'states[3].key', message }`). A change that would leave an issue in a status its workflow no longer has (editing a workflow, switching a project's, choosing another default) is 400 `FAILED_PRECONDITION` `WORKFLOW_STATUS_CONFLICT` with the count per status and project in `metadata.conflicts`. `PATCH /issues/{issueId}` answers `{ data: { issue, pendingApproval } }`: 200 with `pendingApproval: null` once applied, or 202 with the request when the status change waits for approval, applying nothing else of the request; another request for the same issue is 400 `APPROVAL_PENDING`. A dependency that would close a cycle is 400 `DEPENDENCY_CYCLE` (`metadata.via`), one too deep to check 400 `DEPENDENCY_TOO_DEEP`, a duplicate 409 `ALREADY_EXISTS` `DEPENDENCY_EXISTS`; entering a status that waits for sub-issues or blockers is 400 `FAILED_PRECONDITION` `SUBTASKS_OPEN` or `ISSUE_BLOCKED`. A plan with a failing row is 400 `PLAN_INVALID` with every row's check in `metadata.rows`; deciding a plan that is not open is 400 `PLAN_NOT_OPEN`, an expired one 400 `PLAN_EXPIRED`; undoing after the window is 400 `UNDO_EXPIRED`, with nothing left to revert 400 `NOTHING_TO_UNDO`, and when something changed since the preview 409 `ABORTED` `UNDO_STALE`. Other refusals by state are 400 `FAILED_PRECONDITION` too.
+Errors are the standard error body with domain `projects`; clients branch on `reason`, and `metadata` carries the details. A missing resource the URL names is 404 `<RESOURCE>_NOT_FOUND` (such as `ISSUE_NOT_FOUND`); a project or issue named in the query that does not exist is 400 with a field violation. `PATCH /issues/{issueId}` needs the `revision` the caller read; a stale one is 409 `ABORTED` `REVISION_CONFLICT`. It answers 200 `{ data: { issue } }`. A status that does not exist, or a new issue in any status but `backlog` and `in_progress`, is 400 `INVALID_STATUS`; a move the caller's kind may not make is 400 `TRANSITION_NOT_ALLOWED`. A dependency that would close a cycle is 400 `DEPENDENCY_CYCLE` (`metadata.via`), one too deep to check 400 `DEPENDENCY_TOO_DEEP`, a duplicate 409 `ALREADY_EXISTS` `DEPENDENCY_EXISTS`. A plan with a failing row is 400 `PLAN_INVALID` with every row's check in `metadata.rows`; deciding a plan that is not open is 400 `PLAN_NOT_OPEN`, an expired one 400 `PLAN_EXPIRED`; undoing after the window is 400 `UNDO_EXPIRED`, with nothing left to revert 400 `NOTHING_TO_UNDO`, and when something changed since the preview 409 `ABORTED` `UNDO_STALE`. Other refusals by state are 400 `FAILED_PRECONDITION` too.
 
-## Workflows and the lifecycle module
+## Statuses and the lifecycle module
 
 `server/lifecycle/` is a self-contained state machine for records, with no import from the domains, so it can become
 a platform package: a definition as data (states with a category, transitions `from → to` naming who may take them,
-`*` for any state, and event transitions `on` an event the definition lists, which only `fire` takes), `validateDefinition` (paths for every problem, plus rules the application passes in), `compile`
-(the questions the application asks) and `move`, the one path through which a state changes. It runs in the
-caller's unit of work, in order: who may (the actor on the transition, and a registered "who may" rule over the record),
-the guards of the state left and the state entered, an approval when a transition needs one, the caller's write, and
-the entry actions, each in its own savepoint. Rules are registered by name (`createLifecycleRegistry`: state rules,
-"who may" rules, approvers); a definition names them with their settings, and validation checks both.
-`server/domains/workflows/` stores the definitions and adds this plugin's rules: `workflow.rules.ts` (the built-in
-statuses, each transition within what its kinds allow, people able to leave every status, one rule of a kind per
-status) and
-`workflow.registry.ts` (every status rule type, built in or contributed, as a lifecycle state rule, and the approvers
-`owner`, `projectLead`, `admin`). When several transitions match a move (`* → *` and `in_review → done`), the move
-takes them all, and needs an approval when any of them does; a move on an event never waits for one.
-`server/domains/approvals/` keeps the requests; a request has its own lifecycle in code (pending → approved, rejected,
-withdrawn or stale, each decision a transition with a "who may" rule). Approving moves the issue as the requester's
-move, checked again; when it no longer passes, the request goes stale. Notices (`server/providers/notifications.ts`:
-the owner told, approvers asked to decide, the requester told the outcome) go to `projectsNoticesToken` when the App
-binds it (`ProjectsNotices`: `send` each notice with its kind, type, issue and approval request; `resolve` a decision
-once its request is decided) — the assembling application keeps its inbox that way. A request another kind (an agent) made tells the
-issue's owner its outcome instead of the requester; an approved request that no longer applies (its conditions failed
-when it was approved) tells the approvers and whoever asked, except the approver (`approval_stale`). The issue page lists
-the last five decided requests (`IssueDetail.recentApprovals`). Without it they go straight to the notification
-plugin's in-app channel `projects.inboxChannel` names (`inbox` by default) when that channel is configured.
+`*` for any state, and event transitions `on` an event, which only `fire` takes), `validateDefinition`, `compile` (the
+questions the application asks) and `move`, the one path through which a state changes. It runs in the caller's unit
+of work, in order: who may (the actor on the transition, and a registered "who may" rule over the record), the guards
+of the state left and the state entered, the caller's write, and the entry actions, each in its own savepoint. Rules
+are registered by name (`createLifecycleRegistry`).
+
+`server/domains/statuses/` compiles the fixed statuses into such a definition: people `* → *`, each registered kind's
+`moves` (behind a "who may" rule asking the kind's `mayMove`), and each status event's transitions for the system; the
+definition is compiled again whenever the kinds or events change. The entry action `notifyOwner` on `blocked` and
+`in_review` records `owner_notified` and announces it. Notices (`server/providers/notifications.ts`) go to
+`projectsNoticesToken` when the App binds it (`ProjectsNotices`: `send` each notice with its kind, type and issue) —
+the assembling application keeps its inbox that way. Without it they go straight to the notification plugin's in-app
+channel `projects.inboxChannel` names (`inbox` by default) when that channel is configured.
 
 ## Permissions
 
@@ -237,7 +205,7 @@ What can be granted (`shared/access.ts`); the application stores and assigns the
 | Business actions | `pm.issues`                                | `view`, `create`, `edit`, `comment`, `moderate-comments`, |
 |                  |                                            | `close`, `change-owner`, `delete`                         |
 | Business actions | `pm.attachments`                           | `upload`                                                  |
-| Settings items   | `pm.general`, `pm.labels`, `pm.workflows`  | `read`, `update`                                          |
+| Settings items   | `pm.general`, `pm.labels`                  | `read`, `update`                                          |
 | Settings items   | `pm.members`                               | `read`, `invite`, `assign`, `define-roles`                |
 | Pages            | `pm-my-issues`, `pm-issues`, `pm-projects` | `access`                                                  |
 
@@ -257,43 +225,38 @@ The plugin seeds no roles: the application that assembles it seeds its own (the
 
 | Path                                  | What it shows                                               |
 | ------------------------------------- | ----------------------------------------------------------- |
-| `/my-issues/owned`, `executing`       | The viewer's issues, as owner or executor                   |
+| `/my-issues`                          | The viewer's owned or executed issues, each once            |
 | `/issues` (`?view=board` or `list`)   | Every visible issue; filters, search and order in the URL   |
 | `/issues/new` (`?tab=ai` or `manual`) | The New issue dialog: AI draft (intake) or one issue        |
 | `/issues/new?tab=ai&job=:id`          | The AI draft tab following a request to AI                  |
 | `/issues/:id`, `/issues/plans/:id`    | One issue, by id or identifier; one plan, by its id         |
 | `/projects`, `/projects/new`          | Projects; a new one (a project's page is the application's) |
 
-As the old NocoProject had it, My issues has "I own" and "I execute" only, and the New issue dialog opens on its "AI
-draft" tab (the last tab used is remembered in the browser): requirements typed or uploaded are split into a draft of
-issues, edited row by row and created together, after which the dialog closes. Its manual tab offers the workflow's ways
-to start an issue as its process. A change that would start an executor of another kind working asks "Start now?"
-first, as the old NocoProject asked: giving an agent the issue (on creation, a sub-issue, or in the properties) or
-moving an issue it executes out of backlog (a status change or a board drag). Nothing starts in backlog or a finished
-status, so a change landing there asks nothing. Approvals are decided on the issue
-page and wherever the application sends their notices (for example, its inbox).
+My tasks combines owned and executed issues, and the New issue dialog opens on its "AI draft" tab (the last tab used is remembered in the browser): requirements typed or uploaded are split into a draft of issues, edited row by row and created together, after which the dialog closes. Its manual tab asks when the issue starts: "Start now" (`in_progress`) or "Later" (`backlog`), and preselects the default executor. Nothing asks "Start now?" any more: moving an issue to `in_progress` starts its work.
+
+Applications that create tasks through conversation can render the retained create and subtask pages under `IssueCreationModeContext.Provider` (from `client/kit`) with `value='manual'`. This shows only the original guarded form, ignoring old AI tab parameters and preferences, without changing the default plugin pages.
 
 The settings pages are exported for the application to route under its own `/config` (`client/config.ts`: the issue
-prefix, labels, workflows and one workflow), and components it reuses on its member pages are exported from
+prefix and labels), and components it reuses on its member pages are exported from
 `client/kit.ts`. The application routes an issue's page itself and presents it (for example, with the UI Library's
 `issue-detail`, `comment-thread` and `attachment-list`) over the headless parts in `client/issues.ts`: the issue
-(`useIssueDetail`), its property changes (`useIssueUpdate`, and `useConfirmedUpdate` for "Start now?"), every other
+(`useIssueDetail`), its property changes (`useIssueUpdate`; `useConfirmedUpdate` applies a change at once), every other
 change of the page (`useIssuePageActions`), the activity line (`useIssueTimeline`, `useIssueCommentActions`,
 `useMentionSearch`, `useAttachmentUploads`), "Break into sub-issues" (`useIntakeBreakdown`), and the permission and
 wording helpers. It routes a project's page the same way, as a child of the plugin's `/projects` (`projectsRoute` from
-`client/pages`), over the headless parts in `client/projects.ts`: the project with its statuses and workflow
-(`useProjectDetail`, `useProjectStatuses`, `useProjectWorkflow`), its property changes (`useProjectUpdate`), members and
+`client/pages`), over the headless parts in `client/projects.ts`: the project with the statuses
+(`useProjectDetail`, `useProjectStatuses`), its property changes (`useProjectUpdate`), members and
 visibility (`useProjectMembership`), working directories (`useProjectResources`, `useResourceValidation`), deleting it
 (`useDeleteProject`), and the progress, numbers and permission helpers. The pages are behind the `pm-my-issues`, `pm-issues` and `pm-projects` page grants. They hide
 what the server would refuse (`client/lib/permissions.ts` mirrors its rules); the server still checks every request.
-Open pages refresh when the server announces a change on the `pm:changes` realtime topic.
+Open pages refresh when the server announces a change on the `pm:changes` realtime topic: once for the events of a moment, naming the issues that changed when no change moved an issue between lists (`issueIds`), so a page refreshes only what it shows of them (`announcedIssueIds`, `changedIssueSegments` and `isIssueRead` in `client/kit`).
 
 ## Layout
 
 - `shared/`: types and constants the server and the client share.
 - `server/kernel/`: infrastructure with no business rules (errors, events, transactions, pagination, validation).
 - `server/access/`: how a request becomes a `Viewer` with resolved permissions.
-- `server/lifecycle/`: the record state machine behind workflows (see above).
+- `server/lifecycle/`: the record state machine behind the statuses (see above).
 - `server/domains/<name>/`: one folder per domain: `*.store.ts` (tables), `*.access.ts` (who sees what),
   `*.service.ts` (writes), `*.routes.ts` (HTTP), `index.ts` (the domain's public surface).
 - `server/composition.ts`: wires the domains; `server/providers/` registers them with the app.
@@ -308,3 +271,17 @@ Open pages refresh when the server announces a change on the `pm:changes` realti
 ```bash
 pnpm --filter @nocobase/app-plugin-projects check
 ```
+
+When renewing an invitation, deleted projects are ignored if at least one selected project remains. The inviter must still be authorized to invite into every remaining project. If all originally selected projects were deleted, renewal is rejected.
+
+Invitation emails use `notificationService.sendTransient()` so credentials never enter notification message snapshots or job storage. This performs one bounded attempt without durable retries or deduplication. Failures retain safe status/category diagnostics without raw provider messages. The inviter can generate and privately deliver a new link if delivery fails. Historical notification snapshots are not rewritten.
+
+## Structured issue progress
+
+`Issue` exposes nullable text `needsYou` and `next`. `PATCH /api/projects/issues/{issueId}` and `issue.update` plan rows accept them in the same transaction as `statusKey`. Both fields are optional for people, agents, plans and system events. Omitted needsYou is retained in Blocked or In review; null, empty or whitespace clears it. Applications may constrain authenticated callers at their request boundary. Leaving these states clears it. Omitted `next` is retained; nonblank text replaces it; null, an empty string or whitespace clears it. Done and Cancelled always clear it. Both fields allow at most 2,000 characters. Progress-only writes advance revision and emit the existing refresh event. System status events share the optional-field validation and clearing rules. The new reversible migration adds the two columns without backfilling comments.
+
+`Issue` also exposes nullable Markdown `acceptance`: the issue's delivery report — how it was, the agreed approach, what changed, how it was checked, open issues and details — ending with the acceptance criteria the owner checks and where. `PATCH /api/projects/issues/{issueId}` accepts it in any status, normally with the move to In review (`nb-studio issue update <issue> --status in_review --acceptance-file report.md`). It is kept across status changes, including Done, Cancelled and a move back to In progress, and the next delivery replaces it; omitted it is retained, and null, an empty string or whitespace clears it. It allows at most 20,000 characters (`ISSUE_ACCEPTANCE_MAX`). Its reversible migration adds the column without backfilling.
+
+Manual issue descriptions accept pasted images through the existing protected attachment upload. Creation accepts optional `attachmentIds` of the caller's own unattached uploads and requires `pm.attachments` `upload` in addition to issue creation permission. Files are bound in the creation transaction before work starts, so the first agent context includes them. Descriptions remain Markdown; image nodes survive detail edits. Uploading blocks submission; cancelling leaves unattached files to the existing purge.
+
+Applications can provide `ExecutorPresentationContext` from the client kit to render the identity and availability of their registered executor kind in new issue and subtask selectors. It changes presentation only; the server still supplies candidates and enforces qualifications.

package/dist/client/api/changed-issues.d.ts

@@ -0,0 +1,12 @@
+/**
+ * Which cached issue reads an announcement (`PmChangeEvent.issueIds`) concerns: an issue's reads are keyed by
+ * `pmKeys.issue(idOrKey)` and what sits under it, with the id or, on a page opened by its key, the identifier.
+ */
+import type { QueryClient, QueryKey } from '@tanstack/react-query';
+/** The issue ids an announcement names, or null when any issue may have changed. */
+export declare function announcedIssueIds(payload: unknown): ReadonlySet<string> | null;
+/** The key segments (`pmKeys.issue(segment)`) whose reads are of one of `issueIds`: the ids, and the keys loaded for them. */
+export declare function changedIssueSegments(client: Pick<QueryClient, 'getQueryCache'>, issueIds: ReadonlySet<string>): Set<string>;
+/** Whether a query key is one issue's read (`['pm', 'issue', segment, ...]`) of a segment among `segments`. */
+export declare function isIssueRead(key: QueryKey, segments: ReadonlySet<string>): boolean;
+//# sourceMappingURL=changed-issues.d.ts.map

package/dist/client/api/changed-issues.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"changed-issues.d.ts","sourceRoot":"","sources":["../../../client/api/changed-issues.ts"],"names":[],"mappings":"AAAA;;;GAGG;AACH,OAAO,KAAK,EAAE,WAAW,EAAE,QAAQ,EAAE,MAAM,uBAAuB,CAAC;AAInE,oFAAoF;AACpF,wBAAgB,iBAAiB,CAC/B,OAAO,EAAE,OAAO,GACf,WAAW,CAAC,MAAM,CAAC,GAAG,IAAI,CAK5B;AAED,8HAA8H;AAC9H,wBAAgB,oBAAoB,CAClC,MAAM,EAAE,IAAI,CAAC,WAAW,EAAE,eAAe,CAAC,EAC1C,QAAQ,EAAE,WAAW,CAAC,MAAM,CAAC,GAC5B,GAAG,CAAC,MAAM,CAAC,CAeb;AAED,+GAA+G;AAC/G,wBAAgB,WAAW,CACzB,GAAG,EAAE,QAAQ,EACb,QAAQ,EAAE,WAAW,CAAC,MAAM,CAAC,GAC5B,OAAO,CAOT"}

package/dist/client/api/changed-issues.js

@@ -0,0 +1,30 @@
+/** The issue ids an announcement names, or null when any issue may have changed. */
+export function announcedIssueIds(payload) {
+    const ids = payload?.issueIds;
+    return Array.isArray(ids) && ids.every((id) => typeof id === 'string')
+        ? new Set(ids)
+        : null;
+}
+/** The key segments (`pmKeys.issue(segment)`) whose reads are of one of `issueIds`: the ids, and the keys loaded for them. */
+export function changedIssueSegments(client, issueIds) {
+    const segments = new Set(issueIds);
+    for (const query of client
+        .getQueryCache()
+        .findAll({ queryKey: ['pm', 'issue'] })) {
+        const segment = query.queryKey[2];
+        const id = query.state.data?.id;
+        if (typeof segment === 'string' &&
+            typeof id === 'string' &&
+            issueIds.has(id))
+            segments.add(segment);
+    }
+    return segments;
+}
+/** Whether a query key is one issue's read (`['pm', 'issue', segment, ...]`) of a segment among `segments`. */
+export function isIssueRead(key, segments) {
+    return (key[0] === 'pm' &&
+        key[1] === 'issue' &&
+        typeof key[2] === 'string' &&
+        segments.has(key[2]));
+}
+//# sourceMappingURL=changed-issues.js.map

package/dist/client/api/changed-issues.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"changed-issues.js","sourceRoot":"","sources":["../../../client/api/changed-issues.ts"],"names":[],"mappings":"AAQA,oFAAoF;AACpF,MAAM,UAAU,iBAAiB,CAC/B,OAAgB;IAEhB,MAAM,GAAG,GAAI,OAAyC,EAAE,QAAQ,CAAC;IACjE,OAAO,KAAK,CAAC,OAAO,CAAC,GAAG,CAAC,IAAI,GAAG,CAAC,KAAK,CAAC,CAAC,EAAE,EAAE,EAAE,CAAC,OAAO,EAAE,KAAK,QAAQ,CAAC;QACpE,CAAC,CAAC,IAAI,GAAG,CAAC,GAAG,CAAC;QACd,CAAC,CAAC,IAAI,CAAC;AACX,CAAC;AAED,8HAA8H;AAC9H,MAAM,UAAU,oBAAoB,CAClC,MAA0C,EAC1C,QAA6B;IAE7B,MAAM,QAAQ,GAAG,IAAI,GAAG,CAAC,QAAQ,CAAC,CAAC;IACnC,KAAK,MAAM,KAAK,IAAI,MAAM;SACvB,aAAa,EAAE;SACf,OAAO,CAAC,EAAE,QAAQ,EAAE,CAAC,IAAI,EAAE,OAAO,CAAC,EAAE,CAAC,EAAE,CAAC;QAC1C,MAAM,OAAO,GAAG,KAAK,CAAC,QAAQ,CAAC,CAAC,CAAC,CAAC;QAClC,MAAM,EAAE,GAAI,KAAK,CAAC,KAAK,CAAC,IAAqC,EAAE,EAAE,CAAC;QAClE,IACE,OAAO,OAAO,KAAK,QAAQ;YAC3B,OAAO,EAAE,KAAK,QAAQ;YACtB,QAAQ,CAAC,GAAG,CAAC,EAAE,CAAC;YAEhB,QAAQ,CAAC,GAAG,CAAC,OAAO,CAAC,CAAC;IAC1B,CAAC;IACD,OAAO,QAAQ,CAAC;AAClB,CAAC;AAED,+GAA+G;AAC/G,MAAM,UAAU,WAAW,CACzB,GAAa,EACb,QAA6B;IAE7B,OAAO,CACL,GAAG,CAAC,CAAC,CAAC,KAAK,IAAI;QACf,GAAG,CAAC,CAAC,CAAC,KAAK,OAAO;QAClB,OAAO,GAAG,CAAC,CAAC,CAAC,KAAK,QAAQ;QAC1B,QAAQ,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CACrB,CAAC;AACJ,CAAC"}

package/dist/client/api/client.d.ts

@@ -5,21 +5,18 @@
  */
 import type { ApiClient } from '@nocobase/app-client';
 import type { Page } from '../../shared/common.js';
-import type { ApprovalRequest } from '../../shared/approvals.js';
 import type { Attachment } from '../../shared/attachments.js';
-import type { IssueChecklist, UpdateChecklistItemRequest } from '../../shared/checklists.js';
 import { type CommentReaction, type CreateCommentRequest, type CreateCommentResult, type IssueComment, type MentionCandidate, type ThreadPage, type ThreadResolution } from '../../shared/comments.js';
 import type { CreateInvitationsRequest, Invitation, InvitationResult } from '../../shared/invitations.js';
-import { type ActivityPage, type CreateIssueRequest, type Issue, type IssueBoard, type IssueStarts, type IssueDetail, type IssueListItem, type IssueListQuery, type StatusDefinition, type UpdateIssueRequest, type UpdateIssueResult } from '../../shared/issues.js';
+import { type ActivityPage, type CreateIssueRequest, type Issue, type IssueBoard, type IssueDetail, type IssueListItem, type IssueListQuery, type StatusDefinition, type UpdateIssueRequest, type UpdateIssueResult } from '../../shared/issues.js';
 import type { CreateLabelRequest, Label, UpdateLabelRequest } from '../../shared/labels.js';
 import type { ExecutorCandidate } from '../../shared/kinds.js';
 import type { ApiKeyActor, Me, Member } from '../../shared/members.js';
 import type { CreateProjectRequest, CreateProjectResourceRequest, ProjectDetail, ProjectListItem, ProjectResource, UpdateProjectRequest, UpdateProjectResourceRequest } from '../../shared/projects.js';
 import type { UpdateSettingsRequest, WorkspaceSettings } from '../../shared/settings.js';
-import type { AddDependencyRequest, IssueDependency } from '../../shared/subtasks.js';
+import type { AddDependencyRequest, IssueDependency, UpdateDependencyRequest } from '../../shared/subtasks.js';
 import type { UserRef } from '../../shared/common.js';
 import type { SubscriptionState } from '../../shared/subscriptions.js';
-import type { CreateWorkflowRequest, UpdateWorkflowRequest, WorkflowDefinition, WorkflowListItem, WorkflowPreview } from '../../shared/workflows.js';
 export declare class PmApi {
     private readonly api;
     constructor(api: ApiClient);
@@ -31,7 +28,7 @@ export declare class PmApi {
     executors(): Promise<ExecutorCandidate[]>;
     invitations(): Promise<Invitation[]>;
     invite(input: CreateInvitationsRequest): Promise<readonly InvitationResult[]>;
-    resendInvitation(invitationId: string): Promise<InvitationResult>;
+    resendInvitation(invitationId: string, sendEmail?: boolean): Promise<InvitationResult>;
     revokeInvitation(invitationId: string): Promise<void>;
     settings(): Promise<WorkspaceSettings>;
     updateSettings(input: UpdateSettingsRequest): Promise<WorkspaceSettings>;
@@ -39,14 +36,6 @@ export declare class PmApi {
     createLabel(input: CreateLabelRequest): Promise<Label>;
     updateLabel(labelId: string, input: UpdateLabelRequest): Promise<Label>;
     deleteLabel(labelId: string): Promise<void>;
-    workflows(): Promise<WorkflowListItem[]>;
-    workflow(workflowId: string): Promise<WorkflowListItem>;
-    createWorkflow(input: CreateWorkflowRequest): Promise<WorkflowListItem>;
-    updateWorkflow(workflowId: string, input: UpdateWorkflowRequest): Promise<WorkflowListItem>;
-    /** What saving `definition` would change in the workflow's rules; nothing is written. */
-    previewWorkflow(workflowId: string, definition: WorkflowDefinition): Promise<WorkflowPreview>;
-    setDefaultWorkflow(workflowId: string): Promise<WorkflowListItem>;
-    deleteWorkflow(workflowId: string): Promise<void>;
     projects(): Promise<ProjectListItem[]>;
     project(projectId: string): Promise<ProjectDetail>;
     createProject(input: CreateProjectRequest): Promise<ProjectDetail>;
@@ -58,10 +47,8 @@ export declare class PmApi {
     addProjectResource(projectId: string, input: CreateProjectResourceRequest): Promise<ProjectResource>;
     updateProjectResource(projectId: string, resourceId: string, input: UpdateProjectResourceRequest): Promise<ProjectResource>;
     deleteProjectResource(projectId: string, resourceId: string): Promise<void>;
-    /** The statuses of a project's workflow; without a project, those of issues without one. */
-    statuses(projectId?: string | null): Promise<StatusDefinition[]>;
-    /** The ways a new issue may start in a project's workflow; without a project, in that of issues without one. */
-    starts(projectId?: string | null): Promise<IssueStarts>;
+    /** The fixed statuses, in order. */
+    statuses(): Promise<StatusDefinition[]>;
     issuePage(query: IssueListQuery): Promise<Page<IssueListItem>>;
     /** A column per status, each with its first `ISSUE_PAGE_LIMIT.default` issues. */
     board(query: IssueListQuery): Promise<IssueBoard>;
@@ -69,21 +56,17 @@ export declare class PmApi {
     issue(idOrKey: string): Promise<IssueDetail>;
     activities(issueId: string, cursor?: string): Promise<ActivityPage>;
     createIssue(input: CreateIssueRequest): Promise<Issue>;
-    /** The issue after the change; with `pendingApproval`, unchanged because the status change waits for approval. */
+    /** The issue after the change. */
     updateIssue(issueId: string, input: UpdateIssueRequest): Promise<UpdateIssueResult>;
     deleteIssue(issueId: string): Promise<void>;
     restoreIssue(issueId: string): Promise<Issue>;
-    /** The status changes waiting for the caller's approval. */
-    approvals(): Promise<ApprovalRequest[]>;
-    decideApproval(requestId: string, decision: 'approve' | 'reject', comment?: string): Promise<ApprovalRequest>;
-    withdrawApproval(requestId: string): Promise<ApprovalRequest>;
     /** Makes the issue wait for (`blockedBy`, the default) or link to (`relatedTo`) another; answers the link. */
     addDependency(issueId: string, input: AddDependencyRequest): Promise<IssueDependency>;
+    /** Converts a relationship atomically, keeping its id and checking the type the caller read. */
+    updateDependency(issueId: string, dependencyId: string, input: UpdateDependencyRequest): Promise<IssueDependency>;
     /** Removes the link to `dependsOnIssueId` of `type` (`blockedBy` when left out). */
     removeDependencyTo(issueId: string, input: AddDependencyRequest): Promise<void>;
     removeDependency(issueId: string, dependencyId: string): Promise<void>;
-    /** Checks or unchecks one item of the issue's checklist of `statusKey`; answers that checklist. */
-    setChecklistItem(issueId: string, statusKey: string, itemKey: string, input: UpdateChecklistItemRequest): Promise<IssueChecklist>;
     /** Threads older than `cursor` (the detail brings the newest page and its cursor). */
     threads(issueId: string, cursor?: string): Promise<ThreadPage>;
     createComment(issueId: string, input: CreateCommentRequest): Promise<CreateCommentResult>;

package/dist/client/api/client.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"client.d.ts","sourceRoot":"","sources":["../../../client/api/client.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AACH,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,sBAAsB,CAAC;AAEtD,OAAO,KAAK,EAAE,IAAI,EAAE,MAAM,wBAAwB,CAAC;AACnD,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,2BAA2B,CAAC;AACjE,OAAO,KAAK,EAAE,UAAU,EAAE,MAAM,6BAA6B,CAAC;AAC9D,OAAO,KAAK,EACV,cAAc,EACd,0BAA0B,EAC3B,MAAM,4BAA4B,CAAC;AACpC,OAAO,EAEL,KAAK,eAAe,EAEpB,KAAK,oBAAoB,EACzB,KAAK,mBAAmB,EACxB,KAAK,YAAY,EACjB,KAAK,gBAAgB,EACrB,KAAK,UAAU,EACf,KAAK,gBAAgB,EACtB,MAAM,0BAA0B,CAAC;AAClC,OAAO,KAAK,EACV,wBAAwB,EACxB,UAAU,EACV,gBAAgB,EACjB,MAAM,6BAA6B,CAAC;AACrC,OAAO,EAGL,KAAK,YAAY,EACjB,KAAK,kBAAkB,EACvB,KAAK,KAAK,EACV,KAAK,UAAU,EACf,KAAK,WAAW,EAChB,KAAK,WAAW,EAChB,KAAK,aAAa,EAClB,KAAK,cAAc,EAEnB,KAAK,gBAAgB,EACrB,KAAK,kBAAkB,EACvB,KAAK,iBAAiB,EACvB,MAAM,wBAAwB,CAAC;AAChC,OAAO,KAAK,EACV,kBAAkB,EAClB,KAAK,EACL,kBAAkB,EACnB,MAAM,wBAAwB,CAAC;AAChC,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,uBAAuB,CAAC;AAC/D,OAAO,KAAK,EAAE,WAAW,EAAE,EAAE,EAAE,MAAM,EAAE,MAAM,yBAAyB,CAAC;AACvE,OAAO,KAAK,EACV,oBAAoB,EACpB,4BAA4B,EAC5B,aAAa,EACb,eAAe,EACf,eAAe,EACf,oBAAoB,EACpB,4BAA4B,EAC7B,MAAM,0BAA0B,CAAC;AAClC,OAAO,KAAK,EACV,qBAAqB,EACrB,iBAAiB,EAClB,MAAM,0BAA0B,CAAC;AAClC,OAAO,KAAK,EACV,oBAAoB,EACpB,eAAe,EAChB,MAAM,0BAA0B,CAAC;AAClC,OAAO,KAAK,EAAE,OAAO,EAAE,MAAM,wBAAwB,CAAC;AACtD,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,+BAA+B,CAAC;AACvE,OAAO,KAAK,EACV,qBAAqB,EACrB,qBAAqB,EACrB,kBAAkB,EAClB,gBAAgB,EAChB,eAAe,EAChB,MAAM,2BAA2B,CAAC;AAwCnC,qBAAa,KAAK;IACG,OAAO,CAAC,QAAQ,CAAC,GAAG;gBAAH,GAAG,EAAE,SAAS;IAI3C,EAAE,IAAI,OAAO,CAAC,EAAE,CAAC;IAIjB,OAAO,IAAI,OAAO,CAAC,MAAM,EAAE,CAAC;IAInC,6FAA6F;IACtF,YAAY,IAAI,OAAO,CAAC,WAAW,EAAE,CAAC;IAI7C,kFAAkF;IAC3E,SAAS,IAAI,OAAO,CAAC,iBAAiB,EAAE,CAAC;IAIzC,WAAW,IAAI,OAAO,CAAC,UAAU,EAAE,CAAC;IAI9B,MAAM,CACjB,KAAK,EAAE,wBAAwB,GAC9B,OAAO,CAAC,SAAS,gBAAgB,EAAE,CAAC;IAOhC,gBAAgB,CAAC,YAAY,EAAE,MAAM,GAAG,OAAO,CAAC,gBAAgB,CAAC;IAIjE,gBAAgB,CAAC,YAAY,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC;IAMrD,QAAQ,IAAI,OAAO,CAAC,iBAAiB,CAAC;IAItC,cAAc,CACnB,KAAK,EAAE,qBAAqB,GAC3B,OAAO,CAAC,iBAAiB,CAAC;IAItB,MAAM,IAAI,OAAO,CAAC,KAAK,EAAE,CAAC;IAI1B,WAAW,CAAC,KAAK,EAAE,kBAAkB,GAAG,OAAO,CAAC,KAAK,CAAC;IAItD,WAAW,CAChB,OAAO,EAAE,MAAM,EACf,KAAK,EAAE,kBAAkB,GACxB,OAAO,CAAC,KAAK,CAAC;IAIV,WAAW,CAAC,OAAO,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC;IAM3C,SAAS,IAAI,OAAO,CAAC,gBAAgB,EAAE,CAAC;IAIxC,QAAQ,CAAC,UAAU,EAAE,MAAM,GAAG,OAAO,CAAC,gBAAgB,CAAC;IAIvD,cAAc,CACnB,KAAK,EAAE,qBAAqB,GAC3B,OAAO,CAAC,gBAAgB,CAAC;IAIrB,cAAc,CACnB,UAAU,EAAE,MAAM,EAClB,KAAK,EAAE,qBAAqB,GAC3B,OAAO,CAAC,gBAAgB,CAAC;IAI5B,yFAAyF;IAClF,eAAe,CACpB,UAAU,EAAE,MAAM,EAClB,UAAU,EAAE,kBAAkB,GAC7B,OAAO,CAAC,eAAe,CAAC;IAMpB,kBAAkB,CAAC,UAAU,EAAE,MAAM,GAAG,OAAO,CAAC,gBAAgB,CAAC;IAIjE,cAAc,CAAC,UAAU,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC;IAMjD,QAAQ,IAAI,OAAO,CAAC,eAAe,EAAE,CAAC;IAItC,OAAO,CAAC,SAAS,EAAE,MAAM,GAAG,OAAO,CAAC,aAAa,CAAC;IAIlD,aAAa,CAAC,KAAK,EAAE,oBAAoB,GAAG,OAAO,CAAC,aAAa,CAAC;IAIlE,aAAa,CAClB,SAAS,EAAE,MAAM,EACjB,KAAK,EAAE,oBAAoB,GAC1B,OAAO,CAAC,aAAa,CAAC;IAIlB,aAAa,CAAC,SAAS,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC;IAItD,gCAAgC;IACzB,gBAAgB,CAAC,SAAS,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM,GAAG,OAAO,CAAC,OAAO,CAAC;IAMrE,mBAAmB,CAAC,SAAS,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC;IAOrE,kBAAkB,CACvB,SAAS,EAAE,MAAM,EACjB,KAAK,EAAE,4BAA4B,GAClC,OAAO,CAAC,eAAe,CAAC;IAIpB,qBAAqB,CAC1B,SAAS,EAAE,MAAM,EACjB,UAAU,EAAE,MAAM,EAClB,KAAK,EAAE,4BAA4B,GAClC,OAAO,CAAC,eAAe,CAAC;IAQpB,qBAAqB,CAC1B,SAAS,EAAE,MAAM,EACjB,UAAU,EAAE,MAAM,GACjB,OAAO,CAAC,IAAI,CAAC;IAShB,4FAA4F;IACrF,QAAQ,CAAC,SAAS,CAAC,EAAE,MAAM,GAAG,IAAI,GAAG,OAAO,CAAC,gBAAgB,EAAE,CAAC;IAIvE,gHAAgH;IACzG,MAAM,CAAC,SAAS,CAAC,EAAE,MAAM,GAAG,IAAI,GAAG,OAAO,CAAC,WAAW,CAAC;IAIvD,SAAS,CAAC,KAAK,EAAE,cAAc,GAAG,OAAO,CAAC,IAAI,CAAC,aAAa,CAAC,CAAC;IAIrE,kFAAkF;IAC3E,KAAK,CAAC,KAAK,EAAE,cAAc,GAAG,OAAO,CAAC,UAAU,CAAC;IAOxD,gDAAgD;IACzC,KAAK,CAAC,OAAO,EAAE,MAAM,GAAG,OAAO,CAAC,WAAW,CAAC;IAI5C,UAAU,CAAC,OAAO,EAAE,MAAM,EAAE,MAAM,CAAC,EAAE,MAAM,GAAG,OAAO,CAAC,YAAY,CAAC;IAOnE,WAAW,CAAC,KAAK,EAAE,kBAAkB,GAAG,OAAO,CAAC,KAAK,CAAC;IAI7D,kHAAkH;IAC3G,WAAW,CAChB,OAAO,EAAE,MAAM,EACf,KAAK,EAAE,kBAAkB,GACxB,OAAO,CAAC,iBAAiB,CAAC;IAItB,WAAW,CAAC,OAAO,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC;IAI3C,YAAY,CAAC,OAAO,EAAE,MAAM,GAAG,OAAO,CAAC,KAAK,CAAC;IAMpD,4DAA4D;IACrD,SAAS,IAAI,OAAO,CAAC,eAAe,EAAE,CAAC;IAIvC,cAAc,CACnB,SAAS,EAAE,MAAM,EACjB,QAAQ,EAAE,SAAS,GAAG,QAAQ,EAC9B,OAAO,CAAC,EAAE,MAAM,GACf,OAAO,CAAC,eAAe,CAAC;IAQpB,gBAAgB,CAAC,SAAS,EAAE,MAAM,GAAG,OAAO,CAAC,eAAe,CAAC;IAIpE,8GAA8G;IACvG,aAAa,CAClB,OAAO,EAAE,MAAM,EACf,KAAK,EAAE,oBAAoB,GAC1B,OAAO,CAAC,eAAe,CAAC;IAQ3B,oFAAoF;IAC7E,kBAAkB,CACvB,OAAO,EAAE,MAAM,EACf,KAAK,EAAE,oBAAoB,GAC1B,OAAO,CAAC,IAAI,CAAC;IAQT,gBAAgB,CACrB,OAAO,EAAE,MAAM,EACf,YAAY,EAAE,MAAM,GACnB,OAAO,CAAC,IAAI,CAAC;IAOhB,mGAAmG;IAC5F,gBAAgB,CACrB,OAAO,EAAE,MAAM,EACf,SAAS,EAAE,MAAM,EACjB,OAAO,EAAE,MAAM,EACf,KAAK,EAAE,0BAA0B,GAChC,OAAO,CAAC,cAAc,CAAC;IAU1B,sFAAsF;IAC/E,OAAO,CAAC,OAAO,EAAE,MAAM,EAAE,MAAM,CAAC,EAAE,MAAM,GAAG,OAAO,CAAC,UAAU,CAAC;IAO9D,aAAa,CAClB,OAAO,EAAE,MAAM,EACf,KAAK,EAAE,oBAAoB,GAC1B,OAAO,CAAC,mBAAmB,CAAC;IAIxB,aAAa,CAClB,SAAS,EAAE,MAAM,EACjB,OAAO,EAAE,MAAM,GACd,OAAO,CAAC,YAAY,CAAC;IAMjB,aAAa,CAAC,SAAS,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC;IAItD,iEAAiE;IAC1D,KAAK,CACV,SAAS,EAAE,MAAM,EACjB,KAAK,EAAE,MAAM,GACZ,OAAO,CAAC,SAAS,eAAe,EAAE,CAAC;IAItC,mEAAmE;IAC5D,OAAO,CACZ,SAAS,EAAE,MAAM,EACjB,KAAK,EAAE,MAAM,GACZ,OAAO,CAAC,SAAS,eAAe,EAAE,CAAC;YAIxB,QAAQ;IAaf,iBAAiB,CACtB,SAAS,EAAE,MAAM,EACjB,QAAQ,EAAE,OAAO,GAChB,OAAO,CAAC,gBAAgB,CAAC;IAOrB,eAAe,CACpB,OAAO,EAAE,MAAM,EACf,UAAU,EAAE,OAAO,GAClB,OAAO,CAAC,iBAAiB,CAAC;IAO7B,iGAAiG;IAC1F,iBAAiB,CAAC,KAAK,EAAE;QAC9B,QAAQ,CAAC,OAAO,CAAC,EAAE,MAAM,CAAC;QAC1B,QAAQ,CAAC,CAAC,CAAC,EAAE,MAAM,CAAC;QACpB,QAAQ,CAAC,KAAK,CAAC,EAAE,MAAM,CAAC;KACzB,GAAG,OAAO,CAAC,gBAAgB,EAAE,CAAC;IAU/B,6FAA6F;IACtF,gBAAgB,CACrB,IAAI,EAAE,IAAI,EACV,MAAM,CAAC,EAAE,WAAW,GACnB,OAAO,CAAC,UAAU,CAAC;IAItB,gDAAgD;IACzC,qBAAqB,CAC1B,OAAO,EAAE,MAAM,EACf,IAAI,EAAE,IAAI,EACV,MAAM,CAAC,EAAE,WAAW,GACnB,OAAO,CAAC,UAAU,CAAC;IAQf,gBAAgB,CAAC,OAAO,EAAE,MAAM,GAAG,OAAO,CAAC,UAAU,EAAE,CAAC;IAIxD,gBAAgB,CAAC,YAAY,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC;YAI9C,MAAM;YAgBN,IAAI;YAQJ,GAAG;YAQH,IAAI;CAYnB"}
+{"version":3,"file":"client.d.ts","sourceRoot":"","sources":["../../../client/api/client.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AACH,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,sBAAsB,CAAC;AAEtD,OAAO,KAAK,EAAE,IAAI,EAAE,MAAM,wBAAwB,CAAC;AACnD,OAAO,KAAK,EAAE,UAAU,EAAE,MAAM,6BAA6B,CAAC;AAC9D,OAAO,EAEL,KAAK,eAAe,EAEpB,KAAK,oBAAoB,EACzB,KAAK,mBAAmB,EACxB,KAAK,YAAY,EACjB,KAAK,gBAAgB,EACrB,KAAK,UAAU,EACf,KAAK,gBAAgB,EACtB,MAAM,0BAA0B,CAAC;AAClC,OAAO,KAAK,EACV,wBAAwB,EACxB,UAAU,EACV,gBAAgB,EACjB,MAAM,6BAA6B,CAAC;AACrC,OAAO,EAGL,KAAK,YAAY,EACjB,KAAK,kBAAkB,EACvB,KAAK,KAAK,EACV,KAAK,UAAU,EACf,KAAK,WAAW,EAChB,KAAK,aAAa,EAClB,KAAK,cAAc,EAEnB,KAAK,gBAAgB,EACrB,KAAK,kBAAkB,EACvB,KAAK,iBAAiB,EACvB,MAAM,wBAAwB,CAAC;AAChC,OAAO,KAAK,EACV,kBAAkB,EAClB,KAAK,EACL,kBAAkB,EACnB,MAAM,wBAAwB,CAAC;AAChC,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,uBAAuB,CAAC;AAC/D,OAAO,KAAK,EAAE,WAAW,EAAE,EAAE,EAAE,MAAM,EAAE,MAAM,yBAAyB,CAAC;AACvE,OAAO,KAAK,EACV,oBAAoB,EACpB,4BAA4B,EAC5B,aAAa,EACb,eAAe,EACf,eAAe,EACf,oBAAoB,EACpB,4BAA4B,EAC7B,MAAM,0BAA0B,CAAC;AAClC,OAAO,KAAK,EACV,qBAAqB,EACrB,iBAAiB,EAClB,MAAM,0BAA0B,CAAC;AAClC,OAAO,KAAK,EACV,oBAAoB,EACpB,eAAe,EACf,uBAAuB,EACxB,MAAM,0BAA0B,CAAC;AAClC,OAAO,KAAK,EAAE,OAAO,EAAE,MAAM,wBAAwB,CAAC;AACtD,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,+BAA+B,CAAC;AAyCvE,qBAAa,KAAK;IACG,OAAO,CAAC,QAAQ,CAAC,GAAG;gBAAH,GAAG,EAAE,SAAS;IAI3C,EAAE,IAAI,OAAO,CAAC,EAAE,CAAC;IAIjB,OAAO,IAAI,OAAO,CAAC,MAAM,EAAE,CAAC;IAInC,6FAA6F;IACtF,YAAY,IAAI,OAAO,CAAC,WAAW,EAAE,CAAC;IAI7C,kFAAkF;IAC3E,SAAS,IAAI,OAAO,CAAC,iBAAiB,EAAE,CAAC;IAIzC,WAAW,IAAI,OAAO,CAAC,UAAU,EAAE,CAAC;IAI9B,MAAM,CACjB,KAAK,EAAE,wBAAwB,GAC9B,OAAO,CAAC,SAAS,gBAAgB,EAAE,CAAC;IAOhC,gBAAgB,CACrB,YAAY,EAAE,MAAM,EACpB,SAAS,GAAE,OAAc,GACxB,OAAO,CAAC,gBAAgB,CAAC;IAOrB,gBAAgB,CAAC,YAAY,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC;IAMrD,QAAQ,IAAI,OAAO,CAAC,iBAAiB,CAAC;IAItC,cAAc,CACnB,KAAK,EAAE,qBAAqB,GAC3B,OAAO,CAAC,iBAAiB,CAAC;IAItB,MAAM,IAAI,OAAO,CAAC,KAAK,EAAE,CAAC;IAI1B,WAAW,CAAC,KAAK,EAAE,kBAAkB,GAAG,OAAO,CAAC,KAAK,CAAC;IAItD,WAAW,CAChB,OAAO,EAAE,MAAM,EACf,KAAK,EAAE,kBAAkB,GACxB,OAAO,CAAC,KAAK,CAAC;IAIV,WAAW,CAAC,OAAO,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC;IAM3C,QAAQ,IAAI,OAAO,CAAC,eAAe,EAAE,CAAC;IAItC,OAAO,CAAC,SAAS,EAAE,MAAM,GAAG,OAAO,CAAC,aAAa,CAAC;IAIlD,aAAa,CAAC,KAAK,EAAE,oBAAoB,GAAG,OAAO,CAAC,aAAa,CAAC;IAIlE,aAAa,CAClB,SAAS,EAAE,MAAM,EACjB,KAAK,EAAE,oBAAoB,GAC1B,OAAO,CAAC,aAAa,CAAC;IAIlB,aAAa,CAAC,SAAS,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC;IAItD,gCAAgC;IACzB,gBAAgB,CAAC,SAAS,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM,GAAG,OAAO,CAAC,OAAO,CAAC;IAMrE,mBAAmB,CAAC,SAAS,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC;IAOrE,kBAAkB,CACvB,SAAS,EAAE,MAAM,EACjB,KAAK,EAAE,4BAA4B,GAClC,OAAO,CAAC,eAAe,CAAC;IAIpB,qBAAqB,CAC1B,SAAS,EAAE,MAAM,EACjB,UAAU,EAAE,MAAM,EAClB,KAAK,EAAE,4BAA4B,GAClC,OAAO,CAAC,eAAe,CAAC;IAQpB,qBAAqB,CAC1B,SAAS,EAAE,MAAM,EACjB,UAAU,EAAE,MAAM,GACjB,OAAO,CAAC,IAAI,CAAC;IAShB,oCAAoC;IAC7B,QAAQ,IAAI,OAAO,CAAC,gBAAgB,EAAE,CAAC;IAIvC,SAAS,CAAC,KAAK,EAAE,cAAc,GAAG,OAAO,CAAC,IAAI,CAAC,aAAa,CAAC,CAAC;IAIrE,kFAAkF;IAC3E,KAAK,CAAC,KAAK,EAAE,cAAc,GAAG,OAAO,CAAC,UAAU,CAAC;IAOxD,gDAAgD;IACzC,KAAK,CAAC,OAAO,EAAE,MAAM,GAAG,OAAO,CAAC,WAAW,CAAC;IAI5C,UAAU,CAAC,OAAO,EAAE,MAAM,EAAE,MAAM,CAAC,EAAE,MAAM,GAAG,OAAO,CAAC,YAAY,CAAC;IAOnE,WAAW,CAAC,KAAK,EAAE,kBAAkB,GAAG,OAAO,CAAC,KAAK,CAAC;IAI7D,kCAAkC;IAC3B,WAAW,CAChB,OAAO,EAAE,MAAM,EACf,KAAK,EAAE,kBAAkB,GACxB,OAAO,CAAC,iBAAiB,CAAC;IAItB,WAAW,CAAC,OAAO,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC;IAI3C,YAAY,CAAC,OAAO,EAAE,MAAM,GAAG,OAAO,CAAC,KAAK,CAAC;IAIpD,8GAA8G;IACvG,aAAa,CAClB,OAAO,EAAE,MAAM,EACf,KAAK,EAAE,oBAAoB,GAC1B,OAAO,CAAC,eAAe,CAAC;IAQ3B,gGAAgG;IACzF,gBAAgB,CACrB,OAAO,EAAE,MAAM,EACf,YAAY,EAAE,MAAM,EACpB,KAAK,EAAE,uBAAuB,GAC7B,OAAO,CAAC,eAAe,CAAC;IAQ3B,oFAAoF;IAC7E,kBAAkB,CACvB,OAAO,EAAE,MAAM,EACf,KAAK,EAAE,oBAAoB,GAC1B,OAAO,CAAC,IAAI,CAAC;IAQT,gBAAgB,CACrB,OAAO,EAAE,MAAM,EACf,YAAY,EAAE,MAAM,GACnB,OAAO,CAAC,IAAI,CAAC;IAShB,sFAAsF;IAC/E,OAAO,CAAC,OAAO,EAAE,MAAM,EAAE,MAAM,CAAC,EAAE,MAAM,GAAG,OAAO,CAAC,UAAU,CAAC;IAO9D,aAAa,CAClB,OAAO,EAAE,MAAM,EACf,KAAK,EAAE,oBAAoB,GAC1B,OAAO,CAAC,mBAAmB,CAAC;IAIxB,aAAa,CAClB,SAAS,EAAE,MAAM,EACjB,OAAO,EAAE,MAAM,GACd,OAAO,CAAC,YAAY,CAAC;IAMjB,aAAa,CAAC,SAAS,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC;IAItD,iEAAiE;IAC1D,KAAK,CACV,SAAS,EAAE,MAAM,EACjB,KAAK,EAAE,MAAM,GACZ,OAAO,CAAC,SAAS,eAAe,EAAE,CAAC;IAItC,mEAAmE;IAC5D,OAAO,CACZ,SAAS,EAAE,MAAM,EACjB,KAAK,EAAE,MAAM,GACZ,OAAO,CAAC,SAAS,eAAe,EAAE,CAAC;YAIxB,QAAQ;IAaf,iBAAiB,CACtB,SAAS,EAAE,MAAM,EACjB,QAAQ,EAAE,OAAO,GAChB,OAAO,CAAC,gBAAgB,CAAC;IAOrB,eAAe,CACpB,OAAO,EAAE,MAAM,EACf,UAAU,EAAE,OAAO,GAClB,OAAO,CAAC,iBAAiB,CAAC;IAO7B,iGAAiG;IAC1F,iBAAiB,CAAC,KAAK,EAAE;QAC9B,QAAQ,CAAC,OAAO,CAAC,EAAE,MAAM,CAAC;QAC1B,QAAQ,CAAC,CAAC,CAAC,EAAE,MAAM,CAAC;QACpB,QAAQ,CAAC,KAAK,CAAC,EAAE,MAAM,CAAC;KACzB,GAAG,OAAO,CAAC,gBAAgB,EAAE,CAAC;IAU/B,6FAA6F;IACtF,gBAAgB,CACrB,IAAI,EAAE,IAAI,EACV,MAAM,CAAC,EAAE,WAAW,GACnB,OAAO,CAAC,UAAU,CAAC;IAItB,gDAAgD;IACzC,qBAAqB,CAC1B,OAAO,EAAE,MAAM,EACf,IAAI,EAAE,IAAI,EACV,MAAM,CAAC,EAAE,WAAW,GACnB,OAAO,CAAC,UAAU,CAAC;IAQf,gBAAgB,CAAC,OAAO,EAAE,MAAM,GAAG,OAAO,CAAC,UAAU,EAAE,CAAC;IAIxD,gBAAgB,CAAC,YAAY,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC;YAI9C,MAAM;YAgBN,IAAI;YAQJ,GAAG;YAQH,IAAI;CAYnB"}