Release 0.5.1: beta promotion candidate

.github/workflows/ci.yml

@@ -2,7 +2,7 @@ name: CI
 
 on:
   push:
-    branches: [main]
+    branches: [main, beta]
   pull_request:
 
 permissions:

AGENTS.md

@@ -178,6 +178,7 @@ and the store modules; never read the tables from a gated folder.
   — one-time import of the pre-SQLite JSON/JSONL into the tables (guarded by a `_meta` flag; old
   files are left on disk as inert backups).
 - Tables: `users`, `channels`, `channel_meta`, `sessions`, `schedules`, `acks`,
+  `conversation_reply_sessions` (conversation-scoped user/bot message IDs → group session roots),
   `followup_threads` + `followup_done`, `bg_jobs` (config-shaped rows keep their full record in a
   JSON `data` blob so every field survives + no migration for new fields); `usage` and `events`
   (the dashboard data — fully typed, indexed columns for day/week/month/channel/user rollups).
@@ -251,7 +252,10 @@ Config that stays as **JSON files** (read wholesale / bootstrap, hand-editable):
 - **Composio identities stay distinct.** Inject the active author's token as `composio-user` and
   independently inject shared `composio` from the channel token, falling back to the organization
   token. A channel folder never stores either token in plain settings. “My account” means
-  `composio-user`; “your/channel account” means `composio`; ambiguous identity must be clarified.
+  `composio-user`; “your/channel account” means `composio`. Reads/searches may use either or both
+  unless the user restricts the account or scope. Writes/sends/state changes require the intended
+  identity and connected account; reuse established choices and clarify only unresolved mutation
+  identity. Independent authorized reads can continue while that clarification is pending.
 - **Composio is the only external Slack MCP.** There is NO hosted per-user Slack MCP and no
   `connect_slack`/`xoxp` OAuth (removed). Slack actions beyond the gateway's own bot tools —
   cross-channel search, sending elsewhere, scheduled sends, canvases, reactions — go through the
@@ -328,7 +332,35 @@ Config that stays as **JSON files** (read wholesale / bootstrap, hand-editable):
 
 ## Contributor workflow
 
-Use a dedicated branch and worktree from the latest upstream main. Keep shared integration
+### Beta development and stable promotion
+
+- `beta` is the integration branch for all new development, fixes, documentation and tests.
+  Start each task from current `origin/beta` in its own branch/worktree; validate and land on
+  `beta`, then push `origin beta`. Keep a served beta checkout on `beta` between tasks.
+- `main` is the stable release branch for downstream installations. Completing a task or
+  receiving permission to push to `beta` never authorizes a merge or push to `main`.
+- Promote `beta` to `main` only after BOTH a full test pass and the user's explicit confirmation
+  to release that exact candidate. Prepare a release PR and report its candidate commit, scope,
+  test results and live acceptance evidence BEFORE asking for confirmation. A request to adopt
+  this workflow, earlier general approval, silence, or a beta merge is not release approval.
+- A full test pass means `npm run test:coverage` (the full regression suite with coverage floors),
+  `npm run check:static`, `npm run secret-scan`, `npm run test:security-coverage`,
+  `npm audit --omit=dev --audit-level=high`, and `npm run check:dco -- origin/main..HEAD`,
+  plus passing CI and every applicable live release gate in `TEST-PLAN.md` for Claude and Codex.
+  Include exact fixtures, prompts/actions and observed evidence; a skipped, blocked, failed or
+  unexecuted required check is not a pass. Only cases unaffected by engine choice may be marked
+  engine-independent. Maintainers complete private deployment acceptance where applicable.
+- Approval and evidence belong to the exact tested candidate. If its content changes, or
+  integration with newer `main` changes the proposed release, rerun the applicable full checks
+  and obtain fresh user confirmation before promotion. Release only the approved candidate;
+  do not include later beta commits. Keep `beta` up to date with the approved stable history.
+- These branch and release rules apply to both Claude and Codex and override generic skill
+  defaults that say to merge completed tasks into `main`. Use the deployment's serialized landing
+  lock for integration; never switch a shared served checkout to `main` merely to publish a release.
+
+
+Use a dedicated branch and worktree from the latest upstream `beta`. Target development pull
+requests at `beta`; completed development work is merged and pushed to `beta`. Keep shared integration
 checkouts clean, stage only your changes, sign off commits under `CLA.md`, and open a pull request.
 External contributors push to their own fork and never need the publisher's GitHub account or a
 production checkout. See [CONTRIBUTING.md](CONTRIBUTING.md) for local checks and PR requirements.

