fix: drop /route from node type identifiers — category:name only

[pyramation]

Summary

Removes the optional /route suffix from node type identifiers per constructive-planning#1110. The canonical format is now category:name only — / is rejected.

Schema validation — both JSON schemas add "pattern": "^[^/]+$" on NodeDefinition.name/type:

# packages/types/graph.schema.json (NodeDefinition.type)
# packages/spec/graph.schema.json  (NodeDefinition.name)
+"pattern": "^[^/]+$",
+"description": "... Slash (/) is not allowed."

Docs — @fbp/types README Node Type Convention section:

-category:name[/route]
+category:name

-* **`/route`** (optional) — sub-route for multi-method containers
+The **slash** (`/`) character is **not allowed** in node type names.
+The name doubles as the HTTP route for HTTP-dispatched nodes.

Examples — all READMEs and skill references updated from slash-separated format to colon:

-type: 'js/math/add'       →  name: 'add'  (on NodeDefinition)
-type: 'js/math/add'       →  type: 'math:add'  (on Node instances)
-type: 'math/multiply'     →  type: 'math:multiply'
-email:postmaster/send     →  (removed)

Version — @fbp/types bumped 1.1.0 → 1.2.0.

Build passes, all 43 evaluator tests pass.

Link to Devin session: https://app.devin.ai/sessions/e57db035e5d44bf184515ceb100083c6
Requested by: @pyramation

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring