twoimo · twoimo · Aug 4, 2026 · Aug 4, 2026 · Aug 4, 2026 · Aug 5, 2026
diff --git a/.gitattributes b/.gitattributes
@@ -52,9 +52,14 @@ poetry.lock -text
 *.cmd text eol=crlf
 *.bat text eol=crlf
 
-# Changelogs are append-mostly; auto-merge by unioning both sides.
-packages/*/CHANGELOG.md merge=union
-
+# CHANGELOGs are deliberately NOT given `merge=union`. Union never conflicts --
+# it concatenates both sides of an overlapping hunk. Release commits insert
+# `## [X.Y.Z]` directly beneath the surviving `## [Unreleased]` heading, so a
+# branch that added entries under Unreleased overlaps exactly that region and
+# union silently files those entries inside a version that already shipped.
+# GitHub also ignores the driver when computing mergeability, so it reported
+# phantom conflicts on every PR that touched a CHANGELOG. A real conflict that
+# an author resolves is strictly better than a silent misfile.
 
 # Byte-exact render-golden fixtures must never be normalized. Mark them
 # -diff too so `git diff --check` does not flag trailing whitespace on raw

diff --git a/.github/actions/build-native/action.yml b/.github/actions/build-native/action.yml
@@ -27,6 +27,10 @@ inputs:
       description: Whether Swatinem/rust-cache should write a cache entry
       required: false
       default: "false"
+   nightly_version:
+      description: Optional immutable nightly SemVer to stage after dependency installation.
+      required: false
+      default: ""
 
 runs:
    using: composite
@@ -61,6 +65,10 @@ runs:
            bun-version: "1.3"
       - shell: bash
         run: bun install --frozen-lockfile
+      - name: Stage nightly release version
+        if: inputs.nightly_version != ''
+        shell: bash
+        run: bun scripts/nightly-release.ts stage --version "${{ inputs.nightly_version }}" --source-sha "${{ inputs.hash }}"
       - name: Install cross-compilation toolchain
         if: inputs.target == 'aarch64-unknown-linux-gnu'
         shell: bash
@@ -84,7 +92,7 @@ runs:
            TARGET_VARIANTS: ${{ inputs.variant }}
            # Tag builds ship the size-tuned dist profile (strip=debuginfo,
            # fat LTO, panic=unwind preserved); PR/branch builds keep ci.
-           PI_NATIVE_PROFILE: ${{ startsWith(github.ref, 'refs/tags/v') && 'dist' || '' }}
+           PI_NATIVE_PROFILE: ${{ (startsWith(github.ref, 'refs/tags/v') || inputs.nightly_version != '') && 'dist' || '' }}
            CARGO_TARGET_AARCH64_UNKNOWN_LINUX_GNU_LINKER: aarch64-linux-gnu-gcc
         run: bun run ci:build:native
       - name: Upload native addon(s)

diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
diff --git a/.github/workflows/dev-ci.yml b/.github/workflows/dev-ci.yml
diff --git a/.github/workflows/public-site-sync.yml b/.github/workflows/public-site-sync.yml
@@ -26,6 +26,12 @@ jobs:
       - uses: oven-sh/setup-bun@0c5077e51419868618aeaa5fe8019c62421857d6  # v2
         with:
           bun-version: "1.3"
+      # The docs index is generated and untracked, and this job deliberately
+      # skips `bun install` (it only reads repo metadata), so the root `prepare`
+      # hook never fires here. Build it explicitly, which also keeps the
+      # staleness assertion in check:public-sync meaningful rather than vacuous.
+      - name: Build the generated docs index
+        run: bun --cwd=packages/coding-agent run generate-docs-index
       - name: Check local public docs/site/version metadata
         run: bun run check:public-sync
 
@@ -39,5 +45,9 @@ jobs:
       - uses: oven-sh/setup-bun@0c5077e51419868618aeaa5fe8019c62421857d6  # v2
         with:
           bun-version: "1.3"
+      # `--live` runs the local surface check too, so it needs the generated
+      # docs index for the same reason as local-public-sync above.
+      - name: Build the generated docs index
+        run: bun --cwd=packages/coding-agent run generate-docs-index
       - name: Exercise production remote final-evidence and deployed release-state validation
         run: bun scripts/check-public-version-sync.ts --live
diff --git a/.gitignore b/.gitignore
@@ -13,6 +13,8 @@ target/
 *.node
 *.node.build.json
 *.b64.js
+# `bun build --compile` leaves these next to the entrypoint when it is interrupted.
+*.bun-build
 
 # Environment
 .env
@@ -58,6 +60,7 @@ packages/ai/test/.temp-images/
 .gjc/rlm/
 .gjc/state/
 .gjc/_session-*/
+.gjc/rss-checkpoints/
 .gjc/metrics.json
 .pi_config/
 .opencode/

