d365fo-mcp 1.12.0 → 1.13.0

package/dist/bridge/bridgeAdapter.js

@@ -1140,8 +1140,20 @@ const BRIDGE_MODIFY_OPS = new Set([
     'modify-property',
     'add-enum-value', 'modify-enum-value', 'remove-enum-value',
     'add-control', 'add-data-source',
+    // Removal of a control, and of a privilege's entry point, have no C# op either
+    // (MetadataWriteService exposes no RemoveControl, and security objects have no
+    // bridge write path at all) — both are served by a direct-XML writer and still
+    // pass through this gate.
+    'remove-control', 'remove-entry-point',
+    // AxIgnoreDiagnosticList is not an AOT object at all — MetadataWriteService has
+    // no concept of it — so this is XML-only for the same structural reason as the
+    // two above.
+    'remove-diagnostic-suppression', 'add-diagnostic-suppression',
     'add-display-method', 'add-table-method',
     'add-field-modification', 'add-menu-item-to-menu',
+    // No C# op exists for query ranges on entities — served entirely by a
+    // direct-XML writer (data-entity is already in BRIDGE_MODIFY_TYPES).
+    'add-query-range', 'remove-query-range',
 ]);
 /**
  * Supported object types for bridge-based modification.
@@ -1156,6 +1168,25 @@ const BRIDGE_MODIFY_TYPES = new Set([
     'menu-item-action', 'menu-item-display', 'menu-item-output',
     'menu',
 ]);
+/**
+ * Operation → the object types it may target that BRIDGE_MODIFY_TYPES does not
+ * cover, because a direct-XML writer serves the pair and the bridge never will.
+ *
+ * This gate is what EVERY modify operation clears before dispatch, whether or not
+ * a C# op backs it, so an XML-only writer for an XML-only type has nowhere else to
+ * be admitted. The pairing is per-operation rather than per-type on purpose:
+ * dropping 'security-privilege' into BRIDGE_MODIFY_TYPES would also claim
+ * add-method, replace-code and modify-property work on a privilege, which they do
+ * not — the bridge has no write path for security objects at all (the same reason
+ * they are absent from BRIDGE_CREATE_TYPES: a generic
+ * Dictionary<string,string> cannot carry <EntryPoints>). The caller would then get
+ * a bridge resolution failure instead of "not supported for this object type".
+ */
+const XML_ONLY_MODIFY_PAIRS = {
+    'remove-entry-point': new Set(['security-privilege']),
+    'remove-diagnostic-suppression': new Set(['ignore-diagnostic-list']),
+    'add-diagnostic-suppression': new Set(['ignore-diagnostic-list']),
+};
 /**
  * Names the properties the bridge could not write, for appending to a success message.
  *
@@ -1180,7 +1211,11 @@ export function canBridgeCreate(objectType) {
  * Checks if bridge can handle this modify operation.
  */
 export function canBridgeModify(objectType, operation) {
-    return BRIDGE_MODIFY_TYPES.has(objectType.toLowerCase()) && BRIDGE_MODIFY_OPS.has(operation.toLowerCase());
+    const type = objectType.toLowerCase();
+    const op = operation.toLowerCase();
+    if (!BRIDGE_MODIFY_OPS.has(op))
+        return false;
+    return BRIDGE_MODIFY_TYPES.has(type) || (XML_ONLY_MODIFY_PAIRS[op]?.has(type) ?? false);
 }
 /**
  * Give a create's X++ the same doc comments and indentation the XML fallback gives it.

package/dist/server/serverMode.d.ts

@@ -36,8 +36,8 @@ export declare const LOCAL_TOOLS: Set<string>;
  *    SQLite-backed types (Azure read-only).
  *  - labels: read actions (search/info) work on Azure; write actions
  *    (create/rename) need K:\ and error clearly when unreachable.
- *  - d365fo_file: generate works on Azure; create/modify need K:\ and error
- *    clearly when unreachable.
+ *  - d365fo_file: generate works on Azure; create/modify/delete need K:\ and
+ *    error clearly when unreachable.
  */
 export declare const ALWAYS_TOOLS: Set<string>;
 /**

package/dist/server/serverMode.js

@@ -46,8 +46,8 @@ export const LOCAL_TOOLS = new Set([
  *    SQLite-backed types (Azure read-only).
  *  - labels: read actions (search/info) work on Azure; write actions
  *    (create/rename) need K:\ and error clearly when unreachable.
- *  - d365fo_file: generate works on Azure; create/modify need K:\ and error
- *    clearly when unreachable.
+ *  - d365fo_file: generate works on Azure; create/modify/delete need K:\ and
+ *    error clearly when unreachable.
  */
 export const ALWAYS_TOOLS = new Set([
     'get_object_info',

package/dist/server/toolAnnotations.js

@@ -56,7 +56,7 @@ export const TOOL_ANNOTATIONS = {
     // File & label writes. Marked destructive/write so clients prompt for
     // confirmation even though some actions (generate, search/info) are read-only —
     // annotations are hints, not gates.
-    d365fo_file: write('D365FO file (create/modify/generate)', { destructive: true }),
+    d365fo_file: write('D365FO file (create/modify/delete/generate)', { destructive: true }),
     labels: write('Label operations', { destructive: true }),
     undo_last_modification: write('Undo last modification', { destructive: true }),
     generate_object: write('Generate code (pattern/scaffold)'),

package/dist/server/toolSchemas/d365foFile.js

@@ -14,10 +14,11 @@
  */
 export const d365foFileTool = {
     name: 'd365fo_file',
-    description: `Create, modify, or generate a D365FO AOT object. Choose an \`action\`:
+    description: `Create, modify, delete, or generate a D365FO AOT object. Choose an \`action\`:
 • create → write a NEW object file into PackagesLocalDirectory (UTF-8 BOM, auto-added to .rnrproj). THE WRITE STEP — incomplete until isError=false; ⚠️/❌ = failure. Extensions: objectName="Base.PrefixExtension".
 • modify → edit an EXISTING object. APPLIES IMMEDIATELY, no dry-run — confirm with the user first; revert with undo_last_modification. Needs \`operation\`.
-• generate → XML as TEXT only, no write (Azure/Linux fallback). Try create first. create/modify need Windows.
+• delete → remove an object's XML from disk AND un-register it from every .rnrproj of the model that lists it. IRREVERSIBLE — confirm with the user first. Reports ❌ when the object is not found, never a silent no-op.
+• generate → XML as TEXT only, no write (Azure/Linux fallback). Try create first. create/modify/delete need Windows.
 📖 Parameters are NOT inlined here: get_knowledge(kind="op-spec", topic="<operation>"|"<objectType>") returns the contract for the one you picked — pass its values nested in \`params\` (modify) / \`properties\` (create), along with any packageName/packagePath/solutionPath/workspacePath override.
 Model + prefix auto-applied. Classes: member vars inside the class { }, methods after the closing }.`,
     inputSchema: {
@@ -25,8 +26,8 @@ Model + prefix auto-applied. Classes: member vars inside the class { }, methods
         properties: {
             action: {
                 type: 'string',
-                enum: ['create', 'modify', 'generate'],
-                description: 'One of the three modes described above.',
+                enum: ['create', 'modify', 'delete', 'generate'],
+                description: 'One of the four modes described above.',
             },
             objectType: {
                 type: 'string',
@@ -38,12 +39,13 @@ Model + prefix auto-applied. Classes: member vars inside the class { }, methods
                     'menu-item-display', 'menu-item-action', 'menu-item-output', 'menu',
                     'security-privilege', 'security-duty', 'security-role',
                     'security-duty-extension', 'security-role-extension',
+                    'ignore-diagnostic-list',
                     'business-event', 'tile', 'kpi', 'map',
                     'service', 'service-group',
                     'macro', 'configuration-key', 'security-policy', 'aggregate-measurement', 'license-code',
                 ],
                 description: 'Each security/menu-item type is its own AOT folder — NEVER use security-privilege for duty or role. ' +
-                    '[modify]/[generate] cover the core families + their *-extension variants.'
+                    '[modify]/[generate] cover the core families + their *-extension variants; [delete] takes the same enum as [create].'
             },
             objectName: {
                 type: 'string',
@@ -85,10 +87,12 @@ Model + prefix auto-applied. Classes: member vars inside the class { }, methods
                     'add-delete-action', 'remove-delete-action',
                     'add-field-group', 'remove-field-group', 'add-field-to-field-group',
                     'add-field-modification',
-                    'add-data-source', 'add-control',
+                    'add-data-source', 'add-control', 'remove-control',
+                    'remove-entry-point', 'remove-diagnostic-suppression', 'add-diagnostic-suppression',
                     'add-enum-value', 'modify-enum-value', 'remove-enum-value',
                     'add-menu-item-to-menu',
                     'modify-property',
+                    'add-query-range', 'remove-query-range',
                 ],
                 description: '[modify] REQUIRED unless using operations[]. add-method also UPDATES in place; replace-code is the surgical oldCode→newCode path. ' +
                     'Parameters: get_knowledge(kind="op-spec", topic="<operation>").'
@@ -109,7 +113,7 @@ Model + prefix auto-applied. Classes: member vars inside the class { }, methods
                     'topic="<operation>"). A missing/wrong one returns that COMPLETE spec — follow it, do not guess.',
             },
             createBackup: { type: 'boolean', description: '[modify] Back up before modifying.', default: false },
-            filePath: { type: 'string', description: '[modify] Absolute XML path — bypasses symbol-DB lookup. Use for objects just created.' },
+            filePath: { type: 'string', description: '[modify|delete] Absolute XML path — bypasses symbol-DB lookup. Use for objects just created.' },
         },
         required: ['action'],
     },

package/dist/tools/d365foFile.d.ts

@@ -1,10 +1,11 @@
 /**
  * d365fo_file Tool — unified file/metadata-operation entry point.
  *
- * Replaces three tools with one discriminated by `action`:
+ * One tool discriminated by `action`:
  *   • generate → produce AOT XML as TEXT only (Azure/Linux fallback, no write)
  *   • create   → write a NEW AOT object file into PackagesLocalDirectory (write)
  *   • modify   → edit an EXISTING object via IMetadataProvider (write)
+ *   • delete   → remove an object's XML and its .rnrproj registration (write)
  *
  * Like `labels`, this mixes a read-capable action (generate works on Azure
  * read-only) with write actions that need local Windows-VM filesystem access;
@@ -14,7 +15,7 @@
  */
 import type { CallToolRequest } from '@modelcontextprotocol/sdk/types.js';
 import type { XppServerContext } from '../types/context.js';
-export declare const D365_FILE_ACTIONS: readonly ['generate', 'create', 'modify'];
+export declare const D365_FILE_ACTIONS: readonly ['generate', 'create', 'modify', 'delete'];
 export type D365FileAction = (typeof D365_FILE_ACTIONS)[number];
 export declare function d365foFileTool(request: CallToolRequest, context: XppServerContext): Promise<any>;
 //# sourceMappingURL=d365foFile.d.ts.map

package/dist/tools/d365foFile.js

@@ -1,10 +1,11 @@
 /**
  * d365fo_file Tool — unified file/metadata-operation entry point.
  *
- * Replaces three tools with one discriminated by `action`:
+ * One tool discriminated by `action`:
  *   • generate → produce AOT XML as TEXT only (Azure/Linux fallback, no write)
  *   • create   → write a NEW AOT object file into PackagesLocalDirectory (write)
  *   • modify   → edit an EXISTING object via IMetadataProvider (write)
+ *   • delete   → remove an object's XML and its .rnrproj registration (write)
  *
  * Like `labels`, this mixes a read-capable action (generate works on Azure
  * read-only) with write actions that need local Windows-VM filesystem access;
@@ -15,13 +16,15 @@
 import { z } from 'zod';
 import { handleGenerateD365Xml } from './xml/generateD365Xml.js';
 import { handleCreateD365File } from './write/createD365File.js';
+import { handleDeleteD365File } from './write/deleteD365File.js';
 import { modifyD365FileTool } from './write/modifyD365File.js';
 import { resetRecentPrepares } from './prepare/prepare.js';
-export const D365_FILE_ACTIONS = ['generate', 'create', 'modify'];
+export const D365_FILE_ACTIONS = ['generate', 'create', 'modify', 'delete'];
 const D365FileArgsSchema = z
     .object({
     action: z.enum(D365_FILE_ACTIONS).describe('generate → XML text only (no file written, Azure/Linux fallback); ' +
-        'create → write a NEW object file (Windows); modify → edit an EXISTING object (Windows).'),
+        'create → write a NEW object file (Windows); modify → edit an EXISTING object (Windows); ' +
+        'delete → remove an object file and its project registration (Windows).'),
     // Operation-specific parameters may arrive nested in `params` (the published
     // schema advertises only this object) — they are flattened before dispatch.
     params: z.record(z.string(), z.unknown()).optional(),
@@ -163,7 +166,7 @@ export async function d365foFileTool(request, context) {
     // A write changes the AOT out from under anything prepare aggregated earlier, so
     // the remembered answers stop being answers. Cleared before the write rather than
     // after: a handler that throws half-way has still touched disk.
-    if (action === 'create' || action === 'modify') {
+    if (action === 'create' || action === 'modify' || action === 'delete') {
         resetRecentPrepares();
     }
     if (action === 'create') {
@@ -175,6 +178,9 @@ export async function d365foFileTool(request, context) {
         }
         return modifyD365FileTool(subRequest('modify_d365fo_file', rest), context);
     }
+    if (action === 'delete') {
+        return handleDeleteD365File(subRequest('delete_d365fo_file', rest), context);
+    }
     // generate: handler takes the request only (no context).
     return handleGenerateD365Xml(subRequest('generate_d365fo_xml', rest));
 }

package/dist/tools/knowledge/bpMonikerHelp.js

@@ -141,7 +141,13 @@ export async function bpMonikerHelpTool(request) {
     return {
         content: [{
                 type: 'text',
-                text: `${warningText}Add this inside <Items> of ` +
+                text: `${warningText}This is the <Diagnostic> block. You do not have to place it by hand — ` +
+                    `d365fo_file(action="modify", objectType="ignore-diagnostic-list", objectName="{Model}_BPSuppressions", ` +
+                    `operation="add-diagnostic-suppression") builds it from these same arguments and writes it into ` +
+                    `<Items> for you, creating the suppression file if the model has none yet. Pass the moniker as ` +
+                    `diagnosticMoniker, the path as diagnosticPath, and so on — get_knowledge(kind="op-spec", ` +
+                    `topic="add-diagnostic-suppression") has the full contract.\n\n` +
+                    `To place it manually instead, add it inside <Items> of ` +
                     `{Model}/{Model}/AxIgnoreDiagnosticList/{Model}_BPSuppressions.xml:\n\n${built.xml}`,
             }],
     };

package/dist/tools/specs/d365foFileOpSpecs.js

@@ -124,7 +124,9 @@ export const D365FO_FILE_PARAM_SPECS = {
     // form controls
     controlName: {
         type: 'string',
-        description: 'Name of the new form control — MUST match the field name in the table extension so the binding works.',
+        description: 'add-control: name of the new form control — MUST match the field name in the table extension so ' +
+            'the binding works. remove-control: <Name> of the existing control to delete, at any depth in the ' +
+            'design.',
     },
     parentControl: {
         type: 'string',
@@ -234,6 +236,22 @@ export const D365FO_FILE_PARAM_SPECS = {
         description: 'Optional join/link type when joinSource is set: InnerJoin | OuterJoin | ExistJoin | NotExistJoin | ' +
             'Delayed | Active | Passive.',
     },
+    // add-query-range
+    rangeField: {
+        type: 'string',
+        description: 'Field name to filter on (e.g. "IsActive"). Becomes <Field> in the range object.',
+    },
+    rangeName: {
+        type: 'string',
+        description: 'Name for the range object (<Name>). Defaults to rangeField when omitted. ' +
+            'Only ever matched against other ranges of the SAME data source.',
+    },
+    rangeValue: {
+        type: 'string',
+        description: 'Filter value the range applies (e.g. "1" for a NoYes field, "Sales" for an enum, ' +
+            '"1..99" for an interval). Required: a range with no value filters nothing. ' +
+            'For the empty-string filter pass the two characters "" — that is how D365FO stores it.',
+    },
     // enum values
     enumValueName: { type: 'string', description: 'Enum value name (e.g. "Approved").' },
     enumValueNewName: {
@@ -252,6 +270,80 @@ export const D365FO_FILE_PARAM_SPECS = {
         type: 'string',
         description: 'ISO country/region codes, comma-separated (e.g. "CZ,SK").',
     },
+    removeSeparator: {
+        type: 'boolean (default false)',
+        description: 'remove-control: also delete the adjacent AxFormButtonSeparatorControl — the sibling after the ' +
+            'control, else the one before it. Removing a toolbar button usually orphans its separator, which ' +
+            'then shows as a stray divider. Opt-in: a separator between two REMAINING buttons is load-bearing.',
+    },
+    // security privileges
+    entryPointName: {
+        type: 'string',
+        description: '<Name> of the AxSecurityEntryPointReference to remove — conventionally the menu item name. ' +
+            'This is the entry point ON the privilege, not the privilege itself (that is objectName).',
+    },
+    entryPointObjectName: {
+        type: 'string',
+        description: '<ObjectName> of the entry point — the menu item or service operation it grants access to. Use ' +
+            'instead of entryPointName when the entry point carries a different <Name> than its target.',
+    },
+    entryPointObjectType: {
+        type: 'string (MenuItemDisplay | MenuItemAction | MenuItemOutput | ServiceOperation | None)',
+        description: '<ObjectType> (EntryPointType) of the entry point. Only needed to disambiguate one ObjectName ' +
+            'referenced through two entry-point types — two matches are refused, never guessed.',
+    },
+    // BP-check suppressions
+    diagnosticPath: {
+        type: 'string',
+        description: 'remove-diagnostic-suppression: REQUIRED — exact <Path> of the <Diagnostic> to remove (e.g. ' +
+            '"dynamics://Form/MyForm"), copied verbatim from the suppression entry. ' +
+            'add-diagnostic-suppression: the dynamics:// path a BP-check finding was raised against — copy it ' +
+            'verbatim from the finding when you have it (the only way to address a sub-element: a control, a ' +
+            'field, a method, an enum value). Preferred over diagnosticElementType + diagnosticElementName, which ' +
+            'can only derive a path to a whole top-level object. This is the same value ' +
+            'get_knowledge(kind="bp-moniker", action="suppress") renders it from.',
+    },
+    diagnosticMoniker: {
+        type: 'string',
+        description: 'remove-diagnostic-suppression: <Moniker> of the suppression to remove. Only needed when the same ' +
+            'diagnosticPath carries more than one <Diagnostic> (two different rules ignored on the same target) ' +
+            '— two matches on path alone are refused, never guessed. ' +
+            'add-diagnostic-suppression: REQUIRED — the BP moniker being suppressed, validated against the known ' +
+            'catalog (e.g. "BPErrorPrivilegeNotCoveredByDuty").',
+    },
+    diagnosticElementType: {
+        type: 'string (AxClass | AxTable | AxForm | AxView | AxMap | AxEnum | AxQuerySimple | ' +
+            'AxDataEntityView | AxSecurityPrivilege | AxSecurityDuty | AxSecurityRole | AxTableExtension | ' +
+            'AxFormExtension | AxMenuExtension | AxMenu | AxMenuItemDisplay | AxMenuItemAction | ' +
+            'AxMenuItemOutput | AxEdtString | AxEdtInt | … | AxConfigurationKey | AxLicenseCode)',
+        description: 'add-diagnostic-suppression: top-level AOT element type of the object the finding was raised against ' +
+            '— used with diagnosticElementName to DERIVE diagnosticPath when it is not given directly. Only ' +
+            'addresses a whole object; a sub-element needs diagnosticPath verbatim from the finding instead.',
+    },
+    diagnosticElementName: {
+        type: 'string',
+        description: 'add-diagnostic-suppression: name of the object the finding was raised against, paired with ' +
+            'diagnosticElementType to derive diagnosticPath.',
+    },
+    diagnosticJustification: {
+        type: 'string',
+        description: 'add-diagnostic-suppression: why this warning is being ignored. Omitting it writes an obvious TODO ' +
+            'placeholder plus a warning — a suppression with no stated reason is what a reviewer rejects.',
+    },
+    diagnosticMessage: {
+        type: 'string',
+        description: 'add-diagnostic-suppression: the real message text from the BP-check finding, if known. Never ' +
+            'invented when omitted — <Message> is simply left off, which is normal (absent from most real entries).',
+    },
+    diagnosticSeverity: {
+        type: 'string (Error | Warning)',
+        description: 'add-diagnostic-suppression: <Severity> of the diagnostic being suppressed. Default: Warning.',
+    },
+    diagnosticItemSpecific: {
+        type: 'boolean (default false)',
+        description: 'add-diagnostic-suppression: emit the <ItemSpecific> block — rare, only for element-specific rules ' +
+            '(BPErrorUnknownLabel, BPXmlDoc*, BPErrorPrivilegeNotCoveredByDuty, …). Requires diagnosticElementName.',
+    },
     // menus
     menuItemToAdd: { type: 'string', description: 'Name of the menu item to add (e.g. "MyCustomForm").' },
     menuItemToAddType: {
@@ -376,6 +468,25 @@ export const D365FO_FILE_OP_SPECS = {
         optional: ['joinSource', 'linkType'],
         note: 'form-extension only.',
     },
+    'add-query-range': {
+        required: ['dataSourceName', 'rangeField', 'rangeValue'],
+        optional: ['rangeName'],
+        note: 'objectType="data-entity" only. Adds an <AxQuerySimpleDataSourceRange> to the <Ranges> that the ' +
+            'named data source OWNS inside <ViewMetadata>. dataSourceName is the <Name> of either the root ' +
+            'data source (<AxQuerySimpleRootDataSource>, usually the primary table) or a joined one ' +
+            '(<AxQuerySimpleEmbeddedDataSource>) — a joined data source keeps its own <Ranges>, and filtering ' +
+            'the joined table is not the same query as filtering the root. ' +
+            'rangeName defaults to rangeField when omitted. ' +
+            'rangeValue is required (e.g. "1" to restrict to active rows); pass "" (two characters) for the ' +
+            'empty-string filter. Idempotent per data source.',
+    },
+    'remove-query-range': {
+        required: ['dataSourceName', 'rangeName'],
+        optional: [],
+        note: 'objectType="data-entity" only. Removes the <AxQuerySimpleDataSourceRange> whose <Name> equals ' +
+            'rangeName from the <Ranges> the named data source OWNS — a same-named range on a joined data ' +
+            'source is left alone. Collapses <Ranges> to <Ranges /> when empty. Idempotent.',
+    },
     'add-control': {
         required: ['controlName', 'parentControl'],
         optional: [
@@ -397,6 +508,63 @@ export const D365FO_FILE_OP_SPECS = {
             + 'control in the XML, under a base-form parent it is written as '
             + '<PositionType>AfterItem</PositionType> + <PreviousSibling>.',
     },
+    'remove-control': {
+        required: ['controlName'],
+        optional: ['removeSeparator'],
+        note: 'objectType="form" or "form-extension". Removes the control WHEREVER it sits in the design — '
+            + 'controls nest (ActionPane → ButtonGroup → Button), so no parentControl is needed. '
+            + 'On a form-extension the whole <AxFormExtensionControl> envelope goes, not just its '
+            + '<FormControl>: an envelope without its control is a <Parent> reference to nothing. '
+            + 'A control the form SHOWS but does not DEFINE belongs to the base form and is reported as '
+            + 'not found — a form extension cannot delete a base control, only hide it '
+            + '(modify-property Visible=No on a control extension). Emptying a <Controls> collection '
+            + 'collapses it to <Controls />, the spelling the serializer uses.',
+    },
+    'remove-entry-point': {
+        required: [],
+        optional: ['entryPointName', 'entryPointObjectName', 'entryPointObjectType'],
+        mutationOneOf: ['entryPointName', 'entryPointObjectName'],
+        note: 'objectType="security-privilege". Removes one <AxSecurityEntryPointReference> — the block that '
+            + 'grants a menu item through this privilege. Identify it by entryPointName, or by '
+            + 'entryPointObjectName (+ entryPointObjectType when the same object is referenced through two '
+            + 'entry-point types). Two matches are REFUSED rather than resolved: removing the wrong entry '
+            + 'point revokes access to a different object, builds clean, and only surfaces as a user losing '
+            + 'a form. Removing the last one collapses <EntryPoints> to <EntryPoints />. '
+            + 'A privilege left with no entry points and no data-entity permissions grants nothing — delete '
+            + 'it with d365fo_file(action="delete") and drop its BP suppression entry.',
+    },
+    'remove-diagnostic-suppression': {
+        required: ['diagnosticPath'],
+        optional: ['diagnosticMoniker'],
+        note: 'objectType="ignore-diagnostic-list". Removes one <Diagnostic> from a {Model}_BPSuppressions.xml ' +
+            '— objectName is the file\'s own base name, "{Model}_BPSuppressions" (or pass filePath). Identify ' +
+            'the entry by diagnosticPath, the exact <Path> a BP-check finding was suppressed against; add ' +
+            'diagnosticMoniker when the same path carries more than one suppressed rule. Two matches on path ' +
+            'alone are REFUSED rather than resolved: removing the wrong one leaves a live finding silenced. ' +
+            'Removing the last entry collapses <Items> to <Items />. ' +
+            'd365fo_file(action="delete") already strips suppressions whose <Path> targets the deleted object ' +
+            '— use this operation for suppressions left stale by other means (a moniker fixed in code, a ' +
+            'renamed sub-element).',
+    },
+    'add-diagnostic-suppression': {
+        required: ['diagnosticMoniker'],
+        optional: [
+            'diagnosticPath', 'diagnosticElementType', 'diagnosticElementName',
+            'diagnosticJustification', 'diagnosticMessage', 'diagnosticSeverity', 'diagnosticItemSpecific',
+        ],
+        note: 'objectType="ignore-diagnostic-list". Adds one <Diagnostic> to a {Model}_BPSuppressions.xml — ' +
+            'objectName is the file\'s own base name, "{Model}_BPSuppressions" (or pass filePath). Needs ' +
+            'diagnosticMoniker PLUS either diagnosticPath (verbatim from the finding — the only way to address ' +
+            'a control/field/method/enum value) or diagnosticElementType + diagnosticElementName (derives a path ' +
+            'to a whole top-level object only). Builds the <Diagnostic> the same way ' +
+            'get_knowledge(kind="bp-moniker", action="suppress") does, so the two cannot describe two different ' +
+            'shapes — that helper is now redundant for anyone with write access to the metadata; call this ' +
+            'directly instead of rendering text to paste by hand. Refuses a duplicate (same diagnosticPath AND ' +
+            'diagnosticMoniker already present) rather than writing a second copy. When the model has never ' +
+            'suppressed anything before, {Model}_BPSuppressions.xml does not exist yet — this creates it and its ' +
+            'AxIgnoreDiagnosticList folder, in the shape real shipped suppression lists have, and says so in the ' +
+            'reply so you can add it to the model\'s .rnrproj if Visual Studio does not pick it up.',
+    },
     'add-enum-value': {
         required: ['enumValueName'],
         optional: ['enumValueLabel', 'enumValueHelpText', 'enumValueInt', 'enumValueCountryRegionCodes'],

package/dist/tools/specs/opSpecs.js

@@ -37,6 +37,13 @@ const LABELS_TOPICS = ['labels', 'label', 'labels.create', 'labels.rename', 'cre
  * spent on a dead end at the exact moment the caller was already unsure about a name.
  */
 const TOPIC_REDIRECTS = {
+    // `delete` is an ACTION, not an operation, so it has no entry in
+    // D365FO_FILE_OP_SPECS to resolve against — and it is the one action whose
+    // contract a caller most wants before calling it. Without this it fell through
+    // to the catalogue of 33 modify operations, none of which is what was asked.
+    delete: 'delete',
+    'delete-object': 'delete',
+    'remove-object': 'delete',
     naming: 'naming',
     prefix: 'naming',
     'object-naming': 'naming',
@@ -45,6 +52,36 @@ const TOPIC_REDIRECTS = {
     suffix: 'naming',
 };
 const REDIRECT_ANSWERS = {
+    delete: [
+        'd365fo_file(action="delete") — remove an AOT object from the model.',
+        '',
+        'Removes the object XML from disk AND the <Content Include> entry from every .rnrproj of the',
+        'model that lists it. Confirm with the user first, and run find_references first — every',
+        'remaining reference becomes a compile error. Recovery is only partial: when the model directory',
+        'is under git, undo_last_modification(filePath=…) restores the XML but NOT the project entries.',
+        '',
+        '  REQUIRED objectType (string): the same enum action="create" takes. It must match the AOT',
+        '      folder the file actually sits in — a mismatch is refused, because the un-register step',
+        '      builds its <Content Include> from it and would clean a different object.',
+        '  REQUIRED objectName (string): base name; the model prefix is applied on a miss, so the name',
+        '      passed to create resolves too. Optional when filePath is given (derived from the basename).',
+        '  optional modelName (string): owning model — auto-detected when omitted.',
+        '  optional filePath (string): absolute path to the .xml, bypassing lookup.',
+        '  optional packagePath (string): packages root, for metadata outside PackagesLocalDirectory.',
+        '  optional projectPath (string): a .rnrproj to include in the set searched for includes to remove.',
+        '  optional groundingToken (string): from prepare(mode="change"). Required for *-extension',
+        '      objects when GROUNDING_ENFORCE=true — the same gate create and modify apply.',
+        '',
+        'Refused, never silently skipped: an object that resolves to nothing (❌, so a wrong name is not',
+        'read as a completed delete), an objectType that disagrees with the file\'s AOT folder, a file in',
+        'a standard Microsoft model, one owned by a different custom model than the write anchor, and any',
+        'path outside the allowed metadata roots. A project that lists the object but whose entry could',
+        'not be removed is reported as ⚠️, never as "no project referenced it".',
+        '',
+        'Deleting a form control or a privilege entry point instead of a whole object:',
+        '  get_knowledge(kind="op-spec", topic="remove-control")',
+        '  get_knowledge(kind="op-spec", topic="remove-entry-point")',
+    ].join('\n'),
     naming: [
         'Naming is not an op-spec — it is resolved per model, so ask the tools that know your model:',
         '',
@@ -121,6 +158,8 @@ export function renderOpSpecIndex(unknownTopic) {
         'generate_object modes:',
         `  ${topics.generateModes.join(', ')}`,
         '',
+        'd365fo_file(action="delete") — the contract for removing an object (topic="delete").',
+        '',
         'd365fo_file resolution overrides (any action, nested in `params`):',
         ...Object.entries(D365FO_FILE_OVERRIDE_PARAMS).map(([k, v]) => `  ${k}: ${v}`),
         '',

package/dist/tools/write/deleteD365File.d.ts

@@ -0,0 +1,49 @@
+/**
+ * d365fo_file(action="delete") — remove an AOT object from the model.
+ *
+ * The counterpart to `create`, and it has to undo BOTH halves of what create
+ * did: the XML file on disk, and the `<Content Include>` entry that makes the
+ * element part of a Visual Studio project. Deleting only the file leaves an
+ * include pointing at nothing — VS reports it, nothing else does, and the next
+ * developer to open the project gets a load error for an object that was
+ * intentionally removed weeks earlier.
+ *
+ * It un-registers from EVERY project of the model that lists the object, not
+ * just the active one. An element may legitimately belong to several .rnrproj of
+ * one model (see registerFileInActiveProject for the measurement behind that),
+ * so cleaning only the active project is exactly the case that leaves a dangling
+ * include behind.
+ *
+ * Guards, in order, and none of them optional:
+ *   • grounding — the gate create and modify apply to *-extension objects, under
+ *     GROUNDING_ENFORCE=true. Exempting the one action that cannot be undone
+ *     would mean an agent barred from CREATING an extension without a prepare
+ *     token is free to DELETE one;
+ *   • the object must resolve to a real file — a name that matches nothing is
+ *     reported as ❌, never as "done" (a silent no-op reads as a successful
+ *     delete and the object is still in the build);
+ *   • path containment — the target must sit under a configured
+ *     <PackagesLocalDirectory>/<Package>/<Model>/Ax<Type>/<File>.xml layout, so
+ *     an explicit filePath cannot traverse out of the metadata tree;
+ *   • objectType against the file's own Ax<Type> folder — everything downstream
+ *     trusts objectType, and axFolderForObjectType answers 'AxClass' for anything
+ *     it does not recognise, so a mismatch would delete this file and un-register
+ *     a different object;
+ *   • model ownership — a file in a standard Microsoft model is refused
+ *     outright, and one owned by a different CUSTOM model than the write anchor
+ *     goes through the same cross-model refusal every write does.
+ *
+ * There is no bridge path: MetadataWriteService exposes no delete, and going
+ * through the provider would be worse anyway — the file and the project entry
+ * are what "deleted" means here, and both are on disk.
+ */
+import type { CallToolRequest } from '@modelcontextprotocol/sdk/types.js';
+import type { XppServerContext } from '../../types/context.js';
+export declare function handleDeleteD365File(request: CallToolRequest, context?: XppServerContext): Promise<{
+    content: Array<{
+        type: string;
+        text: string;
+    }>;
+    isError?: boolean;
+}>;
+//# sourceMappingURL=deleteD365File.d.ts.map