Skip to content

v0.1.0 publish surfaces — docs, adopter README, public-readiness CI gates#52

Merged
BadGuyFranco merged 4 commits into
mainfrom
v0.1-publish
May 28, 2026
Merged

v0.1.0 publish surfaces — docs, adopter README, public-readiness CI gates#52
BadGuyFranco merged 4 commits into
mainfrom
v0.1-publish

Conversation

@BadGuyFranco
Copy link
Copy Markdown
Owner

Ships the remaining v0.1 work so CoCoder can be tagged v0.1.0. Built on a clean branch off main (founder's Option A) so the release contains only v0.1 — the in-flight v0.4 control-plane build stays on oz-control-plane-design.

What's in here

  • Six adopter docs brought to final form: getting-started, faq, orchestration, personas, oz, freshness-policy.
  • README.md rewritten for adopters (removes the "not yet usable" banner; adds a quick-start pointer).
  • ARCHITECTURE.md verification stamp refreshed + storage-zone diagram clarified.
  • New docs/dogfood-evidence.md summarizing how CoCoder orchestrates its own work.
  • Public-readiness gates added to CI: gitleaks (secret scan, full history), LICENSE/NOTICE presence + content, FAQ commercial-use + zero-telemetry checks; existing stale-reference gate retained.
  • One machine-specific path literal scrubbed from a test fixture so the stale-reference gate stays green.

Checked locally (everything that can be)

  • gitleaks: 104 commits scanned, no leaks.
  • All documentation links resolve (0 missing).
  • LICENSE / NOTICE / FAQ public-readiness checks pass.
  • Unit tests pass except one socket-bind test that can't run in the sandbox — CI confirms the full suite.

Not yet done

  • Tagging v0.1.0 is a separate, deliberate step after this merges and CI is green.

Note: also carries one previously-unpushed design-notes commit (d62e8f9: ADR-0008 + Oz design brief + dashboard nav) that already sat on local main — forward-looking design, not v0.4 build work.

🤖 Generated with Claude Code

BadGuyFranco and others added 4 commits May 27, 2026 11:23
…o Dashboard

Correct the Oz control-plane IA to match the founder's stated layout:
- Left nav is exactly five sections — Dashboard, Workspaces, CLIs, Personas,
  Settings. No standalone Runs or Priorities pages.
- Dashboard is built around the Oz chat as the command center; priorities and
  runs are supporting panels inside it (Oz watches runs from the Dashboard).
- Design prompt rewritten to design from the brief alone (don't reuse the
  current shipped oz-dashboard UI), which is what caused the prior drift.
- ADR-0008: five surfaces + new decision on Dashboard composition; six-section
  layout recorded under rejected alternatives. v0.4 priority work items realigned.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Founder chose Option A (disentangle): ship v0.1 from a clean branch off
main so the v0.1.0 tag contains only v0.1 work, not the v0.4 control-plane
design that accumulated on oz-control-plane-design.

main already carries the full v0.1 product baseline (A/B/C/E/F + cross-link
docs + README/ARCHITECTURE/ci.yml/LICENSE/NOTICE). This commit carries the
Oscar-boundary v0.1 delta: current v0.1-foundation plan/README + the
ADR-0001 §6 .command footnote fix (D-M1.9). The 6 D-M1 docs and the
remaining D atoms (D-M1.7/1.8/2.1/D-S2) land next via Bob.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…sh; D-S1 descoped

Reconcile Sub-Playbook D after Bob landed D-M1.7/D-M1.8/D-M2.1/D-S2 (68feb24):
- Mark D-M1.7 (ARCHITECTURE verify), D-M1.8 (README adopter rewrite),
  D-M2.1 (dogfood-evidence), D-S2 (CI gates) complete on branch v0.1-publish.
- Record founder removal of D-S1 internal-proxy from v0.1 scope (dogfoods own
  projects post-ship); v0.1 Solve is now D-S2 only.
- Rewrite next-start brief: next step is the founder release sequence
  (review v0.1-publish -> merge to main -> CI green = D-S2 Class A -> tag v0.1.0),
  not a fresh build run.
- Update PRIORITIES.md row + Status block + SESSION_LOG newest-first entry.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@BadGuyFranco BadGuyFranco merged commit 87c7b2b into main May 28, 2026
2 checks passed
@BadGuyFranco BadGuyFranco deleted the v0.1-publish branch May 28, 2026 01:46
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