Prepare complete Study Buddy 0.2.4-alpha release batch

.github/workflows/alpha-release.yml

@@ -6,7 +6,7 @@ on:
       version:
         description: Stable, alpha, or beta SemVer without the v prefix
         required: true
-        default: 0.2.0-alpha
+        default: 0.2.4-alpha
         type: string
       signed:
         description: Require Windows code signing (blocked until SignPath onboarding is complete)
@@ -172,7 +172,7 @@ jobs:
           retention-days: 14
 
   assemble:
-    name: Assemble release evidence
+    name: Assemble immutable unpromoted release evidence
     needs: [preflight, build]
     runs-on: ubuntu-24.04
     timeout-minutes: 15
@@ -222,6 +222,9 @@ jobs:
           '
           node -e 'const fs=require("node:fs"); const value=JSON.parse(fs.readFileSync("release-assets/study-buddy-root.cdx.json", "utf8")); if(value.bomFormat!=="CycloneDX" || !value.components?.length) process.exit(1)'
           cd release-assets
+          # Promotion is a separate reviewed action after packaged acceptance.
+          test ! -e distribution-ready.json
+          test ! -e SHA256SUMS
           sha256sum -- * > SHA256SUMS
           cd ..
           node scripts/check-desktop-release-assets.mjs release-assets "$RELEASE_VERSION" "${{ needs.preflight.outputs.channel }}" --final --unpromoted
@@ -250,6 +253,14 @@ jobs:
         with:
           name: study-buddy-${{ inputs.version }}
           path: release-assets
+      - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
+        with:
+          node-version: 22.16
+      - name: Verify draft contains only the exact unpromoted bundle
+        env:
+          RELEASE_VERSION: ${{ inputs.version }}
+          RELEASE_CHANNEL: ${{ needs.preflight.outputs.channel }}
+        run: node scripts/check-desktop-release-assets.mjs release-assets "$RELEASE_VERSION" "$RELEASE_CHANNEL" --final --unpromoted
       - name: Publish reviewed draft from the exact existing tag
         env:
           GH_TOKEN: ${{ github.token }}

.github/workflows/ci.yml

@@ -26,14 +26,24 @@ jobs:
       - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
         with:
           persist-credentials: false
+          submodules: true
       - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
         with:
           node-version: 22.16
           cache: npm
+      - name: Install pinned editor dependencies for workflow parity tests
+        uses: voidzero-dev/setup-vp@49c3e4e92c52e7f8392712a9267bbe71c5ab30e5 # v1.19.0
+        with:
+          working-directory: t3code-fork
+          node-manager: false
+          cache: true
+          run-install: true
       - uses: typst-community/setup-typst@fee4b65b091cc546f02ce3be15fad8760f38a108 # v5.3.0
         with:
           typst-version: 0.15.0
       - run: npm ci
+      - name: Verify workflow package and dependency security contracts
+        run: node --test scripts/check-workflow-package.test.mjs scripts/check-dependency-security.test.mjs
       - name: Install Linux document and browser tooling
         if: runner.os == 'Linux'
         run: |
@@ -59,6 +69,7 @@ jobs:
           pdfinfo -v
           npx playwright install chromium
       - run: npm run typecheck
+      # vitest.config.ts enforces serial files on Windows without shell flags.
       - run: npm test
       - name: Verify SDK and bundled CLI pairing
         run: npm run moodle:doctor:version
@@ -96,6 +107,12 @@ jobs:
         with:
           persist-credentials: false
           submodules: true
+      - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
+        with:
+          node-version: 22.16
+          cache: npm
+      - name: Install parent workflow dependencies for editor broker tests
+        run: npm ci
       - uses: voidzero-dev/setup-vp@49c3e4e92c52e7f8392712a9267bbe71c5ab30e5 # v1.19.0
         with:
           working-directory: t3code-fork

.hidden

@@ -0,0 +1 @@
+AGENTS.md

AGENTS.md

@@ -1,5 +1,9 @@
 # Study Buddy Agent Rules
 
