@n8n-as-code/n8nac 2.1.1-next.22 → 2.1.1-next.23

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/package.json +1 -1
  2. package/skills/n8n-architect/SKILL.md +93 -93
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@n8n-as-code/n8nac",
3
- "version": "2.1.1-next.22",
3
+ "version": "2.1.1-next.23",
4
4
  "description": "OpenClaw plugin for n8n-as-code — create and manage n8n workflows from OpenClaw",
5
5
  "keywords": [
6
6
  "n8n",
package/skills/n8n-architect/SKILL.md CHANGED
@@ -7,21 +7,21 @@ description: Use when the user explicitly wants to create, edit, validate, sync,
7
7
 
8
8
  Use this skill for all n8n-as-code work: workspace readiness, migration, environments, managed local instances, tunnels, workflow authoring, validation, sync, push, and pull.
9
9
 
10
- Use `npx --yes n8nac` as the primary interface. Use `npx --yes @n8n-as-code/n8n-manager` only for local managed runtime lifecycle, tunnels, and workflow presentation commands that are explicitly exposed by n8n-manager.
10
+ Use `npx --yes n8nac@next` as the primary interface. Use `npx --yes @n8n-as-code/n8n-manager@next` only for local managed runtime lifecycle, tunnels, and workflow presentation commands that are explicitly exposed by n8n-manager.
11
11
 
12
12
  ## Context Root Protocol
13
13
 
14
14
  - Treat the current context root as the directory containing `n8nac-config.json`, `AGENTS.md`, `.agents/skills`, and the workflow sync folder.
15
15
  - Generated context root hint: not embedded. Use the shell launch directory or the workspace path explicitly given by the user.
16
- - Before any n8n work, first run `npx --yes n8nac update-ai` from the context root, then read `AGENTS.md`. `update-ai` is designed to create or refresh the n8n-as-code block without destroying existing user or agent instructions.
16
+ - Before any n8n work, first run `npx --yes n8nac@next update-ai` from the context root, then read `AGENTS.md`. `update-ai` is designed to create or refresh the n8n-as-code block without destroying existing user or agent instructions.
17
17
  - Use the exact `n8nac command` and `n8n-manager command` listed in `AGENTS.md`. Those context-root commands override the portable examples in this skill.
18
- - Run every `npx --yes n8nac env ...`, `npx --yes n8nac workspace ...`, `npx --yes n8nac list`, `pull`, `push`, `validate`, `test`, and `update-ai` command from the context root unless the user explicitly gives another context root.
18
+ - Run every `npx --yes n8nac@next env ...`, `npx --yes n8nac@next workspace ...`, `npx --yes n8nac@next list`, `pull`, `push`, `validate`, `test`, and `update-ai` command from the context root unless the user explicitly gives another context root.
19
19
  - `AGENTS.md` is bootstrap context only, not a source of configuration truth.
20
20
  - Do not infer environment, project, sync folder, or workflow directory from `AGENTS.md`.
21
21
  - Before n8n work, resolve the effective context from the backend:
22
22
 
23
23
  ```bash
24
- npx --yes n8nac env status --json
24
+ npx --yes n8nac@next env status --json
25
25
  ```
26
26
 
27
27
  - Use the returned `workflowDir` for workflow files. Treat it as an opaque backend-derived path that may contain generated or hashed segments.
@@ -33,8 +33,8 @@ npx --yes n8nac env status --json
33
33
  Use the unified migration preflight before resolving the effective environment. The dry-run is safe and reports whether any workspace migration is required:
34
34
 
35
35
  ```bash
36
- npx --yes n8nac workspace migrate --json
37
- npx --yes n8nac env status --json
36
+ npx --yes n8nac@next workspace migrate --json
37
+ npx --yes n8nac@next env status --json
38
38
  ```
39
39
 
40
40
  - Treat `workspace migrate --json` as the source of migration need.
@@ -49,91 +49,91 @@ Migration is one user-facing command. Do not reason about internal migration pha
49
49
  1. Run the dry-run first:
50
50
 
51
51
  ```bash
52
- npx --yes n8nac workspace migrate --json
52
+ npx --yes n8nac@next workspace migrate --json
53
53
  ```
54
54
 
55
55
  2. If the dry-run reports `status: "dry-run"`, `required: true`, or otherwise indicates pending changes, stop and ask once before applying it. Do not run `workspace migrate --write` unless the user already directly requested applying migration.
56
56
  3. After confirmation, apply migration and re-check readiness:
57
57
 
58
58
  ```bash
59
- npx --yes n8nac workspace migrate --write
60
- npx --yes n8nac workspace migrate --json
61
- npx --yes n8nac env status --json
59
+ npx --yes n8nac@next workspace migrate --write
60
+ npx --yes n8nac@next workspace migrate --json
61
+ npx --yes n8nac@next env status --json
62
62
  ```
63
63
 
64
64
  - Do not run `workspace migrate --write` without explicit confirmation unless the user already directly requested applying migration.
65
- - When reporting a dry-run, summarize the unified `operations` list and ask for exactly one confirmation for `npx --yes n8nac workspace migrate --write`.
66
- - Do not ask separately for different operation types. `npx --yes n8nac workspace migrate --write` applies the required migration as one operation.
65
+ - When reporting a dry-run, summarize the unified `operations` list and ask for exactly one confirmation for `npx --yes n8nac@next workspace migrate --write`.
66
+ - Do not ask separately for different operation types. `npx --yes n8nac@next workspace migrate --write` applies the required migration as one operation.
67
67
  - Do not run environment, workflow, or setup commands while `workspace migrate --json` still reports migration required.
68
68
  - Managed local instances remain machine-global runtime resources.
69
- - Workspace environments remain workspace-scoped and are managed through `npx --yes n8nac env ...`.
69
+ - Workspace environments remain workspace-scoped and are managed through `npx --yes n8nac@next env ...`.
70
70
 
71
71
  ## Bootstrap Order
72
72
 
73
73
  1. `cd` to the context root.
74
- 2. Run `npx --yes n8nac update-ai`, then read `AGENTS.md`.
75
- 3. Run `npx --yes n8nac workspace migrate --json`.
76
- 4. If migration is required, stop and ask for confirmation before `npx --yes n8nac workspace migrate --write` unless the user already requested applying migration.
77
- 5. Run `npx --yes n8nac env status --json` after migration is not required or has been applied.
78
- 6. If the context root is not ready, inspect managed local instances with `npx --yes @n8n-as-code/n8n-manager instance list`.
74
+ 2. Run `npx --yes n8nac@next update-ai`, then read `AGENTS.md`.
75
+ 3. Run `npx --yes n8nac@next workspace migrate --json`.
76
+ 4. If migration is required, stop and ask for confirmation before `npx --yes n8nac@next workspace migrate --write` unless the user already requested applying migration.
77
+ 5. Run `npx --yes n8nac@next env status --json` after migration is not required or has been applied.
78
+ 6. If the context root is not ready, inspect managed local instances with `npx --yes @n8n-as-code/n8n-manager@next instance list`.
79
79
  7. Reuse an existing environment or managed local instance when suitable.
80
80
  8. If no suitable environment exists, stop and ask the user whether they want to connect a remote n8n URL or create/reuse a managed local n8n instance. Do not create infrastructure by default. If the user chooses a managed local instance, ask separately whether they want a public tunnel.
81
81
  9. Ask for host/API key only for an explicitly remote n8n environment.
82
82
  10. Configure the environment with:
83
83
 
84
84
  ```bash
85
- npx --yes n8nac env add <name> --base-url <url> --sync-folder workflows
86
- npx --yes n8nac env auth set <name> --api-key-stdin
87
- npx --yes n8nac env use <name>
85
+ npx --yes n8nac@next env add <name> --base-url <url> --sync-folder workflows
86
+ npx --yes n8nac@next env auth set <name> --api-key-stdin
87
+ npx --yes n8nac@next env use <name>
88
88
  ```
89
89
 
90
90
  For a managed local instance:
91
91
 
92
92
  ```bash
93
- npx --yes n8nac env add Local --managed-instance <id> --sync-folder workflows
94
- npx --yes n8nac env use Local
93
+ npx --yes n8nac@next env add Local --managed-instance <id> --sync-folder workflows
94
+ npx --yes n8nac@next env use Local
95
95
  ```
96
96
 
97
- 11. Run `npx --yes n8nac update-ai` after changing environments when the facade does not do it automatically.
97
+ 11. Run `npx --yes n8nac@next update-ai` after changing environments when the facade does not do it automatically.
98
98
 
99
99
  ## Environments
100
100
 
101
- Use `npx --yes n8nac env ...` for workspace environments, remote URLs, active environment, API-key binding, projects, and sync folders.
101
+ Use `npx --yes n8nac@next env ...` for workspace environments, remote URLs, active environment, API-key binding, projects, and sync folders.
102
102
 
103
103
  ```bash
104
- npx --yes n8nac env status --json
105
- npx --yes n8nac env list
106
- npx --yes n8nac env add <name> --base-url <url> --sync-folder workflows
107
- npx --yes n8nac env auth set <name> --api-key-stdin
108
- npx --yes n8nac env use <name>
104
+ npx --yes n8nac@next env status --json
105
+ npx --yes n8nac@next env list
106
+ npx --yes n8nac@next env add <name> --base-url <url> --sync-folder workflows
107
+ npx --yes n8nac@next env auth set <name> --api-key-stdin
108
+ npx --yes n8nac@next env use <name>
109
109
  ```
110
110
 
111
111
  - Prefer `--api-key-stdin` for API keys.
112
112
  - Do not pass secrets inline in shell arguments.
113
113
  - Do not ask for host/API key when the user wants a managed local Docker instance.
114
114
  - Do not print API keys or credential secret values back to the user.
115
- - If a command or flag is unfamiliar, run `npx --yes n8nac env --help` or `npx --yes n8nac env <subcommand> --help`.
115
+ - If a command or flag is unfamiliar, run `npx --yes n8nac@next env --help` or `npx --yes n8nac@next env <subcommand> --help`.
116
116
 
117
- Attach a managed local instance to the workspace with `npx --yes n8nac env ...`:
117
+ Attach a managed local instance to the workspace with `npx --yes n8nac@next env ...`:
118
118
 
119
119
  ```bash
120
- npx --yes n8nac env add Local --managed-instance <id> --sync-folder workflows
121
- npx --yes n8nac env use Local
120
+ npx --yes n8nac@next env add Local --managed-instance <id> --sync-folder workflows
121
+ npx --yes n8nac@next env use Local
122
122
  ```
123
123
 
124
124
  ## Managed Local Runtime
125
125
 
126
- Use `npx --yes @n8n-as-code/n8n-manager` only for local managed instance lifecycle, tunnels, and workflow presentation commands that are part of the local runtime layer.
126
+ Use `npx --yes @n8n-as-code/n8n-manager@next` only for local managed instance lifecycle, tunnels, and workflow presentation commands that are part of the local runtime layer.
127
127
 
128
128
  Inspect existing managed instances before changing local machine state:
129
129
 
130
130
  ```bash
131
- npx --yes @n8n-as-code/n8n-manager instance list
132
- npx --yes @n8n-as-code/n8n-manager instance --help
133
- npx --yes @n8n-as-code/n8n-manager config get
131
+ npx --yes @n8n-as-code/n8n-manager@next instance list
132
+ npx --yes @n8n-as-code/n8n-manager@next instance --help
133
+ npx --yes @n8n-as-code/n8n-manager@next config get
134
134
  ```
135
135
 
136
- Do not invent n8n-manager subcommands. Use `npx --yes @n8n-as-code/n8n-manager <subcommand> --help` when unsure.
136
+ Do not invent n8n-manager subcommands. Use `npx --yes @n8n-as-code/n8n-manager@next <subcommand> --help` when unsure.
137
137
 
138
138
  When the context root is not configured and no suitable existing instance is available, stop and ask the user to choose. Do not create infrastructure by default.
139
139
 
@@ -141,7 +141,7 @@ Present these choices clearly:
141
141
 
142
142
  - use an existing managed local instance if one is available;
143
143
  - create a new managed local n8n instance;
144
- - configure a remote n8n URL as a workspace environment through `npx --yes n8nac env`.
144
+ - configure a remote n8n URL as a workspace environment through `npx --yes n8nac@next env`.
145
145
 
146
146
  If the user chooses a managed local Docker instance, ask the tunnel question separately:
147
147
 
@@ -155,27 +155,27 @@ Only run these commands after the user has explicitly chosen the corresponding o
155
155
  Managed local instance without public tunnel:
156
156
 
157
157
  ```bash
158
- npx --yes @n8n-as-code/n8n-manager instance create
159
- npx --yes @n8n-as-code/n8n-manager instance start <id>
160
- npx --yes @n8n-as-code/n8n-manager instance list
158
+ npx --yes @n8n-as-code/n8n-manager@next instance create
159
+ npx --yes @n8n-as-code/n8n-manager@next instance start <id>
160
+ npx --yes @n8n-as-code/n8n-manager@next instance list
161
161
  ```
162
162
 
163
163
  Managed local instance with public tunnel:
164
164
 
165
165
  ```bash
166
- npx --yes @n8n-as-code/n8n-manager instance create
167
- npx --yes @n8n-as-code/n8n-manager instance start <id>
168
- npx --yes @n8n-as-code/n8n-manager tunnel start <id>
166
+ npx --yes @n8n-as-code/n8n-manager@next instance create
167
+ npx --yes @n8n-as-code/n8n-manager@next instance start <id>
168
+ npx --yes @n8n-as-code/n8n-manager@next tunnel start <id>
169
169
  ```
170
170
 
171
171
  Instance and tunnel operations are per managed local instance:
172
172
 
173
173
  ```bash
174
- npx --yes @n8n-as-code/n8n-manager instance start <id>
175
- npx --yes @n8n-as-code/n8n-manager instance stop <id>
176
- npx --yes @n8n-as-code/n8n-manager instance remove <id>
177
- npx --yes @n8n-as-code/n8n-manager tunnel start <id>
178
- npx --yes @n8n-as-code/n8n-manager tunnel stop <id>
174
+ npx --yes @n8n-as-code/n8n-manager@next instance start <id>
175
+ npx --yes @n8n-as-code/n8n-manager@next instance stop <id>
176
+ npx --yes @n8n-as-code/n8n-manager@next instance remove <id>
177
+ npx --yes @n8n-as-code/n8n-manager@next tunnel start <id>
178
+ npx --yes @n8n-as-code/n8n-manager@next tunnel stop <id>
179
179
  ```
180
180
 
181
181
  - Do not delete local instance data unless the user explicitly asks for destructive deletion.
@@ -189,13 +189,13 @@ npx --yes @n8n-as-code/n8n-manager tunnel stop <id>
189
189
  - Use `list` to inspect workflow IDs, file paths, and sync status.
190
190
 
191
191
  ```bash
192
- npx --yes n8nac list
193
- npx --yes n8nac pull <workflowId>
194
- npx --yes n8nac push <path-to-workflow.workflow.ts> --verify
192
+ npx --yes n8nac@next list
193
+ npx --yes n8nac@next pull <workflowId>
194
+ npx --yes n8nac@next push <path-to-workflow.workflow.ts> --verify
195
195
  ```
196
196
 
197
197
  - `push` requires the full workflow file path, either absolute or context-root-relative. Do not pass a bare filename.
198
- - For a new workflow, create the file inside the `workflowDir` returned by `env status --json`, then confirm it with `npx --yes n8nac list --local`.
198
+ - For a new workflow, create the file inside the `workflowDir` returned by `env status --json`, then confirm it with `npx --yes n8nac@next list --local`.
199
199
  - If push/pull reports a conflict, use explicit resolution commands. Do not overwrite remote changes blindly.
200
200
  - `pull` and conflict resolution operate on a single workflow ID.
201
201
  - `list` is the lightweight command that covers all workflows at once.
@@ -206,8 +206,8 @@ npx --yes n8nac push <path-to-workflow.workflow.ts> --verify
206
206
  If push or pull reports a conflict, stop and inspect the conflict. Use explicit resolution commands only after choosing the intended direction:
207
207
 
208
208
  ```bash
209
- npx --yes n8nac resolve <workflowId> --mode keep-current
210
- npx --yes n8nac resolve <workflowId> --mode keep-incoming
209
+ npx --yes n8nac@next resolve <workflowId> --mode keep-current
210
+ npx --yes n8nac@next resolve <workflowId> --mode keep-incoming
211
211
  ```
212
212
 
213
213
  - `keep-current` force-pushes the local version.
@@ -219,10 +219,10 @@ npx --yes n8nac resolve <workflowId> --mode keep-incoming
219
219
  Never guess n8n node parameters.
220
220
 
221
221
  ```bash
222
- npx --yes n8nac skills examples search "<workflow pattern>"
223
- npx --yes n8nac skills search "<node or capability>"
224
- npx --yes n8nac skills node-info <nodeName>
225
- npx --yes n8nac skills validate <workflow.workflow.ts>
222
+ npx --yes n8nac@next skills examples search "<workflow pattern>"
223
+ npx --yes n8nac@next skills search "<node or capability>"
224
+ npx --yes n8nac@next skills node-info <nodeName>
225
+ npx --yes n8nac@next skills validate <workflow.workflow.ts>
226
226
  ```
227
227
 
228
228
  - Use exact node `type` and valid `typeVersion` values from `node-info`.
@@ -237,19 +237,19 @@ npx --yes n8nac skills validate <workflow.workflow.ts>
237
237
  Use these commands instead of guessing:
238
238
 
239
239
  ```bash
240
- npx --yes n8nac skills search "<node or capability>"
241
- npx --yes n8nac skills node-info <nodeName>
242
- npx --yes n8nac skills node-schema <nodeName>
243
- npx --yes n8nac skills docs "<topic>"
244
- npx --yes n8nac skills guides "<topic>"
245
- npx --yes n8nac skills examples search "<workflow pattern>"
246
- npx --yes n8nac skills examples info <id>
247
- npx --yes n8nac skills examples download <id>
240
+ npx --yes n8nac@next skills search "<node or capability>"
241
+ npx --yes n8nac@next skills node-info <nodeName>
242
+ npx --yes n8nac@next skills node-schema <nodeName>
243
+ npx --yes n8nac@next skills docs "<topic>"
244
+ npx --yes n8nac@next skills guides "<topic>"
245
+ npx --yes n8nac@next skills examples search "<workflow pattern>"
246
+ npx --yes n8nac@next skills examples info <id>
247
+ npx --yes n8nac@next skills examples download <id>
248
248
  ```
249
249
 
250
250
  - Start with `examples search` when the user asks for a common automation pattern.
251
251
  - Use examples to learn patterns, not as authority over current node schemas.
252
- - If a command or flag is unfamiliar, run `npx --yes n8nac <subcommand> --help`; do not invent flags.
252
+ - If a command or flag is unfamiliar, run `npx --yes n8nac@next <subcommand> --help`; do not invent flags.
253
253
 
254
254
  ## Workflow Authoring Rules
255
255
 
@@ -389,15 +389,15 @@ defineRouting() {
389
389
  After pushing:
390
390
 
391
391
  ```bash
392
- npx --yes n8nac verify <workflowId>
393
- npx --yes n8nac test-plan <workflowId> --json
392
+ npx --yes n8nac@next verify <workflowId>
393
+ npx --yes n8nac@next test-plan <workflowId> --json
394
394
  ```
395
395
 
396
396
  For webhook, chat, or form workflows, prefer the production test sequence:
397
397
 
398
398
  ```bash
399
- npx --yes n8nac workflow activate <workflowId>
400
- npx --yes n8nac test <workflowId> --prod
399
+ npx --yes n8nac@next workflow activate <workflowId>
400
+ npx --yes n8nac@next test <workflowId> --prod
401
401
  ```
402
402
 
403
403
  - Class A configuration gaps require user/config action, not workflow rewrites.
@@ -407,7 +407,7 @@ npx --yes n8nac test <workflowId> --prod
407
407
 
408
408
  ## Workflow Presentation Contract
409
409
 
410
- `npx --yes n8nac workflow present` is the standard way to show a workflow to the user. It is v4-environment aware and part of the workflow authoring loop.
410
+ `npx --yes n8nac@next workflow present` is the standard way to show a workflow to the user. It is v4-environment aware and part of the workflow authoring loop.
411
411
 
412
412
  Run it whenever one of these is true:
413
413
 
@@ -417,7 +417,7 @@ Run it whenever one of these is true:
417
417
  - the user asks to show, open, present, display, or give the URL/link for a workflow.
418
418
 
419
419
  ```bash
420
- npx --yes n8nac workflow present <workflowId> --json
420
+ npx --yes n8nac@next workflow present <workflowId> --json
421
421
  ```
422
422
 
423
423
  Rules:
@@ -425,8 +425,8 @@ Rules:
425
425
  - Do not manually construct n8n workflow URLs.
426
426
  - Do not return an internal local n8n URL when a presentation URL is available.
427
427
  - Use the `url` returned by `workflow present --json` as the user-facing URL.
428
- - If you do not know the workflow ID, run `npx --yes n8nac list` first and select the matching workflow.
429
- - Do not call `npx --yes @n8n-as-code/n8n-manager presentWorkflowResult`; it is a legacy runtime command and is not workspace-environment aware.
428
+ - If you do not know the workflow ID, run `npx --yes n8nac@next list` first and select the matching workflow.
429
+ - Do not call `npx --yes @n8n-as-code/n8n-manager@next presentWorkflowResult`; it is a legacy runtime command and is not workspace-environment aware.
430
430
  - If `workflow present` fails, report the backend diagnostic and then provide the best direct n8n URL only as a fallback.
431
431
  - Do this before the final response when the task created, changed, pushed, ran, or explicitly asks to show a workflow.
432
432
 
@@ -440,18 +440,18 @@ For webhook, chat, or form workflows:
440
440
  4. Test with `--prod` by default.
441
441
 
442
442
  ```bash
443
- npx --yes n8nac push <path-to-workflow.workflow.ts> --verify
444
- npx --yes n8nac test-plan <workflowId> --json
445
- npx --yes n8nac workflow activate <workflowId>
446
- npx --yes n8nac test <workflowId> --prod
443
+ npx --yes n8nac@next push <path-to-workflow.workflow.ts> --verify
444
+ npx --yes n8nac@next test-plan <workflowId> --json
445
+ npx --yes n8nac@next workflow activate <workflowId>
446
+ npx --yes n8nac@next test <workflowId> --prod
447
447
  ```
448
448
 
449
- Use bare `npx --yes n8nac test <workflowId>` only when a test URL was intentionally armed in the n8n editor.
449
+ Use bare `npx --yes n8nac@next test <workflowId>` only when a test URL was intentionally armed in the n8n editor.
450
450
 
451
451
  For GET/HEAD webhooks that read from `$json.query`, prefer:
452
452
 
453
453
  ```bash
454
- npx --yes n8nac test <workflowId> --query '{"key":"value"}' --prod
454
+ npx --yes n8nac@next test <workflowId> --query '{"key":"value"}' --prod
455
455
  ```
456
456
 
457
457
  ## Execution Debugging
@@ -459,8 +459,8 @@ npx --yes n8nac test <workflowId> --query '{"key":"value"}' --prod
459
459
  If a webhook returns success but the workflow behavior is wrong, inspect executions instead of guessing:
460
460
 
461
461
  ```bash
462
- npx --yes n8nac execution list --workflow-id <workflowId> --limit 5 --json
463
- npx --yes n8nac execution get <executionId> --include-data --json
462
+ npx --yes n8nac@next execution list --workflow-id <workflowId> --limit 5 --json
463
+ npx --yes n8nac@next execution get <executionId> --include-data --json
464
464
  ```
465
465
 
466
466
  - A successful HTTP trigger only means n8n accepted the request.
@@ -472,11 +472,11 @@ npx --yes n8nac execution get <executionId> --include-data --json
472
472
  When a workflow is blocked by missing credentials, resolve the credential gap without rewriting unrelated workflow logic.
473
473
 
474
474
  ```bash
475
- npx --yes n8nac workflow credential-required <workflowId> --json
476
- npx --yes n8nac credential schema <type>
477
- npx --yes n8nac credential list --json
478
- npx --yes n8nac credential create --type <type> --name <name> --file cred.json --json
479
- npx --yes n8nac workflow activate <workflowId>
475
+ npx --yes n8nac@next workflow credential-required <workflowId> --json
476
+ npx --yes n8nac@next credential schema <type>
477
+ npx --yes n8nac@next credential list --json
478
+ npx --yes n8nac@next credential create --type <type> --name <name> --file cred.json --json
479
+ npx --yes n8nac@next workflow activate <workflowId>
480
480
  ```
481
481
 
482
482
  - `workflow credential-required` exits non-zero when at least one credential is missing. Treat that as a signal to act, not as a workflow-code failure.
@@ -500,12 +500,12 @@ For most workflow tasks:
500
500
  8. Push with `--verify`.
501
501
  9. Test if the workflow is HTTP-triggered.
502
502
  10. Inspect executions when behavior is unclear.
503
- 11. Present the final workflow link with `npx --yes n8nac workflow present <workflowId> --json`.
503
+ 11. Present the final workflow link with `npx --yes n8nac@next workflow present <workflowId> --json`.
504
504
 
505
505
  ## Response Discipline
506
506
 
507
507
  - Explain concrete actions and command results, not generic capability.
508
- - When the user asks for an URL or visual inspection of a workflow, run `npx --yes n8nac workflow present <workflowId> --json` instead of composing a URL manually.
508
+ - When the user asks for an URL or visual inspection of a workflow, run `npx --yes n8nac@next workflow present <workflowId> --json` instead of composing a URL manually.
509
509
  - If setup is missing, use `n8nac env ...` for workspace environments and `n8n-manager` only for managed local instances.
510
510
  - Do not ask for host/API key unless the user chooses a remote n8n environment.
511
511
  - Do not tell the user to run setup commands when you can run non-interactive commands yourself.