CHANGELOG.md

@@ -1,5 +1,40 @@
 # Changelog — ChannelGate
 
+- Reply in Slack when conflicting shared-folder skill or memory settings prevent a request
+  from starting, with admin repair instructions instead of silently logging the error.
+
+- Put Remove and Add/update directly on Slack Settings → Secrets. Refresh the same page after
+  deletion, and return saved entry forms to their parent without duplicate lists or modal stack growth.
+
+- Remove the `/files` slash command and typed file-browser entry. The reply folder button and
+  Browse channel files shortcut remain available; legacy typed requests explain the replacement.
+
+- Explain in the All Shared Skills hint that its summary updates automatically when its source
+  groups are configured, matching the other combined skill summary.
+
+- Include the current advisory network policy in every engine attempt, including resumed and
+  Clean turns, so a changed switch supersedes stale context and cached request results.
+
+- Preserve existing channel guest grants when an unrelated Admin UI setting is saved, even if
+  the current member roster omits a saved guest. Explicit guest edits retain membership validation.
+
+- Include received human approval in completed control-plane tool results while preserving the
+  operation outcome; clarify that approval cards can be outside the model transcript and that
+  the receipt records an explicit human decision, not an approval supplied by channel Auto mode.
+
+- Keep subsequent turns working after an author deletes a personal skill, while retaining its
+  grant and revision history for restoration and refusing foreign personal skill access.
+
+- Correct skill-creation approval descriptions to show personal versus shared ownership,
+  optional channel grants and automatic personal/channel-scope activation accurately.
+
+- Keep text-only gateway commands on their control path after thread file sharing, while
+  preserving canonical current attachments and ordinary agent attachment recovery.
+
+- Reject incomplete engine turns even when partial text exists; preserve failure diagnostics and
+  usage. Reserve restart recovery before Slack reconnects, show each recovering thread promptly,
+  and retry pending recoveries on reconnection without requiring another daemon restart.
+
 - Fix one-time automation edits shifting by the browser/daemon timezone difference and potentially firing future tasks immediately.
 
 ChannelGate was formerly *Claude Gateway for Slack*; entries below the rename keep their original
@@ -18,7 +53,52 @@ product overview.
 > | Makeitfuture Sustainable Use License 1.1 | 2026-08-20 | never published |
 > | Makeitfuture Sustainable Use License 1.0 | 2026-08-06 | never published |
 