+This is the active application component under the Study Buddy umbrella now
+used by T3 Code. The original repository is an untouched rollback/reference
+copy. Read `../AGENTS.md` and `../project.json` before changing this component.
+
 - Study Buddy is a universal study agent, not degree-, course-, subject-, or institution-specific. Build reusable modular behavior that adapts to the user's topic, study context, and configured sources; avoid hard-coded curricula, subject templates, or source assumptions.
 - Study Buddy must coexist with independently installed T3 Code. Never share or alter its identity, state, ports, protocols, launchers, artifacts, updater, migrations, or processes unless explicitly requested.
 - `t3code-fork/` belongs exclusively to Study Buddy. Treat `reference repo Study Buddy 1.0/` as read-only.
@@ -9,3 +13,15 @@
 - Before changing Study Builder, read its implementation charter and relevant product specification, then update its implementation plan.
 - Store workflow state under `study-buddy-data/`. Never place generated artifacts inside forks or reference repositories.
 - Use the applicable Study Buddy skill for workflow-specific acquisition, rendering, testing, and delivery procedures.
+
+## Batched Development and Release
+
+- A generic request to prepare the next release includes discovery of the entire accumulated batch; never require the owner to remember individual changes or prior chat threads. Start with `docs/release-agent-handoff.md` and `docs/development-batch.md`, then reconcile them against commits since the last public release, root/UI submodule pins, development/release branches, open PRs and local dirty work. Record every discovered change as included, deferred with a reason, or blocked; do not silently omit another branch or silently include uncommitted work.
+- The release agent owns regression triage and the final Windows/Fedora acceptance workflow. Ask the owner only for genuine owner-only actions such as authentication, required permissions or final publication approval, not to enumerate tests or fixes.
+- Development handoff must distinguish committed, pushed (verified remote SHA), merged, deployed and release-accepted states. Push the reviewed UI dependency before the parent pointer when push is authorized. Document local-only repositories and uncommitted work explicitly; never call local commits remotely available.
+
+- Accumulate compatible fixes and features on the current development version instead of starting or incrementing a release for every change. A batch of roughly 10–20 fixes is a planning heuristic, not a quota or permission to merge unverified work.
+- Give every change focused deterministic tests, a scoped commit, and an entry in the development batch backlog. These checks make a change safe to queue; they do not make the accumulated version release-ready.
+- Freeze the batch deliberately before release. At that point, run the applicable Study Buddy review and release skills, resolve the holistic review findings, and build one exact candidate from the reviewed commit.
+- Because clean packaged acceptance is expensive, reserve full Fedora and Windows VM testing for the exact frozen candidate rather than every small development commit. Any byte change after acceptance invalidates that evidence and requires a rebuilt candidate and fresh affected acceptance.
+- Do not tag, publish, promote, or call a build release-ready without explicit owner approval and the required final review, packaged checks, and clean Fedora/Windows VM acceptance. Never move or reuse a public tag for changed bytes.

CHANGELOG.md

@@ -6,6 +6,26 @@ for owner testing; the `1.x` line remains reserved for the first full release.
 
 ## Unreleased
 
+## 0.2.4-alpha — candidate
+
+- Added Codex, Gemini and Claude provider installation, connection management,
+  task profiles and provider-independent study workflows.
+- Improved source discovery, source-grounded obligations and study communication.
+- Moved native PDF requests to one document owner with deterministic templates,
+  source attribution, math compilation and physical review.
+- Added complete native quiz capture, original media preservation, first-attempt
+  recovery and saved-response verification; final submission remains blocked.
+- Added permission-bound email inventory/search/read and exact-message send
+  approvals; corrected latest-unread ordering and preserved read state.
+- Improved desktop source runtime, identity/ports, updater diagnostics, consent,
+  chat/sidebar/composer behavior and local browser pairing for external agents.
+- Updated production dependencies and repaired cross-platform Windows tests,
+  lock/alias handling, PDF tool discovery and packaged release provenance.
+
+This candidate includes the complete accumulated development batch. Historical
+`v0.2.3-alpha` remains untouched. Publication and website distribution are pending
+exact Windows/Fedora packaged acceptance; source checks alone are insufficient.
+
 ## 0.2.2-alpha — 2026-09-10
 
 This test alpha combines the previously unpublished 0.2.2 and 0.2.3 candidates.

