@codyswann/lisa 2.317.0 → 2.317.2
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/dist/core/upstream-evidence-manifest.js +1 -1
- package/package.json +1 -1
- package/plugins/lisa/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa/.codex-plugin/skills/lisa-remote-dispatch/SKILL.md +8 -1
- package/plugins/lisa/skills/lisa-remote-dispatch/SKILL.md +8 -1
- package/plugins/lisa-agy/plugin.json +1 -1
- package/plugins/lisa-agy/skills/lisa-remote-dispatch/SKILL.md +8 -1
- package/plugins/lisa-cdk/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-cdk/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-cdk-agy/plugin.json +1 -1
- package/plugins/lisa-cdk-copilot/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-cdk-cursor/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-copilot/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-copilot/skills/lisa-remote-dispatch/SKILL.md +8 -1
- package/plugins/lisa-cursor/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-cursor/skills/lisa-remote-dispatch/SKILL.md +8 -1
- package/plugins/lisa-expo/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-expo/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-expo-agy/plugin.json +1 -1
- package/plugins/lisa-expo-copilot/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-expo-cursor/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-harper-fabric/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-harper-fabric/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-harper-fabric-agy/plugin.json +1 -1
- package/plugins/lisa-harper-fabric-copilot/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-harper-fabric-cursor/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-nestjs/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-nestjs/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-nestjs-agy/plugin.json +1 -1
- package/plugins/lisa-nestjs-copilot/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-nestjs-cursor/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-openclaw/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-openclaw/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-openclaw-agy/plugin.json +1 -1
- package/plugins/lisa-openclaw-copilot/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-openclaw-cursor/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-phaser/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-phaser/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-phaser-agy/plugin.json +1 -1
- package/plugins/lisa-phaser-copilot/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-phaser-cursor/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-rails/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-rails/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-rails-agy/plugin.json +1 -1
- package/plugins/lisa-rails-copilot/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-rails-cursor/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-typescript/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-typescript/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-typescript-agy/plugin.json +1 -1
- package/plugins/lisa-typescript-copilot/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-typescript-cursor/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-wiki/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-wiki/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-wiki-agy/plugin.json +1 -1
- package/plugins/lisa-wiki-copilot/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-wiki-cursor/.claude-plugin/plugin.json +1 -1
- package/plugins/src/base/skills/lisa-remote-dispatch/SKILL.md +8 -1
|
@@ -526,7 +526,7 @@ export const UPSTREAM_EVIDENCE_MANIFEST = Object.freeze({
|
|
|
526
526
|
"plugins/src/base/skills/lisa-qa-queue/SKILL.md": "1d5f009f60004bf75b5d79bca370096ce40e1d41d585dc8afd4389f21bba84ae",
|
|
527
527
|
"plugins/src/base/skills/lisa-quality-review/SKILL.md": "17ba45f4c4b7877c0b0c9a3c1cc1cb9e18c642ead74ff7263698d8034d3241da",
|
|
528
528
|
"plugins/src/base/skills/lisa-queue-status/SKILL.md": "87c6d34d0511d4afd812d1af3fee80fa3b7aa47db8449760b12f2699fedc1d78",
|
|
529
|
-
"plugins/src/base/skills/lisa-remote-dispatch/SKILL.md": "
|
|
529
|
+
"plugins/src/base/skills/lisa-remote-dispatch/SKILL.md": "2cc999d2c3b61b10aabb849e0833fd58edb444c5013c05108dd58e5d7d60c4ba",
|
|
530
530
|
"plugins/src/base/skills/lisa-remote-dispatch/scripts/dispatch.mjs": "3bf6c019de34a53a1c84b131ffeb9702441e8c1c7c1794f522f97c0de5ee5ce4",
|
|
531
531
|
"plugins/src/base/skills/lisa-repair-intake/SKILL.md": "4f85ac1381631e9f250d9cf3239baba633ae0df9ba1959f8835ed662592e2d77",
|
|
532
532
|
"plugins/src/base/skills/lisa-reproduce-bug/SKILL.md": "4d460993fac6021219ca23eee29b1b9afa7c37479dddc662b2fcfaca510edd68",
|
package/package.json
CHANGED
|
@@ -115,7 +115,7 @@
|
|
|
115
115
|
"brace-expansion": ">=5.0.8"
|
|
116
116
|
},
|
|
117
117
|
"name": "@codyswann/lisa",
|
|
118
|
-
"version": "2.317.
|
|
118
|
+
"version": "2.317.2",
|
|
119
119
|
"description": "Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects",
|
|
120
120
|
"main": "dist/index.js",
|
|
121
121
|
"exports": {
|
|
@@ -55,6 +55,11 @@ It does **not** poll, wait, or hold anything open. The operator's machine is a l
|
|
|
55
55
|
|
|
56
56
|
**A dispatch with no captured task identifier is a failed dispatch**, even when the command exited zero. The identifier is the only durable handle on work that outlives this process; an untracked remote task is worse than none, because nothing can reconcile it and a retry would duplicate it.
|
|
57
57
|
|
|
58
|
+
Two things about the CLI surface, both verified live on 2026-08-01:
|
|
59
|
+
|
|
60
|
+
- `codex cloud exec` prints **only the task URL** on success — there is no separate identifier line to parse. The identifier must be extracted from that URL.
|
|
61
|
+
- `codex cloud status` returns status, environment label, and a diff summary — **not the agent's text reply**. So a task cannot report a result back through the CLI, only through an artifact. Reconcile through durable objects (the PR, the diff, the external record), never through what the agent said.
|
|
62
|
+
|
|
58
63
|
## Surface options
|
|
59
64
|
|
|
60
65
|
```json
|
|
@@ -75,7 +80,9 @@ It does **not** poll, wait, or hold anything open. The operator's machine is a l
|
|
|
75
80
|
|
|
76
81
|
**`branch` is always passed explicitly.** `codex cloud exec` defaults to the *current* branch, and a dispatcher's incidental checkout state must never decide where work runs.
|
|
77
82
|
|
|
78
|
-
**`model` goes through `-c`,** because the subcommand has no `--model` flag; the CLI's own help documents `-c model="..."`. Model is vendor-specific while `executionEnv` is routing, so it is scoped under the surface rather than hung off the top level.
|
|
83
|
+
**`model` goes through `-c`,** because the subcommand has no `--model` flag; the CLI's own help documents `-c model="..."`. Model is vendor-specific while `executionEnv` is routing, so it is scoped under the surface rather than hung off the top level.
|
|
84
|
+
|
|
85
|
+
**But do not rely on it to select a Codex Cloud task's model.** Verified by live dispatch on 2026-08-01: `-c model="not-a-real-model-probe-xyz"` was accepted without local validation, submitted, and the task then ran to `READY` successfully. Had the invalid value governed remote execution, the task could not have run. Whether the override fails to propagate or propagates and is ignored is not established — the operational rule is the same either way. **Set the model on the environment itself; treat this field as a hint the surface may disregard.**
|
|
79
86
|
|
|
80
87
|
Do not invent an abstract tier (`fast` / `deep`) mapped per vendor. That produces confidently wrong mappings when a second surface arrives with an unrelated model lineup. A raw string scoped to the surface that owns it is honest.
|
|
81
88
|
|
|
@@ -55,6 +55,11 @@ It does **not** poll, wait, or hold anything open. The operator's machine is a l
|
|
|
55
55
|
|
|
56
56
|
**A dispatch with no captured task identifier is a failed dispatch**, even when the command exited zero. The identifier is the only durable handle on work that outlives this process; an untracked remote task is worse than none, because nothing can reconcile it and a retry would duplicate it.
|
|
57
57
|
|
|
58
|
+
Two things about the CLI surface, both verified live on 2026-08-01:
|
|
59
|
+
|
|
60
|
+
- `codex cloud exec` prints **only the task URL** on success — there is no separate identifier line to parse. The identifier must be extracted from that URL.
|
|
61
|
+
- `codex cloud status` returns status, environment label, and a diff summary — **not the agent's text reply**. So a task cannot report a result back through the CLI, only through an artifact. Reconcile through durable objects (the PR, the diff, the external record), never through what the agent said.
|
|
62
|
+
|
|
58
63
|
## Surface options
|
|
59
64
|
|
|
60
65
|
```json
|
|
@@ -75,7 +80,9 @@ It does **not** poll, wait, or hold anything open. The operator's machine is a l
|
|
|
75
80
|
|
|
76
81
|
**`branch` is always passed explicitly.** `codex cloud exec` defaults to the *current* branch, and a dispatcher's incidental checkout state must never decide where work runs.
|
|
77
82
|
|
|
78
|
-
**`model` goes through `-c`,** because the subcommand has no `--model` flag; the CLI's own help documents `-c model="..."`. Model is vendor-specific while `executionEnv` is routing, so it is scoped under the surface rather than hung off the top level.
|
|
83
|
+
**`model` goes through `-c`,** because the subcommand has no `--model` flag; the CLI's own help documents `-c model="..."`. Model is vendor-specific while `executionEnv` is routing, so it is scoped under the surface rather than hung off the top level.
|
|
84
|
+
|
|
85
|
+
**But do not rely on it to select a Codex Cloud task's model.** Verified by live dispatch on 2026-08-01: `-c model="not-a-real-model-probe-xyz"` was accepted without local validation, submitted, and the task then ran to `READY` successfully. Had the invalid value governed remote execution, the task could not have run. Whether the override fails to propagate or propagates and is ignored is not established — the operational rule is the same either way. **Set the model on the environment itself; treat this field as a hint the surface may disregard.**
|
|
79
86
|
|
|
80
87
|
Do not invent an abstract tier (`fast` / `deep`) mapped per vendor. That produces confidently wrong mappings when a second surface arrives with an unrelated model lineup. A raw string scoped to the surface that owns it is honest.
|
|
81
88
|
|
|
@@ -55,6 +55,11 @@ It does **not** poll, wait, or hold anything open. The operator's machine is a l
|
|
|
55
55
|
|
|
56
56
|
**A dispatch with no captured task identifier is a failed dispatch**, even when the command exited zero. The identifier is the only durable handle on work that outlives this process; an untracked remote task is worse than none, because nothing can reconcile it and a retry would duplicate it.
|
|
57
57
|
|
|
58
|
+
Two things about the CLI surface, both verified live on 2026-08-01:
|
|
59
|
+
|
|
60
|
+
- `codex cloud exec` prints **only the task URL** on success — there is no separate identifier line to parse. The identifier must be extracted from that URL.
|
|
61
|
+
- `codex cloud status` returns status, environment label, and a diff summary — **not the agent's text reply**. So a task cannot report a result back through the CLI, only through an artifact. Reconcile through durable objects (the PR, the diff, the external record), never through what the agent said.
|
|
62
|
+
|
|
58
63
|
## Surface options
|
|
59
64
|
|
|
60
65
|
```json
|
|
@@ -75,7 +80,9 @@ It does **not** poll, wait, or hold anything open. The operator's machine is a l
|
|
|
75
80
|
|
|
76
81
|
**`branch` is always passed explicitly.** `codex cloud exec` defaults to the *current* branch, and a dispatcher's incidental checkout state must never decide where work runs.
|
|
77
82
|
|
|
78
|
-
**`model` goes through `-c`,** because the subcommand has no `--model` flag; the CLI's own help documents `-c model="..."`. Model is vendor-specific while `executionEnv` is routing, so it is scoped under the surface rather than hung off the top level.
|
|
83
|
+
**`model` goes through `-c`,** because the subcommand has no `--model` flag; the CLI's own help documents `-c model="..."`. Model is vendor-specific while `executionEnv` is routing, so it is scoped under the surface rather than hung off the top level.
|
|
84
|
+
|
|
85
|
+
**But do not rely on it to select a Codex Cloud task's model.** Verified by live dispatch on 2026-08-01: `-c model="not-a-real-model-probe-xyz"` was accepted without local validation, submitted, and the task then ran to `READY` successfully. Had the invalid value governed remote execution, the task could not have run. Whether the override fails to propagate or propagates and is ignored is not established — the operational rule is the same either way. **Set the model on the environment itself; treat this field as a hint the surface may disregard.**
|
|
79
86
|
|
|
80
87
|
Do not invent an abstract tier (`fast` / `deep`) mapped per vendor. That produces confidently wrong mappings when a second surface arrives with an unrelated model lineup. A raw string scoped to the surface that owns it is honest.
|
|
81
88
|
|
|
@@ -55,6 +55,11 @@ It does **not** poll, wait, or hold anything open. The operator's machine is a l
|
|
|
55
55
|
|
|
56
56
|
**A dispatch with no captured task identifier is a failed dispatch**, even when the command exited zero. The identifier is the only durable handle on work that outlives this process; an untracked remote task is worse than none, because nothing can reconcile it and a retry would duplicate it.
|
|
57
57
|
|
|
58
|
+
Two things about the CLI surface, both verified live on 2026-08-01:
|
|
59
|
+
|
|
60
|
+
- `codex cloud exec` prints **only the task URL** on success — there is no separate identifier line to parse. The identifier must be extracted from that URL.
|
|
61
|
+
- `codex cloud status` returns status, environment label, and a diff summary — **not the agent's text reply**. So a task cannot report a result back through the CLI, only through an artifact. Reconcile through durable objects (the PR, the diff, the external record), never through what the agent said.
|
|
62
|
+
|
|
58
63
|
## Surface options
|
|
59
64
|
|
|
60
65
|
```json
|
|
@@ -75,7 +80,9 @@ It does **not** poll, wait, or hold anything open. The operator's machine is a l
|
|
|
75
80
|
|
|
76
81
|
**`branch` is always passed explicitly.** `codex cloud exec` defaults to the *current* branch, and a dispatcher's incidental checkout state must never decide where work runs.
|
|
77
82
|
|
|
78
|
-
**`model` goes through `-c`,** because the subcommand has no `--model` flag; the CLI's own help documents `-c model="..."`. Model is vendor-specific while `executionEnv` is routing, so it is scoped under the surface rather than hung off the top level.
|
|
83
|
+
**`model` goes through `-c`,** because the subcommand has no `--model` flag; the CLI's own help documents `-c model="..."`. Model is vendor-specific while `executionEnv` is routing, so it is scoped under the surface rather than hung off the top level.
|
|
84
|
+
|
|
85
|
+
**But do not rely on it to select a Codex Cloud task's model.** Verified by live dispatch on 2026-08-01: `-c model="not-a-real-model-probe-xyz"` was accepted without local validation, submitted, and the task then ran to `READY` successfully. Had the invalid value governed remote execution, the task could not have run. Whether the override fails to propagate or propagates and is ignored is not established — the operational rule is the same either way. **Set the model on the environment itself; treat this field as a hint the surface may disregard.**
|
|
79
86
|
|
|
80
87
|
Do not invent an abstract tier (`fast` / `deep`) mapped per vendor. That produces confidently wrong mappings when a second surface arrives with an unrelated model lineup. A raw string scoped to the surface that owns it is honest.
|
|
81
88
|
|
|
@@ -55,6 +55,11 @@ It does **not** poll, wait, or hold anything open. The operator's machine is a l
|
|
|
55
55
|
|
|
56
56
|
**A dispatch with no captured task identifier is a failed dispatch**, even when the command exited zero. The identifier is the only durable handle on work that outlives this process; an untracked remote task is worse than none, because nothing can reconcile it and a retry would duplicate it.
|
|
57
57
|
|
|
58
|
+
Two things about the CLI surface, both verified live on 2026-08-01:
|
|
59
|
+
|
|
60
|
+
- `codex cloud exec` prints **only the task URL** on success — there is no separate identifier line to parse. The identifier must be extracted from that URL.
|
|
61
|
+
- `codex cloud status` returns status, environment label, and a diff summary — **not the agent's text reply**. So a task cannot report a result back through the CLI, only through an artifact. Reconcile through durable objects (the PR, the diff, the external record), never through what the agent said.
|
|
62
|
+
|
|
58
63
|
## Surface options
|
|
59
64
|
|
|
60
65
|
```json
|
|
@@ -75,7 +80,9 @@ It does **not** poll, wait, or hold anything open. The operator's machine is a l
|
|
|
75
80
|
|
|
76
81
|
**`branch` is always passed explicitly.** `codex cloud exec` defaults to the *current* branch, and a dispatcher's incidental checkout state must never decide where work runs.
|
|
77
82
|
|
|
78
|
-
**`model` goes through `-c`,** because the subcommand has no `--model` flag; the CLI's own help documents `-c model="..."`. Model is vendor-specific while `executionEnv` is routing, so it is scoped under the surface rather than hung off the top level.
|
|
83
|
+
**`model` goes through `-c`,** because the subcommand has no `--model` flag; the CLI's own help documents `-c model="..."`. Model is vendor-specific while `executionEnv` is routing, so it is scoped under the surface rather than hung off the top level.
|
|
84
|
+
|
|
85
|
+
**But do not rely on it to select a Codex Cloud task's model.** Verified by live dispatch on 2026-08-01: `-c model="not-a-real-model-probe-xyz"` was accepted without local validation, submitted, and the task then ran to `READY` successfully. Had the invalid value governed remote execution, the task could not have run. Whether the override fails to propagate or propagates and is ignored is not established — the operational rule is the same either way. **Set the model on the environment itself; treat this field as a hint the surface may disregard.**
|
|
79
86
|
|
|
80
87
|
Do not invent an abstract tier (`fast` / `deep`) mapped per vendor. That produces confidently wrong mappings when a second surface arrives with an unrelated model lineup. A raw string scoped to the surface that owns it is honest.
|
|
81
88
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "lisa-openclaw",
|
|
3
|
-
"version": "2.317.
|
|
3
|
+
"version": "2.317.2",
|
|
4
4
|
"description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
|
|
5
5
|
"author": {
|
|
6
6
|
"name": "Cody Swann"
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "lisa-openclaw",
|
|
3
|
-
"version": "2.317.
|
|
3
|
+
"version": "2.317.2",
|
|
4
4
|
"description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, across Claude and Codex.",
|
|
5
5
|
"author": {
|
|
6
6
|
"name": "Cody Swann"
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "lisa-openclaw",
|
|
3
|
-
"version": "2.317.
|
|
3
|
+
"version": "2.317.2",
|
|
4
4
|
"description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
|
|
5
5
|
"author": {
|
|
6
6
|
"name": "Cody Swann"
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "lisa-openclaw",
|
|
3
|
-
"version": "2.317.
|
|
3
|
+
"version": "2.317.2",
|
|
4
4
|
"description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
|
|
5
5
|
"author": {
|
|
6
6
|
"name": "Cody Swann"
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "lisa-openclaw",
|
|
3
|
-
"version": "2.317.
|
|
3
|
+
"version": "2.317.2",
|
|
4
4
|
"description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
|
|
5
5
|
"author": {
|
|
6
6
|
"name": "Cody Swann"
|
|
@@ -55,6 +55,11 @@ It does **not** poll, wait, or hold anything open. The operator's machine is a l
|
|
|
55
55
|
|
|
56
56
|
**A dispatch with no captured task identifier is a failed dispatch**, even when the command exited zero. The identifier is the only durable handle on work that outlives this process; an untracked remote task is worse than none, because nothing can reconcile it and a retry would duplicate it.
|
|
57
57
|
|
|
58
|
+
Two things about the CLI surface, both verified live on 2026-08-01:
|
|
59
|
+
|
|
60
|
+
- `codex cloud exec` prints **only the task URL** on success — there is no separate identifier line to parse. The identifier must be extracted from that URL.
|
|
61
|
+
- `codex cloud status` returns status, environment label, and a diff summary — **not the agent's text reply**. So a task cannot report a result back through the CLI, only through an artifact. Reconcile through durable objects (the PR, the diff, the external record), never through what the agent said.
|
|
62
|
+
|
|
58
63
|
## Surface options
|
|
59
64
|
|
|
60
65
|
```json
|
|
@@ -75,7 +80,9 @@ It does **not** poll, wait, or hold anything open. The operator's machine is a l
|
|
|
75
80
|
|
|
76
81
|
**`branch` is always passed explicitly.** `codex cloud exec` defaults to the *current* branch, and a dispatcher's incidental checkout state must never decide where work runs.
|
|
77
82
|
|
|
78
|
-
**`model` goes through `-c`,** because the subcommand has no `--model` flag; the CLI's own help documents `-c model="..."`. Model is vendor-specific while `executionEnv` is routing, so it is scoped under the surface rather than hung off the top level.
|
|
83
|
+
**`model` goes through `-c`,** because the subcommand has no `--model` flag; the CLI's own help documents `-c model="..."`. Model is vendor-specific while `executionEnv` is routing, so it is scoped under the surface rather than hung off the top level.
|
|
84
|
+
|
|
85
|
+
**But do not rely on it to select a Codex Cloud task's model.** Verified by live dispatch on 2026-08-01: `-c model="not-a-real-model-probe-xyz"` was accepted without local validation, submitted, and the task then ran to `READY` successfully. Had the invalid value governed remote execution, the task could not have run. Whether the override fails to propagate or propagates and is ignored is not established — the operational rule is the same either way. **Set the model on the environment itself; treat this field as a hint the surface may disregard.**
|
|
79
86
|
|
|
80
87
|
Do not invent an abstract tier (`fast` / `deep`) mapped per vendor. That produces confidently wrong mappings when a second surface arrives with an unrelated model lineup. A raw string scoped to the surface that owns it is honest.
|
|
81
88
|
|