@n8n-as-code/skills 2.1.2-next.5 → 2.1.3-next.12

package/README.md

@@ -6,7 +6,7 @@ This package powers the shared n8n ontology behind `n8n-as-code`: searchable nod
 
 > **⚠️ BREAKING CHANGE (v0.16.0)**: Workflows are now generated and documented in **TypeScript format** (`.workflow.ts`) instead of JSON for better AI compatibility and readability.
 
-> **BREAKING CHANGE (v2.0.0)**: Generated agent context now assumes the environment model: use `n8nac env` for workspace environments, `n8nac workspace` for readiness/migration/upgrade, and `n8n-manager` for local managed instances. Legacy workspace-local instance libraries are no longer treated as the source of truth.
+> **BREAKING CHANGE (v2.0.0)**: Generated agent context now assumes the workspace environment model: use `n8nac env` for workspace environments, `n8nac workspace` for readiness and unified migration, and `n8n-manager` for local managed instances. Legacy workspace-local instance libraries are no longer treated as the source of truth.
 
 Documentation: [CLI guide](https://n8nascode.dev/docs/usage/cli/) · [n8n-manager guide](https://n8nascode.dev/docs/usage/n8n-manager/) · [Skills guide](https://n8nascode.dev/docs/usage/skills/)
 

package/dist/agent-skills/n8n-architect/SKILL.md

@@ -24,7 +24,8 @@ Use `{{N8NAC_CMD}}` as the primary interface. Use `{{N8N_MANAGER_CMD}}` only for
 {{N8NAC_CMD}} env status --json
 ```
 
-- Use the returned `workflowDir` for workflow files. Do not reconstruct it from `syncFolder`, `instanceIdentifier`, or `projectName`.
+- Use the returned `workflowDir` for workflow files. Treat it as an opaque backend-derived path that may contain generated or hashed segments.
+- `syncFolder` is only the user-configured sync root, not the workflow directory. Do not reconstruct `workflowDir` from `syncFolder`, environment name/id, `instanceIdentifier`, `instanceUserIdentifier`, `projectId`, or `projectName`.
 - Never write `n8nac-config.json`, `~/.n8n-manager`, or n8n-manager secret files by hand.
 
 ## Workspace Readiness
@@ -81,7 +82,7 @@ Migration is one user-facing command. Do not reason about internal migration pha
 10. Configure the environment with:
 
 ```bash
-{{N8NAC_CMD}} env add <name> --base-url <url> --sync-folder workflows/<name>
+{{N8NAC_CMD}} env add <name> --base-url <url> --sync-folder workflows
 {{N8NAC_CMD}} env auth set <name> --api-key-stdin
 {{N8NAC_CMD}} env use <name>
 ```
@@ -89,7 +90,7 @@ Migration is one user-facing command. Do not reason about internal migration pha
 For a managed local instance:
 
 ```bash
-{{N8NAC_CMD}} env add Local --managed-instance <id> --sync-folder workflows/local
+{{N8NAC_CMD}} env add Local --managed-instance <id> --sync-folder workflows
 {{N8NAC_CMD}} env use Local
 ```
 
@@ -102,7 +103,7 @@ Use `{{N8NAC_CMD}} env ...` for workspace environments, remote URLs, active envi
 ```bash
 {{N8NAC_CMD}} env status --json
 {{N8NAC_CMD}} env list
-{{N8NAC_CMD}} env add <name> --base-url <url> --sync-folder workflows/<name>
+{{N8NAC_CMD}} env add <name> --base-url <url> --sync-folder workflows
 {{N8NAC_CMD}} env auth set <name> --api-key-stdin
 {{N8NAC_CMD}} env use <name>
 ```
@@ -116,7 +117,7 @@ Use `{{N8NAC_CMD}} env ...` for workspace environments, remote URLs, active envi
 Attach a managed local instance to the workspace with `{{N8NAC_CMD}} env ...`:
 
 ```bash
-{{N8NAC_CMD}} env add Local --managed-instance <id> --sync-folder workflows/local
+{{N8NAC_CMD}} env add Local --managed-instance <id> --sync-folder workflows
 {{N8NAC_CMD}} env use Local
 ```
 

package/dist/assets/n8n-credentials-ontology.json

@@ -1,5 +1,5 @@
 {
-  "generatedAt": "2026-05-12T15:12:07.779Z",
+  "generatedAt": "2026-05-13T15:02:35.878Z",
   "n8nVersion": "unknown",
   "sourceFileCount": 428,
   "scanDirectories": [