-## Unreleased
+## 0.5.1 — Unreleased
+
+- Manage plugin packages through existing skill sources, review, templates and channel grants.
+  Compile native Claude hooks as an inline event map so SessionStart hooks execute correctly;
+  keep executable hooks restricted to authorized live admin turns.
+
+- Fix repeated native file creation and inline editing exhausting Slack’s modal stack. Successful
+  forms return to the existing browser/preview; Cancel and validation retain their prior behavior.
+
+- Fix the first browser editor/upload opening from Slack: narrowly scoped SameSite=Lax session
+  cookies survive the cross-site GET redirect while preserving CSRF, authorization and cookie
+  confidentiality protections.
+
+- Correct the bundled skill-authoring workflow: updates and change proposals accept only changed
+  files while retaining omitted files; complete packages are required for initial creation.
+
+- Correct Composio guidance that assumed the agent identity always belonged to other people or
+  was shared across every channel. Preserve account selection and no-substitution rules, including
+  when personal and agent connections reach the same underlying service owner.
+
+- Fix missing run identities in flat chats. Group-chat messages start separate sessions; quoting
+  user or bot messages resumes the original session, including after restart. Teams quotes support
+  both current entities and legacy Reply markup; personal chats remain continuous.
+
+- Make skill assignment rows compact, reveal descriptions and metadata on click, and give Active
+  skills and Add skills matching fixed heights with preserved scroll position when managing skills.
+
+- Make existing channel API/CLI credentials discoverable through a current names-only inventory
+  on non-Clean attempts, including resumed turns. Teach the operating guide to check credentials
+  alongside skills, CLI logins and selected-account MCPs before requesting another connection;
+  clarify runtime environment use without exposing values or silently changing accounts.
+
+- Improve conversation and template skill selection with a shared Active skills / Add skills
+  editor, name and source filters, locked inherited groups, and preserved explicit selections.
+
+- Clarify the Slack Skills categories and where each is configured. Org Skills explicitly
+  states that only admins can add or remove organization skills; combined lists are labelled
+  as automatic summaries.
+
+- Save instruction-update approvals with no deadline. The exact rule remains actionable across
+  restarts and is applied once on approval; changed instructions, destinations or permissions
+  require a fresh request. Other live engine permission/plan approvals retain their timeout.
+
+Next release version selected by the owner. Development continues on `beta`; full testing and
+explicit approval of the exact candidate are required before promotion to `main`. Earlier
+0.6.0 candidate tags and evidence below are retained as historical snapshots, not published releases.
 
 - Give selected optional Codex MCPs the existing 120-second remote startup budget and raise
   Claude's default initialize timeout to the same ceiling. Preserve explicit operator overrides,
@@ -76,7 +156,7 @@ product overview.
   the footer. Recompute after retries, recovery and fallback; never infer a provider model
   from an alias or an unexposed harness default.
 
-## 0.6.0-rc.2 — 2026-09-08 (release candidate)
+## 0.6.0-rc.2 — 2026-09-08 (superseded draft)
 
 Follow-up candidate for the installer findings from disposable Linux acceptance. Full live QA
 remains deferred; stable promotion is not approved.
@@ -92,7 +172,7 @@ remains deferred; stable promotion is not approved.
 - Add disposable Linux installation, encrypted backup/restore, real updater rollback and actual
   OS reboot checks; authenticated engine and chat acceptance remains a separate live gate.
 
-## 0.6.0-rc.1 — 2026-09-08 (release candidate)
+## 0.6.0-rc.1 — 2026-09-08 (superseded draft)
 
 Candidate source and build evidence for review. The GitHub Release remains a draft; the planned
 full live QA campaign is pending. This is not approval for stable-release promotion.

CONTRIBUTING.md

@@ -33,7 +33,7 @@ npm test                   # full node:test suite (test/*.test.js)
 npm run test:coverage      # the same suite with the enforced coverage floors — what CI runs
 npm run check:static       # syntax, undeclared identifiers, whitespace invariants
 npm run secret-scan        # dependency-free credential scan over tracked files
-npm run check:dco          # every commit in origin/main..HEAD carries a sign-off trailer
+npm run check:dco -- origin/beta..HEAD  # every development commit carries a sign-off trailer
 ```
 
 `npm run test:security-coverage` enforces the extra coverage floors on the security-critical
@@ -50,10 +50,15 @@ on ubuntu-latest.
 
 ## Branches and review
 
-Use your own fork, branch and isolated worktree. Start from the latest upstream main, make focused
-commits and open a PR with validation results. You do not need access to the publisher's GitHub
+Use your own fork, branch and isolated worktree. Start from the latest upstream `beta`, make focused
+commits and open a PR targeting `beta` with validation results. You do not need access to the publisher's GitHub
 account, private QA database or production host. Maintainers handle final integration and release.
 
+`beta` receives all completed development work. `main` is the stable update branch. A release PR
+from `beta` to `main` requires the full test and live acceptance evidence defined in `AGENTS.md`,
+followed by explicit user confirmation for that exact tested candidate. Beta work is not
+authorization to release; required checks that are blocked or unexecuted prevent promotion.
+
 Keep `FEATURES.md` and `TEST-PLAN.md` consistent with behavior. Include exact fixtures, setup,
 prompts/actions and pass rules for applicable Claude and Codex acceptance. Report live cases you
 could not execute explicitly so maintainers can run them; a local unit test is not a live pass.