Make Scramjet's demonstrated development velocity visible

[LeanAndMean]

Summary

• Reframe the repository landing page around the workflow friction Scramjet removes and the mechanisms that support durable agentic development.
• Show a representative issue-to-ship path and clarify the roles of the Pi runtime, Scramjet harness, and optional Mach 12 methodology.
• Add a dated, qualified dogfooding snapshot with inspectable repository evidence while preserving early-development caveats and contributor navigation.

Test plan

• Verify all local paths, heading anchors, and introduced public links.
• Confirm cited pull request states, titles, scale figures, and discussion artifacts against GitHub evidence.
• Inspect the pushed branch's GitHub-rendered README, including narrow-width presentation.
• Review the repository description, topics, and homepage for consistency.
• Run npm run lint and git diff --check.

Fixes #465

[LeanAndMean]

Automated PR Review

Critical

None.

Important

None.

Suggestions

S1: Use capability wording for fresh sessions (README.md:23). “Fresh sessions give each substantial step a bounded context window” implies every substantial step automatically runs in a fresh session, while fresh-session dispatch is optional and declared by the selected next-step candidate. Consider: “Fresh sessions can give substantial steps a bounded context window.” Per mach12:comment-analyzer.

S2: Make the command-edge wording plural (README.md:26). A command policy can expose multiple candidates, so “Each command owns its possible next step” is narrower than the current contract. Consider “Each command owns its possible next steps” or “Each command owns its outgoing transitions.” Per mach12:comment-analyzer.

S3: Link directly to Pi’s canonical repository (README.md:86). https://github.com/earendil-works/pi-mono currently redirects to https://github.com/earendil-works/pi; using the canonical target avoids relying on a redirect and keeps the displayed source destination current. Per mach12:silent-failure-hunter.

Strengths

• The rewrite leads with user outcomes and concrete workflow mechanisms while retaining a prominent, accurate early-development caveat.
• The representative path is clearly optional rather than a mandatory pipeline, and the prose correctly distinguishes choice-bearing transitions from deterministic forced transitions.
• The Pi runtime, Scramjet harness, and optional Mach 12 methodology are separated clearly and consistently with current project authority.
• The dated dogfooding evidence is inspectable and carefully bounded: changed lines are defined, automated discussion artifacts are not presented as human approval, and the text disclaims benchmark, causation, quality, and external-adoption conclusions.
• The implementation completely covers Make Scramjet's demonstrated velocity visible to prospective users #465 and its latest plan without adding assets, generators, CI machinery, dependencies, or other unnecessary scope.
• Repository-relative paths and anchors resolve; cited PR titles, merged states, changed-line totals, file counts, and discussion artifacts were verified; the README rendering and narrow-width presentation are sound.
• Installation, package orientation, contributor navigation, documentation links, and licensing remain discoverable below the product narrative.

Reviewed by GPT-5.6 Sol

This is an automated review.

[LeanAndMean]

Independent Review Assessment

Assessing review comment: #475 (comment)

Classifications

S1 — Genuine issue

Original finding: Fresh-session wording presents the capability as universal.

README.md:23 says fresh sessions “give each substantial step” a bounded context window, but fresh_session defaults to false and a new session is created only when the selected next step requests one. Changing “give” to “can give” is a precise, contained correction that preserves the benefit without overstating current behavior.

S2 — Nitpick

Original finding: The command-edge wording uses singular “next step” despite policies that can offer multiple candidates.

Closed and open policies can expose candidate arrays, although the surrounding sentence already mentions choices, so the current prose is not materially misleading. “Each command owns its possible next steps” is a safe precision improvement.

S3 — Nitpick

Original finding: The upstream Pi link relies on a redirect rather than using the canonical repository URL.

The current /earendil-works/pi-mono destination redirects to /earendil-works/pi, which is also the canonical upstream recorded in repository guidance. Updating the link avoids an unnecessary redirect and aligns the landing page with current authority.

Staged Implementation Plan

Stage 1 — Required: Correct fresh-session capability wording

• Finding: S1
• Affected file: README.md
• Change the fresh-session bullet to: “Fresh sessions can give substantial steps a bounded context window.”
• Verify Markdown formatting and run git diff --check.

Stage 2 — Optional: Tighten transition and upstream-link wording

• Findings: S2, S3
• Affected file: README.md
• Change the transition sentence to: “Each command owns its possible next steps.”
• Change the Pi link destination to https://github.com/earendil-works/pi.
• Recheck the rendered links and run git diff --check.

Assessed by GPT-5.6 Sol

[LeanAndMean]

Review-fix progress

Originating review: 5209444505

Completed S1–S3 from the selected review cycle:

• Corrected the fresh-session bullet to describe an optional capability rather than universal behavior.
• Made the command-edge wording plural to cover policies with multiple candidates.
• Replaced the redirecting Pi repository link with its canonical destination.

Commit: 6865d23fa0e4d011c404767fa2184f208680ea57 (Correct README workflow capability wording)

Verification:

• git diff --check passed.
• Targeted README assertions confirmed all three expected strings and removal of the redirecting URL.
• Local HEAD, upstream, and the fresh PR head all converged at the commit above; the worktree is clean.