fix: route case-insensitive worker messages
Some checks failed
tamq-ci / test (push) Failing after 5s

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a03397-4d51-7fd1-8ff2-946eb22ea2bc
This commit is contained in:
tegwick 2026-08-25 22:13:32 +02:00
parent fbb56f5981
commit cd73b954e9
14 changed files with 183 additions and 37 deletions

View file

@ -27,8 +27,9 @@ old address aliases and changes `pushy` so that submission requires the new
## Required protocol contract
The normalized line grammar is case-sensitive and recognized only at the start
of a logical line:
The normalized line keywords are case-insensitive and recognized only at the
start of logical content. A terminal program's conservative worker-output
gutter may precede worker content:
| Observed source | Line | Effect |
| --- | --- | --- |
@ -254,8 +255,10 @@ while a worker output replay can duplicate an operator message.
## Completion evidence
- The readable, case-sensitive `To:` parser is shared by attributed operator
input and normalized worker output. Durable provenance renders exactly as
- The readable, case-insensitive `To:` parser is shared by attributed operator
input and normalized worker output. Conservative full-screen worker-output
gutters are removed before worker parsing, while operator prompt gutters stay
inert. Durable provenance renders exactly as
`From:sender/o:` or `From:sender:`; `From:` and worker-output `Cmd:` lines are
inert. Legacy `@/#` routing, reply/composer code, and generated v1 shims were
removed from the active contract.