0 Fork 0

Files

T

Frank 8af40c402b chore(agent): commit the machine tier and the doctrine text the checkout was already running

Landing blocker for #61 and #63: the deployment checkout is 12 commits behind and
`merge --ff-only` refuses while tracked paths are dirty. Discard is not available here
(workspace policy: no `checkout`/`stash` on shared state), so the dirt is committed.

- `agent/APPEND_SYSTEM.md`: the point-of-use / one-work-log / PR-link doctrine, already
  byte-identical to `origin/main` (`cmp` against the trunk blob: no difference). No new
  prose — the commit exists so the trunk merge can proceed.
- `agent/config.yml` and `agent/managed-skills/**`: the machine-live tier the heartbeat
  owns (AGENTS.md § Live-sync tiers).

`ALLOW_SECRETS=1` was used, deliberately and after auditing the staged diff by hand: the
only credential-shaped strings in it are two copies of `AKIA0000000000000EXAMPLE` — the
inert all-zero AWS example id — and they appear inside the two skill pages that teach
that exact placeholder shape. This checkout is still running the pre-#61 hook; the merged
gate (value-scoped placeholder filter, `71601f7`) exempts this value, so the refusal
dies with this landing. No `--no-verify` was used: the gate ran and its verdict is
recorded here.

Refs #61

2026-10-21 01:44:51 -07:00

2.3 KiB

Raw Blame History

name, description

name	description
recover-subagent-yield-payload	Recover or salvage subagent deliverables: missing yields, payloads misrouted to xd://report_issue, and degraded TAKEN-list echoes.

Recovering subagent deliverables

Three failure modes seen with scout bulk-content tasks, in order of frequency.

1. Misrouted payload: scout wrote the deliverable to `xd://report_issue`

Symptom: yield summary says "delivered to xd://report_issue" instead of containing the content. That device is write-only (a bug-report channel); the response "Noted, thanks!" fooled the scout into thinking delivery worked.

Salvage path (often impossible — decide fast, ≤2 probes):

Transcript jsonl: ~/.omp/agent/sessions/*/*/Tan-*/Tan-*.jsonl (glob by agent id).
Streamed toolCall blocks store only partial arg fragments of big writes (arguments.content is chunked/empty; partialArgs holds deltas). Reassembly of a 140-line write across ~100 fragment rows has never worked — if content on the toolCall rows is empty or truncated, abandon salvage.
Only reliable in-file content: final assistant text blocks — walk rows for message.role=="assistant", content[].type=="text", filter lines against the delivery contract regex.

Prevention (put in scout prompts for bulk content): "Return the deliverable as plain lines in your FINAL OUTPUT TEXT. NEVER write it to xd://report_issue, files, or eval state."

2. Degenerate echo: scout returns the TAKEN/dedupe examples verbatim

Symptom: candidate lines repeat the "already used" examples given in the prompt, in looping blocks. Write off that batch entirely — do not re-prompt (it repeats). Cover the cluster inline yourself.

3. No yield at all (hung/force-stopped)

history://<agent-id> renders the transcript but compresses tool payloads to "1 line" — useless for payloads, fine for status. Try write agent://<id> with a one-line re-emit instruction ("end your turn by yielding the lines verbatim; do not re-research") exactly once; if the reply is garbage, abandon.

Rule of thumb for bulk creative content

Scouts add value for terminology research (search the universe's rank/offices vocabulary, 2-5 searches), not for drafting hundreds of lines — models echo, spin variants ("dune-mentat of the X" ×14), and misroute. Pattern: scout researches → parent drafts.

2.3 KiB Raw Blame History Unescape Escape