chore(release): promote dev to main (v1.0.0)

.changeset/1494-templates-readme.md

@@ -0,0 +1,5 @@
+---
+"@bradygaster/squad-cli": patch
+---
+
+Add `.squad/templates/README.md` to init output explaining which files are runtime inputs vs bootstrap templates, and register the source template in the manifest. Closes #1494.

.changeset/1973-gh-aw-enlistment-credentials.md

@@ -0,0 +1,6 @@
+---
+"@bradygaster/squad-cli": patch
+"@bradygaster/squad-sdk": patch
+---
+
+Correct the `gh-aw-enlistment` skill's first-install guidance: `SQUAD_GITHUB_APP_PRIVATE_KEY` and `SQUAD_GITHUB_TOKEN` are names `gh aw add` reports as *referenced* for approval, not prerequisites. Neither secret needs to exist, and single-repo activation runs on the built-in `github.token`. The scaffolded skill previously listed them as a bare setup-time item, which led readers to conclude a PAT was required to enlist a repository.

.changeset/2056-doctor-remote-state-dir.md

@@ -0,0 +1,5 @@
+---
+"@bradygaster/squad-cli": patch
+---
+
+`squad doctor` now validates team state files (`team.md`, `routing.md`, `agents/`, `casting/registry.json`, `decisions.md`) against the resolved team root in remote (linked) mode instead of the local `.squad/` stub, which only holds `config.json`. Previously this caused false "file not found" failures for correctly configured `squad link` setups even though `squad status` and `squad cast` resolved the team fine. Fixes #2056.

.changeset/2106-windows-durable-casting.md

@@ -0,0 +1,5 @@
+---
+"@bradygaster/squad-sdk": patch
+---
+
+Fix `squad init` and team casting failing on Windows with `EPERM: operation not permitted, fsync`. The durable casting registry fsynced directory handles after each rename, which Windows rejects; directory flushes are now skipped on `win32`, where the file-level fsync is the only flush available. Also fixed the casting writer lock crashing with `EPERM ... rename` instead of waiting when another process already holds it on Windows, which reports a rename onto an existing directory as `EPERM` rather than POSIX `ENOTEMPTY`/`EEXIST`. Lock timeouts now name the last publish error, and releasing the lock retries briefly when Windows transiently rejects the directory rename (e.g. antivirus holding a freshly written file), instead of leaving a recovery guard that blocks later casting writers. If Windows still blocks deleting the released lock copy, release succeeds and a later release sweeps the leftover out of `.squad/casting/`.

.changeset/2107-linked-team-root-forms.md

@@ -0,0 +1,10 @@
+---
+"@bradygaster/squad-sdk": minor
+"@bradygaster/squad-cli": patch
+---
+
+Linked teams now work with either `teamRoot` form: the team repository (what `squad link` writes) or the team's `.squad/` directory (what the docs show). `resolveSquadPaths()` adds `teamSquadDir`, the team's squad directory for both forms, and `resolveSquadState()` roots local-backend storage there. `squad loop`/`watch`, `squad cast`, and the state MCP server read team state from `teamSquadDir`, so `squad loop` no longer reports "No squad found" for the docs form, and `squad_decide` no longer writes decisions outside `.squad/` for the `squad link` form. Closes #2107.
+
+`teamSquadDir` is a required field on the exported `ResolvedSquadPaths` type, so code that constructs that type must now set it. `@bradygaster/squad-sdk/tools` also exports `MUTABLE_STATE_PATHS` and `isMutableStateKey()`, the list of state paths that the state tools can write.
+
+If you linked a team with `squad link`: state that the state MCP server wrote to the team repo root (`decisions.md`, `decisions/inbox/`, `casting/policy.json`, `agents/*/history.md`, `log/`, `orchestration-log/`, `sessions/`, `.scratch/`, `identity/`) now belongs in `<team>/.squad/`. Squad does not move it. Run `squad doctor` to find leftovers. It lists the `.md` and `.json` files to move to the same relative path under `<team>/.squad/` (for example `<team>/identity/now.md` to `<team>/.squad/identity/now.md`), and the files that already exist there, which you must merge by hand without overwriting the newer state. Do not replace the existing `<team>/.squad/` directories. Skills that `squad_skill` wrote went to `.github/skills/` in the folder that contains the team repo; move any you want to keep to `<team>/.github/skills/`. Doctor does not check that folder.

.changeset/2155-heartbeat-fork-pr-labels.md

