@mrrlin-dev/mcp 0.4.114 → 0.4.115

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/dist/bin.cjs +3 -2
  2. package/package.json +1 -1
package/dist/bin.cjs CHANGED
@@ -58732,7 +58732,7 @@ var mcpToolDescriptions = {
58732
58732
  [mcpToolNames.searchWikiPages]: "Search project Wiki pages using ranked full-text search. Returns excerpts suitable for grounding Director decisions.",
58733
58733
  [mcpToolNames.searchKnowledge]: "Search the rendered Mrrlin docs wiki using the lexical RAG index. Returns cited chunks with stable wiki_url fields.",
58734
58734
  [mcpToolNames.updatePlan]: "Update a plan/epic.",
58735
- [mcpToolNames.updateTask]: `Update a task. Honors DB invariants: closed_no_result requires linked Evidence wiki pages. Set directorThreadId here to persist the worker's resumable provider thread handle. specApproved: "approved" requires declaredOutcome (set it in the same call or earlier): an object {sentence, requires, verification} stating what must exist when the task is done.`,
58735
+ [mcpToolNames.updateTask]: `Update a task. Honors DB invariants: closed_no_result requires linked Evidence wiki pages. Set directorThreadId here to persist the worker's resumable provider thread handle. specApproved: "approved" requires declaredOutcome (set it in the same call or earlier): an object {sentence, requires, verification} stating what must exist when the task is done. The Director sets it itself when writing the spec. requires holds one kind; verification is "machine" for page, code_change or message, "human_tap" for document, file_set or structured_data.`,
58736
58736
  [mcpToolNames.resetDirectorThread]: "Clear a task's persisted Director execution thread handle so the next execution run starts a fresh provider thread. Records a director_thread_reset task event.",
58737
58737
  [mcpToolNames.archiveTask]: "Archive a task: hides it from default reads, removes it from plan progress and scheduler consideration, cancels its non-terminal execution runs, and closes its open inbox items. Reversible \u2014 the project owner can restore it with unarchive_task. Records an 'archived' task event.",
58738
58738
  [mcpToolNames.unarchiveTask]: "Restore an archived task to its original status and visibility. Owner-only \u2014 refused with NOT_PROJECT_OWNER for any other caller. Does not resurrect the execution runs or inbox items that were cancelled/closed when the task was archived. Records a 'restored' task event.",
@@ -61764,7 +61764,7 @@ Do NOT derail the current task - if the operator has an in-flight question, answ
61764
61764
  }
61765
61765
 
61766
61766
  // src/_generated/version.ts
61767
- var PKG_VERSION = "0.4.114";
61767
+ var PKG_VERSION = "0.4.115";
61768
61768
 
61769
61769
  // src/receipt-signing.ts
61770
61770
  var import_node_crypto13 = __toESM(require("node:crypto"), 1);
@@ -74560,6 +74560,7 @@ function buildThreadStartParams(msg, config2, desiredModel) {
74560
74560
  "- MUST include `## Verification`: the exact tests, commands, or checks that prove each criterion holds.",
74561
74561
  "- Keep behavior contracts in the spec; implementation details belong in `## Implementation Plan`.",
74562
74562
  "- Apply this format ONLY to Specs/{id} pages; do not retro-fit it onto other wiki page types.",
74563
+ "- With each spec, set the task's `declaredOutcome` via `update_task` yourself; approval needs it.",
74563
74564
  '- Spec consensus runs ASYNCHRONOUSLY. Call `run_spec_consensus` for a `Specs/{id}` page; it returns IMMEDIATELY. On `already_converged`, the spec is already marked ready \u2014 proceed straight to `create_execution_run`; do NOT call `mark_spec_ready` and do NOT re-run consensus. On `queued` or `already_running`, tell the user it was launched and END your turn \u2014 do NOT poll or call it again; the result arrives in the inbox (an `info` item on CONVERGED, a `handoff` item if it was blocked/failed). When a `handoff` says it was blocked, address the recorded issues in the spec (any edit re-arms the gate) and call `run_spec_consensus` once more. For a NON-code task (domain seo/marketing/content, ADR 0020): the low-risk lanes `seo`, `marketing`, and `content` proceed to `create_execution_run` after consensus converges, using the same flow as code tasks. When the review agrees, tell the operator "the reviewers agreed on the spec" and proceed to create_execution_run. When it does not, tell them the reviewers could not agree and that there is a decision question in the inbox. Never say "consensus", "converged", or "CONVERGED" to the operator; those are internal words.',
74564
74565
  "- When creating a task, classify and supply the `domain` field explicitly based on the nature of the work: pass `domain:'code'` for software engineering work, `domain:'seo'` for SEO/optimization, `domain:'marketing'` for marketing/growth, or `domain:'content'` for content creation/writing \u2014 the same way you select category/subcategory. A follow-up task spawned with `parentTaskId` inherits its parent's domain automatically and requires no explicit domain.",
74565
74566
  '- When a task needs a browser (login flows, UI verification/clicks, scraping), pass `prerequisites:[{mcp:"mrrlin-browser",reason:"..."}]` to `create_execution_run`. If that run later fails into a handoff, the operator gets a one-click "Launch browser & resume" that brings up the dedicated browser as the turn starts.',
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mrrlin-dev/mcp",
3
- "version": "0.4.114",
3
+ "version": "0.4.115",
4
4
  "type": "module",
5
5
  "bin": {
6
6
  "mrrlin-mcp": "dist/bin.cjs"