Skip to content

feat(workspaces): assemble an attachment's instructions from agent, shared and harness - #1061

Merged
LinuxDevil merged 1 commit into
mainfrom
fb-prod-assemble
Nov 12, 2026
Merged

LinuxDevil merged 1 commit into
mainfrom
fb-prod-assemble

Conversation

@LinuxDevil

Copy link
Copy Markdown
Owner

Why

The same agent must run under different harnesses without duplicating its definition. The harness is injected per run and never written into the agent (P1.6).

Changes

  • src/workspaces/runtime/assemble.ts: assembleInstructions (agent, ## Workspace rules, ## Task environment: <page>, ## Your role on this page, engine framing outside the harness hash) returning { text, sections, harnessPart, harnessPartHash, hash, explain() }; assembleMainInstructions; agentRunOptions (model, model hints, limits combined with min).
  • Re-exported from lousho/workspaces; api/workspaces.api.md updated.
  • Not done: the feat(workspaces): resolve harness profiles into an effective harness #1057 follow-up (one shared harness-layer reader) — the validator collects problems while the resolver throws, so it is not small or behaviour-identical.

Testing

  • npx vitest run src/workspaces/runtime/assemble.test.ts: 15 pass, including the ticket's six named tests.
  • npx vitest run src/workspaces: all tests pass; stores/dbSource suites cannot load locally (pg and @electric-sql/pglite missing in the shared node_modules).

🤖 Generated with Claude Code

LinuxDevil added a commit that referenced this pull request Nov 12, 2026
…n agent (#1061)

Fail on missing main-harness prose, file-style provenance labels, and no empty Pages block.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…n agent (#1061)

Fail on missing main-harness prose, file-style provenance labels, and no empty Pages block.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@LinuxDevil
LinuxDevil marked this pull request as ready for review November 12, 2026 08:11
@LinuxDevil
LinuxDevil merged commit 7442119 into main Nov 12, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant