Repository navigation
website: bring src-control status up to date (Phases 1-31) - #127
Merged
Merged
Conversation
The site still said Phases 1-9 while the src-control repo's phase log has Phases 1-31 built. Update the badge, status arc, feature list, and demo examples on /src-control and the homepage pillar: agent workspaces (sc work), signed commits, sealed agent-session transcripts, SSH/HTTP native transports with access control, bidirectional Git sync including hosted remotes, sparse checkouts, streaming packs, partial clone. Facts sourced from src-control CLAUDE.md phase log and ROADMAP. Claude-Session: https://claude.ai/code/session_01V9TtRvFnDS4eGkcxZhnyf9
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the website’s src-control marketing/status copy to reflect the project’s current capabilities and phase progress, aligning the /src-control page and homepage pillar with the upstream repo’s phase log/roadmap.
Changes:
- Refreshes
/src-controlmetadata and status narrative (badges, description, “How it works”, and phase arc summary). - Updates demo/command snippets to include workspace and transcript examples.
- Updates the homepage
src-controlpillar copy and meta line to match the new positioning.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 5 comments.
| File | Description |
|---|---|
| website/src/pages/src-control.astro | Updates src-control page description, demo commands, capability bullets, and status paragraph to reflect newer features/phases. |
| website/src/pages/index.astro | Updates homepage src-control pillar copy, demo snippet, and phase meta line. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| <div class="badges"> | ||
| <span class="badge"><span class="pulse"></span>Phases 1–9 implemented</span> | ||
| <span class="badge"><span class="pulse"></span>Phases 1–31 built</span> |
| encrypted paths, packfiles/GC, and Git export. Beyond the P9 roadmap: | ||
| network transports, richer merge ergonomics, secret/permission | ||
| lifecycle, sparse/subtree sharing, signed provenance. | ||
| Phases 1–31 are built and tested. The arc so far: in-RAM virtual |
| editing (P10–21); signed commits, merge ergonomics, sparse checkouts, | ||
| streaming pack transfer, sc-native HTTP transport with token access | ||
| control, partial clone, security hardening, sealed agent-session | ||
| transcripts, and listener resource limits (P22–31). Feature phases |
Comment on lines
+87
to
+89
| <li>sc-native transports over SSH and HTTP — token-based access | ||
| control, connection caps, session timeouts, streaming packs that | ||
| move multi-GiB repos in bounded RAM — plus partial clone</li> |
| <p class="meta">Rust · Phases 1–9 implemented</p> | ||
| <span class="comment"># agent workspaces: run a command across N forks, harvest results</span> | ||
| $ sc work --agents 4 -- cargo test</code></pre> | ||
| <p class="meta">Rust · Phases 1–31 built</p> |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The suite site still described src-control as "Phases 1–9 implemented" — the repo's authoritative phase log (CLAUDE.md) has Phases 1–31 built, so the site under-sold the project by 22 phases, and the "beyond the P9 roadmap" teaser listed features (network transports, merge ergonomics, lifecycle, sparse, signed provenance) that have all since shipped.
What
/src-controlpage and the homepage pillar:demo/sc work --agents 4 -- cargo testandsc transcript attach HEAD session.json --signAll facts sourced from the src-control repo's CLAUDE.md phase log and ROADMAP (same pattern as #101 for Sentinel). Astro build passes (4 pages).
https://claude.ai/code/session_01V9TtRvFnDS4eGkcxZhnyf9