fix: vulnerabilities

AGENTS.md

@@ -55,13 +55,12 @@ constants live in `helpers/consts.ts`.
 
 `executeAndLinkItems` owns the per-input-item loop, `pairedItem` linking, and `continueOnFail()`.
 Input iteration there and in `executeActor` has caused duplicate-run regressions before, so
-change it carefully. Because `continueOnFail` lives there, `Apify.node.ts#execute` carries an
-intentional `require-continue-on-fail` eslint-disable — leave it.
+change it carefully.
 
 ### Node → resource → operation tree
 
 `Apify.node.ts` is thin: properties from `Apify.properties.ts`, methods from `resources/index.ts`,
-`execute` delegating to `resources/router.ts`. Both nodes set `usableAsTool: true`.
+`execute` delegating to `resources/router.ts`. Only the action node sets `usableAsTool: true`.
 
 Every level of `nodes/Apify/resources/` repeats the same shape:
 

nodes/Apify/Apify.node.ts

@@ -56,7 +56,6 @@ export class Apify implements INodeType {
 	methods = methods;
 
 	// continueOnFail is handled inside executeAndLinkItems (see resources/genericFunctions.ts).
-	// eslint-disable-next-line @n8n/community-nodes/require-continue-on-fail
 	async execute(this: IExecuteFunctions) {
 		return await executeAndLinkItems.call(this, async function (this: IExecuteFunctions, itemIndex: number) {
 			return await resourceRouter.call(this, itemIndex);

nodes/Apify/ApifyTrigger.node.ts

@@ -151,7 +151,6 @@ export class ApifyTrigger implements INodeType {
 				description: 'The status of the Actor or task run that should trigger the workflow',
 			},
 		]),
-		usableAsTool: true,
 	};
 
 	webhookMethods = {