@orkestrel/scaffold 0.0.107 → 0.0.109

package/dist/host/agents/skills/orkestrel-parallel/references/harnesses.md

@@ -1,19 +0,0 @@
-# Harness mechanics
-
-Apply `.agents/orchestration.md` § Sessions and consultation before choosing a launch or continuation. Read the live tool descriptions; do not infer a wake, resume, or isolation capability from a tool name.
-
-| Harness     | Start work                                                                                                                                                                                          | Continue work                                                                                                                                                                                                 | Track                                                                                                                                                                                          |
-| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| T3          | Discover provider, model, options, and limits through `orchestrator_capabilities`. Use `delegate_task` for app-owned children, cross-provider work, requested model options, or worktree isolation. | Send an ordinary continuation to its `childThreadId` through `t3_thread_send`. Use `queue` for a separate request turn and `auto` for a reply or idle continuation. Use `steer` only for an in-flight change. | Retain the returned `taskId`, `childThreadId`, provider, model, and options and check them against the request. Retain each follow-up `taskId` beside, never in place of, the original result. |
-| Claude Code | Start a named custom role with `Agent` for work that needs continuation. Apply the Claude bridge's model rules.                                                                                     | Resume per `.claude/AGENTS.md` § Dispatch.                                                                                                                                                                    | Retain the stable agent id, not only its display name, and the parent session needed to recover it.                                                                                            |
-| Codex       | Use native collaboration when it supports the selected model and no model options are requested or inherited; otherwise use the T3 row. For a CLI bench, follow `.agents/transports/codex.md`.      | Use `followup_task` to resume an idle native agent. Use `send_message` to deliver information; it wakes no idle agent. For a bench, use its recorded CLI session's resume command.                            | Retain the native agent id or CLI session id separately from a long command's shell session and process ids.                                                                                   |
-| Cursor      | Follow `.agents/transports/cursor.md` for the read-only bench.                                                                                                                                      | Use only the continuation mechanism the installed transport supports.                                                                                                                                         | Do not assign a writer or runner lane without a demonstrated peer-message wake channel.                                                                                                        |
-
-- For every T3 independent review round, call `delegate_task` with a distinct `clientRequestId`. Reuse that id only when retrying the same round's uncertain launch. Supply the original brief, prior findings, responses, and unresolved objections. Never continue a review round through `t3_thread_send`.
-- For an ordinary T3 follow-up, use a stable `clientRequestId` and retain the returned task id. A completed task and a later turn in its child thread are distinct results. Read the intended task's status when completion is unclear.
-- Use `restart` only to interrupt an active turn and start it again, never as a resume. Create no ordinary top-level thread as a delegated lane.
-- A timeout on a parent wait cancels no child work. Before retrying a launch whose reply is missing or ambiguous, apply `.agents/orchestration.md` § Sessions and consultation.
-- Keep the idle runner available for queued requests. Wait on completion delivery; run no watcher agent and no file-poll loop. `SKILL.md` § Exchange requests and results owns recovery of a missing notice.
-- When a shell yields, retain and resume its tracked session until the terminal result arrives. Keep its output in the assigned artifact. Do not replace the command with a second launch.
-- After compaction or a harness restart, reconcile the retained roster against the live session and process state. When continuation is unsupported or unavailable, dispatch a successor brief that carries the prior evidence and unresolved work.
-- Keep provider-specific cache claims in evidence. For Claude behavior, verify the installed version against the official documentation; see the [subagent documentation](https://code.claude.com/docs/en/sub-agents), [team limitations](https://code.claude.com/docs/en/agent-teams), and [prompt-cache documentation](https://code.claude.com/docs/en/prompt-caching).