carthagent 1.1.0-preview.12 → 1.1.0-preview.13

package/README.md

@@ -72,6 +72,65 @@ persistence; see the [preview.10 candidate notes](docs/release-notes-preview.10.
 for its limits. Published preview.9 remains immutable and does not acquire
 changes from current main.
 
+### Projects sidebar source preview (development only)
+
+The redesigned Projects sidebar (folder card, folder browser, and folder/model
+setup for new sessions) exists only as source. It is **not** in any published
+`ctg` release, and the steps below do not build or update the published native
+runtime. The published runtime stays pinned to
+`docs/patches/opencode-v2.0.32-session-ui-combined-v4.patch` and
+`lib/opencode/runtime-release.json`.
+
+Requirements: Git, a POSIX shell, `sha256sum` or `shasum`, Bun 1.4.2 (the
+OpenCode `packageManager` pin), and this checkout with `npm ci` already run. No
+native compilation is needed. The launcher is a POSIX `sh` script for Linux and
+macOS; native Windows is not supported.
+
+1. Prepare a clean OpenCode checkout at the pinned upstream and apply the
+   development patch (v5 replaces v4 and applies directly to upstream):
+
+   ```sh
+   git clone https://github.com/anomalyco/opencode "$HOME/src/opencode preview"
+   git -C "$HOME/src/opencode preview" checkout 843a6c514e606b436a7fe713422ace0a93ad3d61
+   script/ctg/prepare-development-runtime.sh "$HOME/src/opencode preview"
+   (cd "$HOME/src/opencode preview" && /path/to/bun-1.4.2 install)
+   ```
+
+2. Launch from any directory with explicit paths (spaces are fine):
+
+   ```sh
+   /path/to/carthagent/script/ctg/source-preview.sh \
+     --source "$HOME/src/opencode preview" \
+     --profile "$HOME/.carthagent/source-preview" \
+     --bun /path/to/bun-1.4.2 \
+     --workspace "$HOME/projects/my project"
+   ```
+
+   The launcher runs `bun --no-env-file run src/index.ts --standalone <workspace>`
+   from `packages/cli` with only a private HOME, TMPDIR, XDG and OpenCode config
+   directory inside `--profile`. It disables project config and auto-update and
+   passes no inherited API keys. On first use it creates the profile (mode 0700)
+   with the Carthagent plugin, Carthage theme and CLI theme config. Existing
+   profile files are never rewritten. The private server listens on an ephemeral
+   loopback port and exits when the TUI exits.
+
+3. Sign in once inside the same profile. Enter secrets only at the terminal
+   prompt, never as arguments:
+
+   ```sh
+   script/ctg/source-preview.sh --source ... --profile ... --bun ... -- auth login
+   ```
+
+In the TUI, the folder card at the top of Projects shows the current folder and
+model. Use **Browse** (or `/browse`) to pick a folder and **Ctrl+S** to confirm.
+**New session** (also Ctrl+X N or `/new`) opens folder and model setup; the session is created only when
+you send the first message, with your current agent and the chosen model. If that agent or model is
+unavailable when you send, the send is blocked and your text is kept until you choose another. Leave with `/exit` (or Ctrl+P, “Exit the app”); relaunch with
+the same `--profile` and choose the session in Projects to continue it.
+
+See [source preview](docs/source-preview.md) for testing, patch verification and
+limits.
+
 ## Install and update
 
 The installer selects an exact published release and acquires its pinned native runtime; it never falls back to an unrelated system binary. See the [native upgrade guide](docs/native-upgrade.md) for source-checkout and profile-preservation instructions, or [legacy CLI instructions](docs/legacy-cli.md) for stable 1.0.7.
@@ -106,21 +165,18 @@ Experimental software may still contain bugs; read its release notes first.
 
 ## Release status
 
-1.1.0-preview.12 is the current experimental release. It republishes
-preview.11 with an npm package that keeps the `ctg` command, plus a release
-check that blocks manifests npm would rewrite. Preview.11 added a Projects /
-Voyages mode switch to the native left rail, with read-only Voyages profile and
-daily assignment summaries, on top of preview.10's native daily coding quests
-(selected evidence, exact-payload preview, fresh per-submission consent, and
-durable recovery; assessments do not award rewards). Native remains the default
-`ctg` interface. Ship retains approval, checks, review, repair, recovery, and
-resume; Lite remains direct execution. Published previews are immutable.
-Experimental installation is explicit and selects published releases only;
-stable 1.0.7 retains the legacy console.
+1.1.0-preview.13 is the current experimental release. It promotes the
+combined-v5 runtime patch: a directory-first Projects rail with a folder
+browser, shared folder and model setup for new sessions, and an isolated
+source-preview launcher, on top of preview.12's npm-publishable package.
+Native remains the default `ctg` interface. Ship retains approval, checks,
+review, repair, recovery, and resume; Lite remains direct execution.
+Published previews are immutable. Experimental installation is explicit and
+selects published releases only; stable 1.0.7 retains the legacy console.
 
 Each experimental release must pass its exact installed-package gate before
-publication. See the [preview.12 release notes](docs/release-notes-preview.12.md),
-[preview.11 notes](docs/release-notes-preview.11.md), and [preview.10 notes](docs/release-notes-preview.10.md); earlier migration findings and remaining platform caveats
+publication. See the [preview.13 release notes](docs/release-notes-preview.13.md),
+[preview.12 notes](docs/release-notes-preview.12.md), and [preview.11 notes](docs/release-notes-preview.11.md); earlier migration findings and remaining platform caveats
 are in the [Native migration ledger](docs/opencode-migration.md#delivery-ledger),
 [native compatibility matrix](docs/native-compatibility.md), and [terminal
 evidence status](docs/native-terminal-semantics.md#evidence-status-pr-162).

package/docs/native-manual-testing.md

@@ -275,11 +275,33 @@ The explicit root is a development selector: its local checksum detects byte
 changes but does not independently establish a published binary's provenance.
 
 The update point for a reviewed local patch is
-`CTG_DEVELOPMENT_RUNTIME_PATCH_SHA256` in `lib/opencode/runtime.mjs`. Initially
-it equals the published patch digest; after generating and reviewing new patch
-bytes, update **only this development constant** and the build recipe's
-`EXPECTED_PATCH` to their actual SHA-256. The regression test in
-`tests/native-ship-plan.test.mjs` requires both to match the checked-in patch.
+`CTG_DEVELOPMENT_RUNTIME_PATCH_SHA256` in `lib/opencode/runtime.mjs`. It pins
+the development patch `docs/patches/opencode-v2.0.32-session-ui-combined-v5.patch`
+(SHA-256 `ec4bb182308ed8b311513aad5c9c7d57dcd0db103f0882f3dc3517d535b4c975`),
+a replacement patch containing the published combined-v4 changes plus the
+folder-browser controller, the Browse folders dialog with its sidebar, compact
+rail and command-palette entry points, the directory-first Projects rail (current
+folder card with Browse, New session and model controls, distinct folder and
+group headings, and an active-session marker), the folder and model setup for
+new sessions (global and folder "New session here" entries; the session is
+created only on the first send, with the chosen folder, agent, model and
+variant), and their tests. It applies directly to a clean
+checkout of upstream `843a6c514e606b436a7fe713422ace0a93ad3d61`; do not apply
+it on top of v4:
+
+```sh
+git clone https://github.com/anomalyco/opencode.git opencode-dev
+git -C opencode-dev checkout 843a6c514e606b436a7fe713422ace0a93ad3d61
+script/ctg/prepare-development-runtime.sh opencode-dev
+```
+
+The preparation recipe checks the source revision, a clean checkout, and the
+patch hash, then applies the patch. It does not install, compile, or publish.
+After generating and reviewing new patch bytes, update **only this development
+constant** and the preparation recipe's `EXPECTED_PATCH`. The regression test
+in `tests/native-ship-plan.test.mjs` requires both to match the checked-in
+development patch, and that the shared release recipe
+`script/ctg/build-owned-runtime.sh` still pins the published v4 patch.
 Do not change `CTG_RUNTIME_PATCH_SHA256`, the published
 `lib/opencode/runtime-release.json`, its archive/executable pins, or historical
 release documentation to make a development build pass. Promotion to a public

package/docs/opencode-owned-runtime.md

@@ -40,9 +40,9 @@ preview.8 or preview.9 acceptance gates have passed.
 
 - Upstream: `https://github.com/anomalyco/opencode`
 - Tag/revision: `v2.0.32` / `843a6c514e606b436a7fe713422ace0a93ad3d61`
-- CTG patch: `docs/patches/opencode-v2.0.32-session-ui-combined-v4.patch` (combined-v3 plus the Projects / Voyages navigation rail, shared dialog resize subscription, and hardened rail/watcher timing tests; published in preview.11 and preview.12)
-- Patch SHA-256: `1f2309bb3a31dfb8e8a0827a6a1144a1f76a005abff58f6f48857639ec02478a`
-- Previous combined-v3 patch SHA-256 (preview.10): `b4238d77827d7ccf8f87fb0326551eaa62268d9387cd89e29bd0cf12bd6dafaa`
+- CTG patch: `docs/patches/opencode-v2.0.32-session-ui-combined-v5.patch` (combined-v4 plus the directory-first Projects rail, folder-browser dialog, shared folder/model session setup, and the isolated source-preview launcher)
+- Patch SHA-256: `ec4bb182308ed8b311513aad5c9c7d57dcd0db103f0882f3dc3517d535b4c975`
+- Previous combined-v4 patch SHA-256 (preview.11 and preview.12): `1f2309bb3a31dfb8e8a0827a6a1144a1f76a005abff58f6f48857639ec02478a`
 - Lock SHA-256: `9d78379cd264584a495440a217b9d2ecab524c9a56f7f8b4b5bed3926daa330d`
 - Historical combined preview.8 source verification: 136 retained TUI rendering/loader/theme/selection
   regressions, 24 core recovery/shell regressions, and core/server/plugin/client/tui