@anyforge/mcp-server 3.10.0 → 3.11.0
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.
- package/README.md +4 -1
- package/dist/index.js +7 -7
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -228,7 +228,7 @@ complete capability and local/remote workspace boundary.
|
|
|
228
228
|
| `anyforge_split_work_item` | write | Replace one unstarted work item with multiple children |
|
|
229
229
|
| `anyforge_merge_work_items` | write | Replace multiple unstarted work items with one merged item |
|
|
230
230
|
| `anyforge_list_crews` | read | Discover crews by status, active state, and limit |
|
|
231
|
-
| `anyforge_get_crew` | read | Crew state + recent outputs + comments |
|
|
231
|
+
| `anyforge_get_crew` | read | Crew state + recent outputs + comments. Leads with status, halt reason, work item, PR and timestamps; `shape: "summary"` (default) excerpts long text and leaves out large snapshots, naming each; `messages: 0` is the status read; `shape: "full"` for every field |
|
|
232
232
|
| `anyforge_post_crew_comment` | write | Comment on / @-mention people on a crew (the crew does not read comments; use `anyforge_message_crew` to steer a running crew, `anyforge_amend_crew` for one at a gate) |
|
|
233
233
|
| `anyforge_message_crew` | approve | Message a running crew's Engineer ("skip X", "check Z first"). It reads the message before its next step and confirms in the crew chat; a crew not yet started or stopped inside the Engineer reads it on its first step or on resume. Refused with `crew_not_reading_messages` at a gate, in review or when finished. Optional `idempotencyKey` makes a retry safe |
|
|
234
234
|
| `anyforge_resume_crew` | approve | Resume a PAUSED/HALTED crew |
|
|
@@ -293,6 +293,9 @@ complete capability and local/remote workspace boundary.
|
|
|
293
293
|
| `anyforge_update_report` | write | Change the title, description or settings, and edit widgets by id (`addWidgets`, `replaceWidgets`, `removeWidgetIds`) or replace the whole list (`widgets`). Every widget is validated as a Console save is; a refusal saves nothing |
|
|
294
294
|
| `anyforge_preview_report_query` | read | Run one report query against live data without saving anything: total, rows and a text summary (program, strategy and cycles snapshots included); needs a role that edits reports |
|
|
295
295
|
| `anyforge_describe_report_catalog` | read | The report data catalog: sources, measures, group-bys, filter fields and widget types; needs a role that edits reports |
|
|
296
|
+
| `anyforge_create_risk` | write | Record an accepted risk on a program, initiative or work item: owner (defaults to you), `reviewBy` date or `acceptedUntilMilestoneId`, trigger, mitigation. A risk never blocks dispatch, `Depends on` or the critical path |
|
|
297
|
+
| `anyforge_list_risks` | read | List accepted risks for a program (`programId`) or one subject (`subjectKind` + `subjectId`); closed risks only with `includeClosed` |
|
|
298
|
+
| `anyforge_update_risk` | write | Change a risk's status (for example `MATERIALISED` or `CLOSED`), owner, review date, mitigation or follow-up work items; only the fields passed change |
|
|
296
299
|
| `anyforge_list_report_filter_values` | read | The values a query filter field may take: an enum's closed set, or real ids with names (`query` looks one up by name); needs a role that edits reports |
|
|
297
300
|
| `anyforge_triage_ticket` | read | Run or continue a Support Triage interview — classification, readiness scoring, owning-team routing — and get a paste-ready rendering plus the structured draft; pass the same `sessionId` to continue an interview. Never files anything itself |
|
|
298
301
|
| `anyforge_list_triage_eval_cases` | read | List permitted triage eval cases; historical cases require Owner/Operator |
|