Testing plan: tiny-harness tui never asserts a participant, so it cannot send messages

Derived from bugfix.md and design.md. It names commands an agent will run, so review it like code.

Test matrix

#	Type	Applies?	Scope / what it proves	Where it runs
T1	Unit	yes	--participant parsing, tui_participant resolution, exit 2 on blank / undeterminable id, commands.tui passing the id on the --url path	uv run pytest tests/unit
T2	Integration (scenario)	yes	the real run_tui path sends a message under the asserted participant and reaches COMPLETED (regression, red before the fix); the embedded scenario takes the id from the command	uv run pytest tests/integration/embedded
T3	Contract (OpenAPI / GraphQL SDL)	n/a — no API surface changes; the public-API snapshots do not cover the CLI or run_tui
T4	End-to-end	n/a — the e2e suite drives the web renderer, which already asserts a participant; T2 plus T11 cover the TUI path end to end
T5	UI / visual	yes	the composer placeholder shows Enter to send as <participant>; the regression scenario asserts it on the live app	uv run pytest tests/integration/embedded
T6	Snapshot	yes	the TUI SVG snapshots change only by the composer's Enter to send as you; regenerated, and the diff reviewed to contain nothing else	uv run pytest tests/ui
T7	Performance / load	n/a — one string threaded through a call chain
T8	Security / abuse case	yes	abuse case 1 (no participant → refused) and 2 (asserted id gets no extra trust) still hold: the existing refusal and access tests pass unchanged; fail-closed CLI exits are in T1	uv run pytest tests/security tests/integration/a2a
T9	Accessibility	n/a — no UI change
T10	Migration / upgrade	n/a — additive optional flag; no stored state
T11	Manual exploratory	yes	the ticket's reproduction against the demo now replies	see Verification activities
T12	Full suite + static checks	yes	nothing else regressed; lint, format, types	uv run pre-commit run --all-files, uv run pytest

Scenarios & requirement trace

Row	Requirement(s)	Scenario / case
T1	R1.1, R1.3	parser accepts --participant; no flag → getpass.getuser()
T1	R1.4, R1.5	OSError from getuser and a blank flag → exit 2, stderr names --participant
T1	R1.8	josé, a\nb, a\rb, 名前, a tab, from the flag or the OS → None; --participant josé → exit 2
T1	R1.2, R1.6	commands.tui(url=…, participant="alice") → run_tui(url, participant="alice")
T2	R1.2, R1.6, R1.7, R2.1	Scenario: TUI sends a message under the asserted participant
T5	R1.7	the regression scenario reads Enter to send as alice from the composer
T2	R1.6, R2.2	Scenario: TUI hosts its own harness in embedded mode (stand-in takes the id from the command)
T8	abuse cases 1, 2	existing no participant asserted refusal and task-access tests
T11	R1, R2	ticket reproduction, remote and embedded

Verification environment

• Repositories: this repo only.
• Services / containers: none for T1/T6/T8. T2 starts the Temporal CLI dev server through WorkflowEnvironment.start_local (cached under the integration suite's CACHE, as in issue-17). T11 uses uv run python -m examples.demo --config examples/demo/config.embedded.toml in the background.
• Fixtures & data: the scripted model from tests/integration/embedded/conftest.py.
• Credentials: none. T11 in embedded mode needs no TEMPORAL_API_KEY. The demo's model uses whatever the demo config names; a scripted or local model is used if OPENAI_API_KEY is absent.
• Bring-up: uv sync --locked · Tear-down: stop the demo process by PID.
• If bring-up fails: record it below, leave the dependent activities unticked, and escalate on the PR.

Evidence plan

Row	Evidence	Path under evidence/
T1, T6, T8, T12	command, pass/fail counts, duration	unit.md, regression.md
T2	red run (before the fix) and green run, plus the scenario table	integration.md
T11	terminal transcript of the reproduction; an SVG screenshot of the TUI with a reply	manual-walkthrough.md, ui/tui-participant.svg

Verification activities

• [x] T1 — uv run pytest tests/unit
• [x] T2 — uv run pytest tests/integration/embedded (red recorded before the fix)
• [x] T5 — composer placeholder assertion inside the T2 regression scenario
• [x] T6 — uv run pytest tests/ui
• [x] T8 — uv run pytest tests/security tests/integration/a2a
• [x] T11 — ticket reproduction against the demo, remote (--url) and embedded
• [x] T12 — uv run pre-commit run --all-files and uv run pytest

Verification results

All activities ran on 2026-10-10. Every one passed. The CI suite's first run hit a pre-existing observability flake; its second run was clean.

Activity	Command / procedure	Outcome	Evidence
T1	uv run pytest tests/unit	261 passed at 7bb154d; red recorded first (collection error, tui_participant missing)	unit.md
T2	uv run pytest tests/integration/embedded	17 passed; red recorded first (InvalidParamsError('no participant asserted') through the real run_tui)	integration.md
T5	composer placeholder assertion in the T2 regression scenario	Enter to send as alice	integration.md
T6	uv run pytest tests/ui	9 passed, 4 snapshots regenerated; rendered text differs from main only in the composer	regression.md
T8	uv run pytest tests/security tests/integration/a2a	33 passed; the server-side refusal is unchanged	regression.md
T11	ticket reproduction against the demo: remote with the OS default and with --participant alice, a blank --participant, and embedded with --participant bob	replies on every path; blank flag and josé exit 2; no dev server left behind	manual-walkthrough.md, ui/tui-participant.svg
T12	uv run pre-commit run --all-files; CI's uv run pytest tests/integration tests/contract tests/security tests/ui	pre-commit clean; CI suite 114 passed on the second run (first run: 1 failure in the untouched o11y span test, which passed 3 of 3 on its own)	regression.md

Not executed: none. R1.4's real-world trigger (a process with no OS user name) was not staged on the host; the unit test that makes getpass.getuser raise OSError covers it.

Review comments