@@ -0,0 +1,10 @@
+---
+"@bradygaster/squad-cli": patch
+"@bradygaster/squad-sdk": patch
+---
+
+Fix `squad-heartbeat.yml`'s "Repair orphaned squad labels" step 403ing when a fork PR closes.
+
+`GITHUB_TOKEN` is forced read-only for `pull_request`-triggered workflow runs originating from a fork, regardless of the workflow's declared `permissions:` block, so `issues.addLabels` was rejected with `403 Resource not accessible by integration`. The trigger is switched to `pull_request_target` across all 5 synced copies (`.github/workflows/`, `templates/workflows/`, `packages/squad-cli/templates/workflows/`, `packages/squad-sdk/templates/workflows/`, `.squad-templates/workflows/`), which runs with base-repo token permissions regardless of fork origin.
+
+This is safe because the `actions/checkout` step never overrides `ref:` (always checks out the base ref, never the fork head), and no step reads or executes anything from the triggering PR's content.

.changeset/agent-identity-provenance.md

@@ -0,0 +1,25 @@
+---
+"@bradygaster/squad-sdk": minor
+"@bradygaster/squad-cli": minor
+---
+
+Publish and validate a versioned producer-owned agent identity provenance
+contract with stable IDs, rename preservation, retirement tombstones, and
+optional repository avatar references. Activation artifacts now carry a
+versioned repository-scoped work-to-agent binding linked to the exact registry
+revision, with explicit fail-closed omission, cross-row reconciliation, and
+stale-data semantics. Preset and CLI Cast registry updates now share an
+ABA-safe directory lock, and registry/history publication uses a durable
+manifest-backed roll-forward transaction plus a consistency-aware pair reader.
+Interrupted post-journal commits never roll back, while abandoned same-host
+locks recover only after the owner PID is definitively dead. Init and upgrade
+now create or migrate the same durable pair under that shared protocol, all
+production exporters and health readers reject split generations, legacy pairs
+migrate without an ABA window, and CLI Cast validates every casting input
+before its first filesystem mutation. Preset rollback now uses byte-identical
+compare-and-swap guards so concurrent external file and tree changes survive,
+and uncertain journal removal or directory fsync is reported as commit-in-doubt
+instead of success. These protocols provide process-crash consistency on
+filesystems with local atomic rename; power-loss durability additionally
+depends on successful file and parent directory fsync and the underlying
+platform and filesystem semantics.

.changeset/automate-release-distribution.md

@@ -0,0 +1,6 @@
+---
+'@bradygaster/squad-cli': patch
+'@bradygaster/squad-sdk': patch
+---
+
+Automate insider, preview, and stable distribution through npm, standalone archives, Homebrew, and WinGet, and update the packaged release guidance.

.changeset/automatic-squad-bootstrap.md

@@ -0,0 +1,8 @@
+---
+"@bradygaster/squad-cli": minor
+"@bradygaster/squad-sdk": minor
+---
+
+Install a dedicated seventh Agentic Workflow that automatically creates one
+validated draft Cast pull request and one linked research-proposals issue after
+the workflow installation lands on the repository's default branch.

.changeset/bright-gh-aw-central-ops.md

@@ -0,0 +1,6 @@
+---
+"@bradygaster/squad-cli": patch
+"@bradygaster/squad-sdk": patch
+---
+
+Require gh-aw v0.89.22 across the Squad workflow package, enlistment guidance, integrity contract, CI, and hosted E2E controller for central agentic ops compatibility. Validate isolated bootstrap candidates against the trusted checkout's Git history and create the candidate payload parent before writing so materialization can create the Cast PR and research issue.

.changeset/calm-casts-preserve-support.md

@@ -0,0 +1,6 @@
+---
+"@bradygaster/squad-cli": patch
+"@bradygaster/squad-sdk": patch
+---
+
+Keep built-in support identities and their canonical charters out of the routable cast roster, preserve the disabled Coding Agent section, and stop recreating retired per-agent history files during casts.

.changeset/casting-runtime-state.md

@@ -0,0 +1,6 @@
+---
+'@bradygaster/squad-cli': patch
+'@bradygaster/squad-sdk': patch
+---
+
+Allow the casting policy, registry, and history to be persisted through runtime state tools.

.changeset/coordinator-scope-persistence.md

@@ -0,0 +1,6 @@
+---
+"@bradygaster/squad-cli": patch
+"@bradygaster/squad-sdk": patch
+---
+
+Require coordinators to preserve user-approved scope and prevent directive or reflection capture from falling back to local Markdown proposals.

.changeset/dedicated-review-app.md

@@ -0,0 +1,12 @@
+---
+"@bradygaster/squad-cli": patch
+"@bradygaster/squad-sdk": patch
+---
+
+Use the base-controlled deterministic relay's native `Squad Review / review`
+job as the authoritative review result only when it validates the exact trusted
+automatic workflow run. Authoritative merge enforcement requires a source-bound
+required-workflow or equivalent ruleset; where that is unavailable, the context
+is advisory and an independent human approving review remains required. This
+path needs no separately provisioned reviewer App, token, private key, secret,
+environment, or custom Checks API publisher.

