Confirm: "actor" in actors integration testing = ThreadCraft workspace itself #22

New issue

Closed

opened 2026-06-26 15:23:03 +00:00 by Mark · 1 comment

Mark commented

2026-06-26 15:23:03 +00:00

Owner

Decision required

Pick one:

(a) ThreadCraft is the actor. No separate harness. The actor flow is whatever the workspace's normal user path exercises. #20 stays as-is.
(b) Add a separate harness. File a new issue covering the harness, scope it (which scenarios, what pass criteria), and update #20 to reference it.

Once confirmed

Close this issue as completed. No code changes.

Mark/Kimi_Agent_Brother_10_Digitizing_App#20 — depends on this issue resolving first.

## Decision required Pick one: - (a) ThreadCraft is the actor. No separate harness. The actor flow is whatever the workspace's normal user path exercises. #20 stays as-is. - (b) Add a separate harness. File a new issue covering the harness, scope it (which scenarios, what pass criteria), and update #20 to reference it. ## Once confirmed Close this issue as `completed`. No code changes. ## Related - Mark/Kimi_Agent_Brother_10_Digitizing_App#20 — depends on this issue resolving first.

Mark added the

triage-approved

needs-decompose

labels

2026-06-26 15:23:39 +00:00

Mark commented

2026-06-26 15:23:40 +00:00

Author

Owner

Auto-triage: needs decompose

Marked triage-approved + needs-decompose. decompose-executor will pick this up and break it into implementable sub-issues.

## Auto-triage: needs decompose Marked `triage-approved` + `needs-decompose`. decompose-executor will pick this up and break it into implementable sub-issues.

Mark

2026-06-27 09:44:32 +00:00