Skip to content

feat(web): launch provider integration work from Factory - #94

Open
Nurozen wants to merge 2 commits into
mainfrom
stave/lecturn-factory/lecturn
Open

Nurozen wants to merge 2 commits into
mainfrom
stave/lecturn-factory/lecturn

Conversation

@Nurozen

@Nurozen Nurozen commented Sep 29, 2026 •

Copy link
Copy Markdown
Owner

Provider integration updates currently require manually coordinating release research, implementation, review, and PR handoff. Factory adds a web/desktop entry point that launches this work through an existing Lecturn provider in an isolated Git worktree and keeps its conversation, reported stage, evidence, controls, and resulting PR accessible.

The page separates the upstream release source from the execution provider, preserves uncertain launch identity without replaying bootstrap, and scopes steering and interruption to the selected environment and run. The coordinator follows an ordered research/explore/plan/build/review/PR recipe with explicit repository targeting and no automatic merge or deployment.

Scope and limitations:

  • Three release sources: Codex, Claude Code, and OpenCode. Execution uses an installed provider and model.
  • A standalone Git checkout outside a Stave space is required by current worktree admission.
  • Stages are agent reports; turn completion does not certify validation or PR creation. Workflow adherence remains prompt-driven.
  • Native mobile can use the resulting conversation; it does not get a Factory launch page. Renaming the reserved branch removes Factory indexing while preserving the conversation.

Validation:

  • 58 focused tests passed across the implementation and regression checks: 22 recipe/parser, 18 launch helper, 14 controller, and 4 existing quick-steer tests. The controller suite and scoped lint passed after fixing controls during history synchronization.
  • Web and client-runtime scoped typechecks, scoped lint/formatting, production web build, and staged diff checks passed. Existing build warnings remain.
  • Isolated synthetic browser verification covered desktop and 375-pixel layouts, launch/source selection, steering success/failure, interruption, navigation, and PR handoff. This validates the interface and callbacks, not external provider credentials or GitHub permissions.
  • Independent source review completed with confirmed findings fixed. No preview fixtures, screenshots, or working reports are included in the commit.

Real Factory run: PR #96 was produced in an isolated worktree, separate from this implementation. It surfaces Claude Code startup failures and preserves the resume cursor. Its final run artifacts report 95/95 adapter tests, scoped server typecheck exit 0, clean lint/formatting, and independent review converged after fixing a resume-cursor defect. The output PR targets main at 2ca2d81d3a77824d2887f503b75b02a8f81daa63; its CI is separate from this PR.

Live UI steering submission and acknowledgement were verified on the original built client after history became ready. The synchronization-gate fix is covered by controller tests and CI. The updated cold Vite client did not render under shared-machine load, and final completed-PR-card inspection failed because the native computer-use pipe could not start; those browser checks are not claimed. Screenshots and evidence.

Implemented and reviewed with GPT-6 in the Codex harness, with independent Claude CLI reviews.

@Nurozen

Nurozen commented Sep 29, 2026 •

Copy link
Copy Markdown
Owner Author

Factory page captured in an isolated browser against the real run environment. The sidebar shows the live Claude integration run. This is a new page; there was no Factory page before this change.

Factory page with live provider update run

Live run inspection, including conversation access, stop control, and agent evidence. A direction was sent through the page and acknowledged by the server.

Live Factory run inspection

This branch has not been deployed

No deployments
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