GatherThread Beta 3

GatherThread 0.1.0-beta.3 — Beta 3

Beta 3 brings the reviewed main-branch changes since Beta 2 into matching server,
Web, connector, plugin and Launcher artifacts. Its authorized rollout covers both
test.gatherthread.cn and gatherthread.cn, using one frozen build while keeping
the two environments' accounts, configuration, databases and secrets separate.
Release and deployment receipts, not these notes, establish publication or live status.

Highlights

• Browse a project's GT Cloud or authorized GitHub branches in a right-hand file
  workspace. Open and close independent tabs, inspect source, preview Markdown,
  PDF and raster images, review additions/deletions and commit history, and save
  permitted changes to your own branch. Teammate and historical branches remain
  read-only; main still requires review and integration.
• Use focused mobile conversation, member, invitation, settings and connection
  pages. Confirm a detected mobile layout or select Mobile/Desktop explicitly in
  General. Phones continue to use an online computer Agent or Cloud Agent, not a
  local installation flow.
• Keep the conversation header compact: one Summaries entry, one Session options
  entry, and an unread-mention jump that disappears after the message is seen.
• Explicitly share a supported native Codex/DSH connection with selected project
  members, within configured daily limits. Sharing is opt-in and requires a
  supported isolated native execution path; unsupported platforms refuse it.
  This preview does not create an automatic Agent team.
• Install the DSH plugin on 0.2.1-rc.2 Web or Desktop with matching install,
  start, repair and version-check commands. The optional peer guard prevents old
  DSH from applying the incompatible current layer. DSH 0.1.7-rc.2 continues to
  use the unchanged published Beta 2 artifact.

“Multi-Agent” describes the planned next step: one person's connected Agents
forming a team and collaborating directly, with further automatic communication
between different members' Agents only after authorization. Those capabilities
will arrive in a later version; multiple integrations or opt-in connection
sharing are not a claim that this team workflow is already available.

See the changelog, product guide and
中文图文指南 for the current workflow.

Matching packages and downloads

• npm: @gatherthread/codex-connect@0.1.0-beta.3 and
  @gatherthread/dsh-host@0.1.0-beta.3, published under the beta channel.
• Source tag: v0.1.0-beta.3; record its full commit and package integrity in the
  publication receipt. Do not overwrite Beta 1/Beta 2 versions, tags or downloads.
• Current Launcher builds contain the matching connector/plugin. The macOS app
  uses numeric version 0.1.3, build 13, and remains ad-hoc signed, not Developer
  ID signed or notarized. Each platform archive retains its own source/checksum
  provenance and is promoted only after its build verification succeeds.

Prefer Connect Codex → Open Launcher or the source-matched download index.
The release marketplace identity is:

codex plugin marketplace add https://github.com/TH060419/gatherthread.git --ref v0.1.0-beta.3 --sparse .agents/plugins --sparse plugins/gatherthread
codex plugin add gatherthread@gatherthread

A source checkout alone is not an installed connector. Follow the
Codex guide to prepare the source plugin and matching local
package before enabling Hooks. The DSH guide describes its
explicit version boundary; the frozen cordis.patch.dsh-0.1.yml is reference-only,
not an automatic alternate layer in the Beta 3 package.

Upgrade and verification boundaries

Deploy matching server/Web files together. Native sharing adds separate
authorization/job tables, and the file workspace adds provider-bound APIs and
write receipts. Take each environment's verified SQLite/cloud-Git backup before
startup migrations; preserve test admission separately. Prefer forward repair
after migration rather than running an older binary against the changed stores.
Do not copy accounts or reset secrets, quotas, registration settings or model
configuration between environments.

Reuse the reviewed feature tests and CI. Run the canonical release gate once on
the frozen candidate, plus package/version/download consistency checks; do not
repeat full test campaigns or model diagnostics on each server. The deployment
handoff records source SHA/tree, artifact checksums, actual process working
directory, loopback readiness and public HTTPS readiness after Caddy's health
interval. Resolve any pre-existing failed service guards before restart; a
package update must not bypass them.

The DSH 0.2.1-rc.2 change has contract, upstream loader-preflight and isolated
browser evidence from PR107. A complete new-version native Web/provider workflow
has not been rerun; earlier 0.1.7-rc.2 native acceptance is not evidence for it.
Native sharing likewise retains its documented platform/authentication probes
and refusal behavior; fictional browser fixtures are not real-provider or
Windows/Linux acceptance. See ADR-0056,
ADR-0058 and
ADR-0059.

The hosted image must be compared against the final frozen build inputs. Reuse
an unchanged image only with its original immutable identity and provenance;
otherwise build the matching image once for both environments. No document or
version label enables a provider, GitHub App or registration service by itself.