@ghl-ai/aw 0.1.43-beta.1 → 0.1.43

package/ecc.mjs

@@ -12,7 +12,7 @@ import { applyStoredStartupPreferences } from "./startup.mjs";
 
 const AW_ECC_REPO_SSH = "git@github.com:shreyansh-ghl/aw-ecc.git";
 const AW_ECC_REPO_HTTPS = "https://github.com/shreyansh-ghl/aw-ecc.git";
-export const AW_ECC_TAG = "v1.4.42";
+export const AW_ECC_TAG = "v1.4.43";
 
 const MARKETPLACE_NAME = "aw-marketplace";
 const PLUGIN_KEY = `aw@${MARKETPLACE_NAME}`;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ghl-ai/aw",
-  "version": "0.1.43-beta.1",
+  "version": "0.1.43",
   "description": "Agentic Workspace CLI — pull, push & manage agents, skills and commands from the registry",
   "type": "module",
   "bin": {

package/render-rules.mjs

@@ -344,6 +344,8 @@ For every non-trivial request, execute these steps in order before any substanti
 2. **Select route** — using the decision tree below, pick the smallest correct AW route.
 
 3. **Read the stage skill** — you MUST Read the matching skill file before responding:
+   - /aw-adk → Read aw-adk/SKILL.md
+   - /aw-publish → Read aw-publish/SKILL.md
    - /aw-plan → Read aw-plan/SKILL.md
    - /aw-build → Read aw-build/SKILL.md
    - /aw-investigate → Read aw-investigate/SKILL.md
@@ -362,21 +364,31 @@ Stating a route without Reading the skill file is NOT compliance.
 ## Route Decision Tree
 
 \`\`\`text
-Does an approved plan/spec already exist for this exact work?
-├── NO → Is the request about a bug, alert, or unclear failure?
-│         ├── YES → /aw-investigate
-│         └── NO  → /aw-plan  ← DEFAULT for anything new
-└── YES → Is the work implemented and needs testing/review?
-          ├── YES → /aw-test or /aw-review
-          └── NO  → Is this a deploy or release action?
-                    ├── YES → /aw-deploy or /aw-ship
-                    └── NO  → /aw-build
+Is the user authoring/editing a CASRE artifact (command, agent, skill, rule, eval) in .aw_registry/?
+├── YES → /aw-adk
+└── NO  → Is the user pushing registry content (.aw_registry/ or .aw_rules/) to remote platform-docs?
+          ├── YES → /aw-publish
+          └── NO  → Does an approved plan/spec already exist for this exact work?
+                    ├── NO → Is the request about a bug, alert, or unclear failure?
+                    │         ├── YES → /aw-investigate
+                    │         └── NO  → /aw-plan  ← DEFAULT for anything new
+                    └── YES → Is the work implemented and needs testing/review?
+                              ├── YES → /aw-test or /aw-review
+                              └── NO  → Is this a deploy or release action?
+                                        ├── YES → /aw-deploy or /aw-ship
+                                        └── NO  → /aw-build
 \`\`\`
 
+**ADK triggers**: "create an agent/skill/command/rule/eval", "score my skill", "audit all agents", "ADK", "developer kit", "fix lint errors" on registry artifacts.
+
+**Publish triggers**: "push this agent/skill/rule to the registry", "publish registry changes", "sync to platform-docs", "aw push", "aw push-rules". NOT regular git push, app PRs, or deploys.
+
 **Plan-first rule**: New endpoints, services, schemas, features, architecture changes, and integrations ALL go through /aw-plan first. /aw-build requires an approved plan or a mechanical change.
 
 ## Default Assumptions
 
+- /aw-adk → create, improve, fix, score, audit, or health-check CASRE artifacts in .aw_registry/.
+- /aw-publish → dry-run first, show diff, confirm, then real push. Never auto-publish.
 - /aw-plan → write file artifacts under .aw_docs/features/<slug>/ unless user says "chat only".
 - /aw-build → code changes with tests.
 - /aw-investigate → reproduction + root cause evidence.