Skip to content
ContractSpec
Start here

Agents · Advanced · runnable fixture source

Review an agent's migration proposal

Follow a deterministic release migration through scoped subagents, digest-bound approval, and a draft PR receipt.

@lssm-tech/example.agent-application-foundation · Reference test source inspected · evidence as of 2026-10-27

Source context

Reference test source inspected · b67c376f

Pinned source links require repository access; publication and anonymous package availability were not checked for this example.

A fixture release removes billing.invoices.createLegacy and identifies two affected consumer files. The reference separates impact analysis, migration, and independent verification, then produces governed patch and draft-PR evidence without contacting GitHub.

What you will learn

  • Declare an agent application's instructions, tools, connections, sandbox, and evaluations as source.
  • Constrain analysis, migration, and verification responsibilities.
  • Bind approval to the proposed migration and preserve a reviewable draft outcome.

AN INTERACTIVE READING MAP

Walk through this example.

Step through the maintained source review, inspect its evidence boundaries, or assemble an adaptation packet.

SOURCE WALKTHROUGH

Read the operation in its authored order

01 / IN FOCUS

Compile the application

The source compiles the release-steward filesystem application and inspects required approvals for patching, draft PR creation, and selected delegation tools.

1 / 4

0 points in your packet

Walk through the source

  1. Compile the application. The source compiles the release-steward filesystem application and inspects required approvals for patching, draft PR creation, and selected delegation tools.
  2. Inspect the migration scope. The fixture calculates an immutable source digest and identifies the affected billing files. Subagent evidence records permitted tools and denied effects, including auto-merge.
  3. Bind approval and apply once. Tests assert that approval is bound to migration digests, changed material invalidates it, and the patch invocation occurs once even when replayed.
  4. Read the remaining qualification. The fixture's PR URL is under github.example.test, its PR is a draft, and autoMerge is false. Adapter and deployment composition results explicitly remain candidate with unresolved live requirements.

What this review establishes

  • The inspected source asserts separate subagent authority and digest-bound approval.
  • Tests assert one application invocation, replay evidence, a draft result, and no auto-merge.
  • Candidate readiness retains unresolved requirements for exact live environments.

Not established

  • A real patch applied to a user's repository or an actual GitHub PR.
  • Successful CI in a production repository; this fixture reports deterministic CI evidence.
  • Production isolation or deployment qualification merely because a topology composes.

Before adapting

  • Access to the inspected source repository and a checkout at the cited revision.
  • The repository's Bun workspace dependencies and required generated package exports. These instructions were inspected; the examples were not executed in this review.

Adapt the pattern

  • Begin with read-only impact analysis and a reviewable patch proposal.
  • Bind approval to exact source and patch material.
  • Keep merge authority and live-environment qualification explicit in the host application.
declaredStability
Not recorded
registry
Source package exists; absent from inspected generated registry
inlinePreview
Not registered
execution
Not rerun
production
Candidate