docs(skills): rename queue trigger type to durable:subscriber

Update skills and references to match PR #1422 rename:
- Trigger type 'queue' → 'durable:subscriber' in built-in type lists
- Updated in 4 SKILL.md files and 5 reference file comments

Unchanged (correct as-is):
- TriggerAction.Enqueue SDK API name
- IIITrigger::Queue Rust SDK enum
- queue_configs config key
- iii::queue::redrive function ID
- General 'queue' concept in descriptions

Author: rohitg00

skills/iii-custom-triggers/SKILL.md

@@ -18,7 +18,7 @@ Use the concepts below when they fit the task. Not every custom trigger needs al
 - The handler receives a **TriggerConfig** containing `id`, `function_id`, and `config`
 - When the external event fires, call `iii.trigger({ function_id, payload: event })` to invoke the registered function
 - **unregisterTriggerType** cleans up when the trigger type is no longer needed
-- Do not reuse built-in trigger type names: `http`, `cron`, `queue`, `state`, `stream`, `subscribe`
+- Do not reuse built-in trigger type names: `http`, `cron`, `durable:subscriber`, `state`, `stream`, `subscribe`
 
 ## Architecture
 

skills/iii-functions-and-triggers/SKILL.md

@@ -15,7 +15,7 @@ Comparable to: Serverless function runtimes, Lambda, Cloud Functions
 Use the concepts below when they fit the task. Not every worker needs all of them.
 
 - A **Function** is an async handler registered with a unique ID
-- A **Trigger** binds an event source to a function — types include http, queue, cron, state, stream, and subscribe
+- A **Trigger** binds an event source to a function — types include http, durable:subscriber, cron, state, stream, and subscribe
 - Functions invoke other functions via `trigger()` regardless of language or worker location
 - The engine handles serialization, routing, and delivery automatically
 - HTTP-invoked functions wrap external endpoints as callable function IDs

skills/iii-trigger-conditions/SKILL.md

@@ -20,7 +20,7 @@ Use the concepts below when they fit the task. Not every trigger needs a conditi
 - The engine calls the condition function before the handler; the handler runs only if `true`
 - Attach a condition to any trigger type via `condition_function_id` in the trigger config
 - The condition function receives the same event data as the handler would
-- Works with all trigger types: http, queue, cron, state, stream, subscribe
+- Works with all trigger types: http, durable:subscriber, cron, state, stream, subscribe
 
 ## Architecture
 
@@ -58,7 +58,7 @@ Code using this pattern commonly includes, when relevant:
 Use the adaptations below when they apply to the task.
 
 - Replace the condition logic with your business rules (threshold checks, role validation, feature flags)
-- Conditions work on all trigger types — use them on HTTP triggers for auth guards, on queue triggers for message filtering
+- Conditions work on all trigger types — use them on HTTP triggers for auth guards, on durable:subscriber triggers for message filtering
 - Keep condition functions lightweight and fast since they run on every trigger fire
 - Combine multiple business rules in a single condition function rather than chaining conditions
 - Condition functions can call `trigger()` internally to check state or other functions

skills/references/custom-triggers.js

@@ -3,7 +3,7 @@
  * Comparable to: Custom event adapters, webhook connectors, polling integrators
  *
  * Demonstrates how to define entirely new trigger types beyond the built-in
- * http, queue, cron, state, and subscribe triggers. A custom trigger type
+ * http, durable:subscriber, cron, state, and subscribe triggers. A custom trigger type
  * registers handler callbacks that the engine invokes when triggers of that
  * type are created or removed, letting you bridge any external event source
  * (webhooks, file-system watchers, pollers) into the iii function graph.

skills/references/custom-triggers.py

@@ -3,7 +3,7 @@
 Comparable to: Custom event adapters, webhook connectors, polling integrators
 
 Demonstrates how to define entirely new trigger types beyond the built-in
-http, queue, cron, state, and subscribe triggers. A custom trigger type
+http, durable:subscriber, cron, state, and subscribe triggers. A custom trigger type
 registers handler callbacks that the engine invokes when triggers of that
 type are created or removed, letting you bridge any external event source
 (webhooks, pollers) into the iii function graph.

skills/references/custom-triggers.rs

@@ -2,7 +2,7 @@
 /// Comparable to: Custom event adapters, webhook connectors, polling integrators
 ///
 /// Demonstrates how to define entirely new trigger types beyond the built-in
-/// http, queue, cron, state, and subscribe triggers. A custom trigger type
+/// http, durable:subscriber, cron, state, and subscribe triggers. A custom trigger type
 /// registers handler callbacks that the engine invokes when triggers of that
 /// type are created or removed, letting you bridge any external event source
 /// (webhooks, pollers) into the iii function graph.

skills/references/functions-and-triggers.js

@@ -3,7 +3,7 @@
  * Comparable to: Core primitives of iii
  *
  * Demonstrates every fundamental building block: registering functions,
- * binding triggers of each built-in type (http, queue, cron, state, subscribe),
+ * binding triggers of each built-in type (http, durable:subscriber, cron, state, subscribe),
  * cross-function invocation, fire-and-forget calls, and external HTTP-invoked
  * functions via HttpInvocationConfig.
  *

skills/references/functions-and-triggers.py

@@ -3,7 +3,7 @@
 Comparable to: Core primitives of iii
 
 Demonstrates every fundamental building block in Python: registering functions,
-binding triggers of each built-in type (http, queue, cron, state, subscribe),
+binding triggers of each built-in type (http, durable:subscriber, cron, state, subscribe),
 cross-function invocation, fire-and-forget calls, and external HTTP-invoked
 functions via HttpInvocationConfig.
 

skills/references/functions-and-triggers.rs

@@ -4,7 +4,7 @@
  *
  * Demonstrates every fundamental building block in Rust: registering functions
  * with the RegisterFunction builder, binding triggers of each built-in type
- * (http, queue, cron, state, subscribe), cross-function invocation, and
+ * (http, durable:subscriber, cron, state, subscribe), cross-function invocation, and
  * fire-and-forget calls.
  *
  * How-to references: