Ourobuild

Studio notes · Ourobuild

Changelog

Dated studio notes are distinct from package releases and current setup requirements.

1. June 16, 2026 · added / changed

   Agent-workflow scaffolding and PRD issue preview

   Ourobuild’s early source established configuration, agent-workflow starter files, MCP settings, skills, and a CLI for an existing repository. init writes those artifacts into a target project. run --layer 2 --dry-run is intended to parse pending PRD roadmap checklist items into issue proposals without a GitHub write; running Layer 2 without --dry-run can create issues with configured GitHub credentials. Other run layers print guidance about the generated workflows. They do not execute a local autonomous build loop.

   The current source also includes setup diagnostics and changelog/dashboard helpers. Their presence does not establish that a generated workflow compiled, ran, merged code, captured a release, or enforced a budget. The seven-stage ring on the standalone landing is a design map rather than a completed execution trace.

   Source-run evaluation, 25 September 2026: against current source 4ee6ba6, init --engine codex --model local-fixture --search searxng wrote starter files in a disposable Git project. The immediately following Layer 2 dry run could not load the generated config because it imports bare ourobuild, which was not installed in that target project by the documented source-checkout quick start. doctor reported 6/9 checks, including that config failure. No external agent, GitHub issue creation, or credential-backed run was tested; the dry-run onboarding path therefore remains unverified end to end.

   The former shared light/dark hero and inline image pictured the landing page, not paired product output, and were withdrawn. Real current CLI transcripts, paired captures, annotated motion, narration, and a release poster still need their own verified media study.