README.md

@@ -4,12 +4,11 @@ Study Buddy is a local-first AI learning companion that finds authorized course
 evidence and turns it into source-grounded answers, PDF study guides, and
 single-file offline learning webpages.
 
-> **Alpha status:** `v0.2.2-alpha` consolidates the unpublished corrective builds
-> for hands-on Windows and Fedora testing. Stable-channel promotion is separate
-> and requires owner approval and clean Windows and Fedora acceptance;
-> the `1.x` line remains reserved for the future full release. Read
-> the [security](SECURITY.md) and [privacy](PRIVACY.md) guidance before
-> connecting an account.
+> **Alpha status:** `v0.2.4-alpha` is the next coordinated candidate. The latest
+> public version is `v0.2.2-alpha`; website promotion requires exact clean
+> Windows and Fedora acceptance. The `1.x` line remains reserved for a full
+> release. Read the [security](SECURITY.md) and [privacy](PRIVACY.md) guidance
+> before connecting an account.
 
 [MIT licensed](LICENSE) · [Roadmap](ROADMAP.md) ·
 [Contributing](CONTRIBUTING.md) · [Support](SUPPORT.md)

docs/composer-permissions-2026-10-02.md

@@ -0,0 +1,48 @@
+# Compact composer permission labels — 2026-10-02
+
+The composer now shows the active profile's name without adding “profile”.
+Built-ins read Fast, Balanced, and Quality; custom names are preserved verbatim.
+A single vertical divider separates the profile picker from Computer, Email,
+and Quizzes. Their selected modes appear through icons, hover descriptions,
+and the existing detailed menus.
+
+Computer retains its locked, edit, and unlocked icons. Email uses an envelope
+with an X for off, search for reading, plus for drafts, and a small paper plane
+for sending with approval. Multiple accounts retain the generic envelope and
+their individual account permissions in the popover. Quizzes always use a
+shield: an “i” for review, a question mark for asking before opening, and a
+check mark for assistance. The same quiz icons appear in the narrow overflow
+menu. The existing responsive overflow behavior remains in place.
+
+This is a presentation change. Runtime permission values, per-account email
+policy, quiz admission and the final-submission boundary are preserved.
+
+## Evidence
+
+Browser-diagnostic screenshots of the actual rendered composer are retained
+under `study-buddy-data/composer-controls-review/2026-10-02/`: desktop and narrow
+layouts, plus all three quiz modes. The screenshots were visually inspected.
+These fixture-backed browser checks do not establish native desktop or
+packaged Windows/Fedora acceptance. No chat prompt or actual quiz was submitted.
+
+Focused regressions cover fixed control labels and ordering, one divider,
+verbatim custom names, runtime menu descriptions and icon changes, all three
+quiz transitions and saved values, and all four email permission states with
+their corresponding account switches.
+
+All 125 affected Chromium checks passed across the full chat view, profile
+picker, compact controls menu, and source settings. Full fork `vp check`
+passed, and all 13 workspace typechecks passed.
+
+UI commit `eec115d93` and the parent pointer/documentation are committed locally.
+
+The follow-up replaces the email approval question mark with a paper plane
+at the envelope's bottom-right corner. The detailed menu still requires
+approval for sending. Its browser-diagnostic capture is
+`study-buddy-data/composer-controls-review/2026-10-02/email-ask-to-send.png`.
+Follow-up UI `3521096d8` is committed locally; all 10 source-settings browser
+checks, full fork format/lint, and all 13 workspace typechecks passed.
+This change belongs to the open `0.2.3-alpha` development batch. It is local
+development work; it has not been pushed, merged, packaged, deployed, published,
+or release-accepted. Frozen-batch review and exact-candidate Windows/Fedora
+acceptance remain required.