.changeset/exact-gh-aw-enlistment-version.md

@@ -0,0 +1,8 @@
+---
+"@bradygaster/squad-cli": patch
+"@bradygaster/squad-sdk": patch
+---
+
+Make public Squad gh-aw enlistment prove exact compiler version `v0.89.22`,
+cleanly reinstall the pinned extension on mismatch, and stop before generating
+repository artifacts when the supported version cannot be verified.

.changeset/fail-closed-gh-aw-resource-verification.md

@@ -0,0 +1,8 @@
+---
+"@bradygaster/squad-cli": patch
+"@bradygaster/squad-sdk": patch
+---
+
+Verify installed workflow resources against their trusted installer source binding,
+revision, ownership provenance, and canonical digest while preserving exact-byte
+verification for shared runtime and skill resources.

.changeset/fix-bootstrap-payload-transport.md

@@ -0,0 +1,7 @@
+---
+"@bradygaster/squad-cli": patch
+"@bradygaster/squad-sdk": patch
+---
+
+Transport automatic bootstrap Cast and research payloads through bounded,
+integrity-checked chunks so large validated payloads reach the typed writer.

.changeset/fix-bootstrap-triage-continuity.md

@@ -0,0 +1,8 @@
+---
+"@bradygaster/squad-cli": patch
+"@bradygaster/squad-sdk": patch
+---
+
+Make automatic bootstrap proposals immediately available to `/squad triage`
+after the linked Cast PR merges, and recognize the deterministic bootstrap Cast
+branch during team-required command gating.

.changeset/fix-router-author-binding.md

@@ -0,0 +1,6 @@
+---
+"@bradygaster/squad-cli": patch
+"@bradygaster/squad-sdk": patch
+---
+
+Bind mutating `/squad` command authorization to both the event actor and the author of the classified issue or comment text, preventing privileged edits from dispatching commands authored by an unprivileged user.

.changeset/fix-squad-command-relay-defects.md

@@ -0,0 +1,10 @@
+---
+"@bradygaster/squad-cli": patch
+"@bradygaster/squad-sdk": patch
+---
+
+Fixed three command-routing defects where a `/squad` command relayed by `squad-command-router.md` via `workflow_dispatch` (instead of arriving as a direct issue comment) could be silently dropped or mis-authorized:
+
+- The lifecycle-repair fallback in the shared `squad.md` coordinator only recognized exact, `/squad`-prefixed issue-comment bodies. A command normalized and relayed by the router (e.g. the bare `activate` dispatch input for a `/squad activate` comment) no longer matched, so terminal activation states went unrepaired. Repair gating and the effective command are now derived the same way for both the `issue_comment` and `workflow_dispatch` event paths.
+- `squad-command-router.md` was missing `roles: all`, so gh-aw's default write-role activation gate blocked the router from even running for non-write actors — including modes the router intentionally allows anyone to invoke (e.g. `status`). The router now declares `roles: all` and continues to enforce its own in-script, per-command authorization for mutating modes.
+- The router's relayed dispatch dropped the originating issue/comment context, so an embedded `/squad approve-improvement` command could never supply a real `approval_comment_id` and was rejected outright. The router now forwards an `aw_context` pointer (item type/number and originating comment id) through the dispatch, and the improvement-approval gate validates permission against that comment's own live author — never the dispatch actor — so approval binding is unchanged, not weakened.

.changeset/formalize-charter-profile.md

@@ -0,0 +1,5 @@
+---
+'@bradygaster/squad-sdk': minor
+---
+
+Add the draft `squad-charter/v0.1` artifact profile, explicit conformance profile selection, validation-before-runtime compilation, typed diagnostics and operation-exact capability metadata, canonical and lossless extension-preserving serialization, a schema-defined language-neutral conformance manifest with complete diagnostic coverage, and implementation-independent specification documents.

.changeset/gh-aw-compiled-expression.md

@@ -0,0 +1,8 @@
+---
+"@bradygaster/squad-cli": patch
+"@bradygaster/squad-sdk": patch
+---
+
+Keep the installed Squad agentic workflow valid at GitHub runtime by avoiding
+JSON-escaped operators inside compiled expressions, and add an emitted-lock
+verification gate to the enlistment guidance.

.changeset/gh-aw-enlistment-skill.md

@@ -0,0 +1,6 @@
+---
+"@bradygaster/squad-cli": patch
+"@bradygaster/squad-sdk": patch
+---
+
+Add the `gh-aw-enlistment` skill: an operationalized, safety-gated guide for enlisting a repository into Squad via GitHub Agentic Workflows (`gh aw`). It walks the supported install → strict-compile → validate → bootstrap-PR path, enforces an explicit safe-update allowlist (only the documented Squad secrets and `squad-init` action), keeps the default workflow token read-only, stages only documented surfaces, and never auto-merges.