diff --git a/AGENTS.md b/AGENTS.md
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -1,4 +1,5 @@
 # Contributing to Gajae-Code
+Maintainers and their access are listed in [MAINTAINERS.md](./MAINTAINERS.md).
 
 Thanks for contributing. This guide is intentionally short so pull requests land on the right branch with enough context to review.
 
@@ -35,6 +36,26 @@ bun run check
 
 Use focused tests first for code changes, then broader checks when the change affects shared behavior or release-critical paths.
 
+## Rebasing onto `dev`
+
+`dev` moves often, so expect to rebase. Two files behave in ways worth knowing about up front.
+
+**`packages/*/CHANGELOG.md` conflicts are normal.** These files have no custom merge driver: if your branch and `dev` both added entries under `## [Unreleased]`, git reports a real conflict. Resolve it by keeping **both** entries under `## [Unreleased]`. Never move an entry into a released `## [X.Y.Z]` section, and never edit a released section — that version already shipped and its notes are historical record.
+
+Resolving one of these by emptying the file is a real hazard, not a hypothetical: ten pull requests across six authors did exactly that within ten minutes of the merge driver being removed, each leaving a one-byte changelog with every released section gone. CI now fails a PR that removes any `## [X.Y.Z]` heading (`scripts/changelog-history-guard.ts`), but check before you push:
+
+```sh
+git cat-file -s HEAD:packages/coding-agent/CHANGELOG.md   # expect ~300 KB, not 1
+```
+
+If it is already lost, recover with `git checkout origin/dev -- packages/<pkg>/CHANGELOG.md` and re-add only your own entry.
+
+**`packages/coding-agent/src/internal-urls/docs-index.generated.ts` is generated and untracked.** `bun install` rebuilds it through the root `prepare` hook, and `bun run generate-docs-index` rebuilds it on demand. Do not commit it. If you see it in `git status`, something forced it back into the index — `git rm --cached` it. A tracked copy inlines every doc onto a single line, which git cannot three-way merge, so it conflicts on every rebase.
+
+## Nightly release operations
+
+The `CI` workflow publishes a nightly prerelease from `main` at 04:23 UTC. Maintainers can run the same cycle with **Run workflow → nightly-release**. The run must pass the complete main check/test graph before publication, then publishes all public packages under the npm `nightly` dist-tag and creates a matching immutable GitHub prerelease with binaries and package-evidence assets. Do not create or move nightly tags manually, and do not edit package versions or `[Unreleased]` changelog sections for a nightly run; version staging is ephemeral inside CI.
+
 ## PR checklist
 
 - Target branch is `dev`, not `main`.

