Skip to content

[P2] Final agent demonstration: record an independent installed-release build/repair journey #302

Description

@wsdt

[P2] Final agent demonstration: record an independent installed-release build/repair journey

Review baseline and scope

Reviewed source: c9d32008e98d0e1711f47cb739f61c42376b884e on main, 22 September 2026.
Classification: PREREQUISITES + END-TO-END ACCEPTANCE.
Predecessors: #148.
This replaces their remaining work; closing a predecessor during backlog migration is not a claim that its original scope was completed.

Already delivered — do not rebuild

The issue has no progress comments. Its original prerequisites include the pilot, source-live repair and catalog-normalizer work, whose remaining gaps are retained separately. No qualifying complete independent final journey was established by this review; existence of the individual tools is not that evidence.

Remaining implementation / execution

  • After the relevant prerequisites are accepted, install the exact release into a clean external workspace and have an independent operator/agent complete the original multi-module build-and-repair journey.
  • Include an authentic failing test, repair, preserved sibling edits, interrupt/resume without repeated settled calls and independent oracle validation on the claimed backend.
  • Retain the exact package/release, transcript, edits, costs, outcomes and review evidence, separating preparation and replay from real provider execution.

Acceptance evidence

  • One reproducible end-to-end record exercises the shipped installed route rather than a repository-only fixture.
  • The original acceptance tasks and prerequisites are accounted for, with no fabricated independent review or demonstration outcome.
  • Any required live calls and artifact publication are separately approved.

Integration dependencies

These identify related acceptance work; safe independent implementation can proceed in parallel where the owning contracts permit it.

Boundaries

Do not recreate already delivered installer, transport, CLI or app infrastructure, or add optional model training/public-generic support as a new prerequisite. A task description is not an authorization for provider spend, signing, publication, remote deployment or a change to support policy. Preserve existing stable identities, explicit profile limits, source authority and non-vacuous acceptance gates.

Evidence and implementation entry points

Test results described above are retained repository evidence, not a fresh full test run performed by this backlog review. Re-run the owning gates for the implementation being accepted.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions