c8ctl-plugin-nano 1.61.1 → 1.62.0

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.
package/README.md CHANGED
@@ -236,11 +236,14 @@ How it works and why it needs no wiring:
236
236
  agent jobs at all, it and the app are already on the same engine, so *what
237
237
  agent job types exist* is answerable from that engine alone — **no cross-machine
238
238
  app discovery, no app enrol endpoint, no channel connection**.
239
- - **Agent-task header filter.** Not every service task is an agent task —
239
+ - **Agent-task marker filter.** Not every service task is an agent task —
240
240
  connectors and record-keepers (e.g. `pr.record-plan`) are plain workers.
241
- `--auto` keeps only leaves whose service task carries an
242
- **`io.nanobpm.agentTask.`** task header (e.g. `senior:plan` carries
243
- `io.nanobpm.agentTask.task.prompt`; a record-keeper does not).
241
+ `--auto` keeps only leaves whose service task carries the single-convention
242
+ external-agent marker **`<zeebe:agentDefinition agentType="external" />`** (the
243
+ same marker every external agent task already declares). A task can **opt out**
244
+ of `--auto` with `<zeebe:property name="io.nanobpm.agentTask.autoSubscribe"
245
+ value="false" />` — it is then served only by explicit `--job-type`/profile
246
+ subscription.
244
247
  - **One poller per agent job type, reconciled on change.** It opens one poller
245
248
  per agent job type and re-reads the engine periodically, adding pollers for
246
249
  newly deployed agent processes and draining pollers for undeployed ones — the