diff --git a/Cargo.lock b/Cargo.lock
diff --git a/Cargo.toml b/Cargo.toml
@@ -4,7 +4,7 @@ exclude = ["crates/brush-core-vendored", "crates/brush-builtins-vendored", "crat
 resolver = "3"
 
 [workspace.package]
-version = "0.11.6"
+version = "0.12.16"
 edition = "2024"
 license = "MIT"
 authors = ["Yeachan-Heo"]
@@ -254,8 +254,10 @@ windows-sys = { version = "0.61", features = [
    "Win32_Storage_ProjectedFileSystem",
    "Win32_System_Com",
    "Win32_System_IO",
+   "Win32_System_JobObjects",
    "Win32_System_Ioctl",
    "Win32_System_LibraryLoader",
+   "Win32_System_ProcessStatus",
    "Win32_System_Threading",
 ] }
 winreg = "0.56"

diff --git a/MAINTAINERS.md b/MAINTAINERS.md
@@ -0,0 +1,26 @@
+# Maintainers
+
+Maintainers own the `gajae-code` repository: they review and merge pull requests,
+drive the `dev` → `main` release flow, and are reachable for governance decisions.
+
+## Roster
+
+| GitHub | Role | Access |
+| --- | --- | --- |
+| [Yeachan-Heo](https://github.com/Yeachan-Heo) | Owner / maintainer | admin |
+| [probepark](https://github.com/probepark) | Maintainer | write |
+| [HaD0Yun](https://github.com/HaD0Yun) | Collaborator | write |
+| [IYENTeam](https://github.com/IYENTeam) | Collaborator | write |
+
+Access is granted at the GitHub repository level. Because `gajae-code` is owned by
+a personal account, GitHub does not expose the org-only `maintain`/`triage` roles;
+the closest equivalent is the **write** (push) role, which covers day-to-day
+maintenance — pushing to `dev`, reviewing and merging PRs, and managing issues and
+PRs. `admin` is reserved for the repository owner.
+
+## Branch and review policy
+
+- All PRs target `dev`. `main` is reserved for maintainer-directed release flow.
+- Maintainers review and merge PRs against `dev` and drive releases to `main`.
+- See [CONTRIBUTING.md](./CONTRIBUTING.md) for the contribution flow and the
+  changelog/merge-driver rules that apply to every PR.
diff --git a/README.md b/README.md
@@ -1,6 +1,3 @@
-<p align="center">
-  <img src="assets/logo-vertical.png" alt="Gajae-Code vertical logo" width="320" />
-</p>
 
 <p align="center">
   <img src="assets/hero.png" alt="Gajae-Code autonomous coding-agent hero illustration" width="100%" />
@@ -91,6 +88,18 @@ bun install -g gajae-code
 
 The scoped package is also available as `@gajae-code/coding-agent`.
 
+### Nightly channel
+
+A verified nightly prerelease is published from `main` at 04:23 UTC and can also be started manually with the **nightly-release** CI dispatch. Nightly runs execute the complete main verification graph, build every supported native addon and standalone binary, publish the exact package set under the npm `nightly` dist-tag, and create a matching GitHub prerelease with package evidence. They do not move npm `latest`, rewrite `main`, or consume the `[Unreleased]` changelog sections.
+
+```sh
+bun install -g gajae-code@nightly
+gjc --version
+gjc --smoke-test
+```
+
+Already on GJC? Switch channels without reinstalling: `gjc update --channel nightly` moves to the latest nightly, and `gjc update --channel stable` switches a nightly install back to the latest stable (the command detects the channel switch and installs even though stable is semver-lower than the nightly). To make a channel the default for both `gjc update` and the startup update check, set **Settings → Interaction → Update Channel** (the `startup.updateChannel` setting). In the brief window where a nightly shares the stable core version, add `--force` to move onto it.
+
 ### Shell completion
 
 GJC can generate a Fig/withfig-compatible spec for [Microsoft inshellisense](https://github.com/microsoft/inshellisense):
@@ -251,6 +260,12 @@ gjc setup defaults --check
 
 For evaluating Aside as an opt-in search/context retrieval sidecar, see [`docs/aside-integration.md`](docs/aside-integration.md). For generic third-party bot setup and provider-independent smokes, see [`docs/bot-integration.md`](docs/bot-integration.md). For external-control readiness, see [`docs/external-control-readiness.md`](docs/external-control-readiness.md). For the wire protocol and machine interfaces, see [`docs/sdk.md`](docs/sdk.md).
 
+## SDK Extensions
+
+- [gjc-remote](https://github.com/kogangdon/gjc-remote) — a real-world SDK extension for controlling allowlisted GJC sessions on remote hosts from Discord.
+- [oh-my-gajae-code](https://github.com/devswha/oh-my-gajae-code) — a community plugin marketplace for installing additional workflow skills and slash commands.
+- [GJC multivendor setup guide](https://github.com/project820/gjc-multivendor-setup-guide) — role-based provider profiles and installable model bundles for multivendor GJC setups.
+
 ## Configuration
 
 Provider retry budgets live in `~/.gjc/config.yml`:
@@ -271,6 +286,8 @@ Interactive startup checks the npm registry for a newer GJC version in the backg
 
 Run `gjc config set startup.checkUpdate false` to disable the launch-time check. Registry or network failures are ignored so they do not block startup.
 
+Both the launch-time check and `gjc update` resolve the registry the way npm does — `BUN_CONFIG_REGISTRY` or `npm_config_registry` from the environment, a scoped `@gajae-code:registry` key, then your user and machine-wide `.npmrc`, including the credentials registered for that registry. A mirrored or firewalled network is therefore checked at the same place the update would install from. A `.npmrc` in the current working directory is deliberately ignored, so a repository you have cloned cannot redirect the check or choose the credential it carries. `bunfig.toml` is not read, so a mirror declared only there is still checked against the public registry.
+
 ### Good to read together
 
 - [GJC multivendor setup guide](https://github.com/project820/gjc-multivendor-setup-guide) — a community guide for role-based provider/profile selection across Anthropic, OpenAI/Codex, Google/Gemini, xAI/Grok, and opencode-go. Treat its presets as user-level configuration guidance rather than bundled defaults; verify model availability and provider auth in your own environment before adopting them.
@@ -350,7 +367,7 @@ For a package-by-package map, see [`docs/codebase-overview.md`](docs/codebase-ov
 
 ## Contributors
 
-Thanks to the people and agents helping shape the early Gajae-Code releases, including [Yeachan-Heo](https://github.com/Yeachan-Heo), [IYENTeam](https://github.com/IYENTeam), and [HaD0Yun](https://github.com/HaD0Yun). Contributions, bug reports, and release validation are welcome through GitHub and the Discord community.
+Thanks to the people and agents helping shape the early Gajae-Code releases, including [Yeachan-Heo](https://github.com/Yeachan-Heo), [IYENTeam](https://github.com/IYENTeam), [HaD0Yun](https://github.com/HaD0Yun), and [probepark](https://github.com/probepark). Contributions, bug reports, and release validation are welcome through GitHub and the Discord community.
 
 ## Inspirations and lineage