teamai-cli 0.27.0-beta.1 → 0.27.0-beta.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "teamai-cli",
-  "version": "0.27.0-beta.1",
+  "version": "0.27.0-beta.2",
   "description": "TeamAI — Make Every Team AI Native (skill sync + shared knowledge base, powered by Git)",
   "type": "module",
   "bin": {

package/skill-data/core/SKILL.md

@@ -128,18 +128,20 @@ the copy and run `teamai pull --force`. The first pull after upgrading, and a
 new worktree's first pull, still overwrite: nothing is recorded yet.
 
 In project scope, `init` and `pull` also install a git hook in the repository's
-local git config (`hook.teamai-post-checkout`, `hook.teamai-post-merge`; Git
+local git config (`hook.teamai-post-checkout`, `hook.teamai-post-merge`, `hook.teamai-post-rewrite`; Git
 2.54+; older Git without `core.hooksPath` gets a marked block in `.git/hooks/`
 scripts, and with it `teamai doctor` advises), beside any `core.hooksPath` manager or `.git/hooks` script. When a
 worktree is created by `git worktree add` or an app that runs checkout hooks, it creates the project roots
 of `enabledAgents` (else the ones the main checkout has) and pulls into it before
 the command returns, from the team clone as last fetched when that was within
 24 h; a full pull then runs in the background. A branch switch does nothing.
-After `git pull` it fetches the team repo (5 s cap, then the background pull) and
+After `git pull` (merge or a completed rebase) it fetches the team repo (5 s cap, then the background pull) and
 delivers; in single-repo mode it delivers what `git pull` brought, offline. It prints nothing and always
 exits 0; a failure inside it is recorded, and `teamai doctor` names it (`Last git
 hook run failed: ...`) with its fix, as does the next interactive `teamai pull`, once.
-`teamai doctor` also reports whether the hook is installed, and why not.
+`teamai doctor` also reports whether the hooks are installed and enabled, with a
+reactivation command when Git disables a hook or event. Pull preserves explicit
+disablement. A conflicting rebase syncs only on completion; commit amend does not sync.
 `pull --dry-run` says when it would install or update the hook, writing nothing;
 `teamai uninstall` removes only teamai's hook entries and blocks. For hosts that
 skip checkout hooks, prepare the worktree before launch; see the new-worktree

package/skill-data/core/references/commands.md

@@ -125,7 +125,7 @@ Generated: do not edit by hand. Regenerate with
   - `teamai projects list` — List defined projects and the ones active in this directory
   - `teamai projects set [ids...]` — Set the projects active in this directory (comma-separated or repeated; empty to clear)
   - `teamai projects add <id>` — Add a project to manifest/projects.yaml, creating the file if needed (admin)
-    - `--namespaces <ns>` — Comma-separated namespaces for knowledge, skills, learnings and agents (e.g. common,checkout); env, hooks, mcp, models and docs are declared by hand
+    - `--namespaces <ns>` — Comma-separated namespaces for knowledge, skills, learnings and agents (e.g. common,checkout); env, hooks, mcp, models, docs and wiki are declared by hand
     - `--name <name>` — Display name for the project
     - `-d, --description <desc>` — Description for the project
   - `teamai projects update <id>` — Update a project in manifest/projects.yaml (admin)
@@ -295,9 +295,10 @@ Generated: do not edit by hand. Regenerate with
 
 ## contribute
 
-- `teamai contribute` — Contribute session knowledge to team repo
+- `teamai contribute` — Contribute session knowledge to team repo; projects list shows the default destination and allowed namespaces
   - `--file <path>` — Path to the contribution document
   - `--title <title>` — Title for the contribution document
+  - `--namespace <ns>` — Write to an active learnings namespace (default: the only active namespace, or the shared root when none or several are active)
   - `--session-id <id>` — Session ID for dedup tracking
   - `--scope <scope>` — Target scope: user or project
 

package/skill-data/core/references/troubleshooting.md

@@ -85,9 +85,12 @@ This is the #1 onboarding issue. In order:
 ## "Last git hook run failed: ..." / a new worktree lacks team resources
 
 In project scope, teamai's git hook syncs on `git worktree add` and `git pull`
+through merge or a completed rebase (`post-rewrite`, including `pull.rebase=true`; on Git 2.32
+and older, a fast-forward rebase with autostash syncs on `post-checkout`).
+A conflicting rebase syncs only on completion; `git commit --amend` does not sync. It runs
 silently and always exits 0, so its failures surface only here: `teamai doctor`
 names the last one with its fix, and the next interactive `teamai pull` says it
-once. The causes are a team repo fetch that failed or hit the 5 s post-merge
+once. The causes are a team repo fetch that failed or hit the 5 s git-pull hook
 cap without the background pull finishing it, and another teamai process
 holding the project's sync lock longer than the hook waits, or incomplete resource,
 hook or MCP delivery. Only a complete startup sync clears the recorded failure.
@@ -96,10 +99,14 @@ in the checkout (after a stuck pull ends, or once the team repo is reachable);
 `~/.teamai/debug.log` has the details. If doctor reports `Git hook syncs new
 worktrees and git pull` as failing, follow its fix: `teamai pull` installs it.
 Git older than 2.54 has no config hooks: teamai then adds a marked block to
-`.git/hooks/post-checkout` and `post-merge`, unless `core.hooksPath` is set (or a
+`.git/hooks/post-checkout`, `post-merge` and `post-rewrite`, unless `core.hooksPath` is set (or a
 hook there is a symlink or not an executable shell script), in which case doctor's fix says to upgrade Git
 or, if the team agrees, to commit its guarded `command -v teamai ... || true`
-line into the manager's post-checkout and post-merge hooks.
+line into the manager's post-checkout, post-merge and post-rewrite hooks.
+Doctor also detects hooks disabled by name (Git 2.54+) or event (Git 2.55+)
+in effective global, local or worktree config. Follow its command (`git config --local <key> true`,
+or `git config --worktree --unset <key>` for a worktree setting) to enable the named hook or event, then run `teamai pull` to sync. Pull preserves
+explicit disable settings, so reinstalling alone does not enable a disabled hook.
 Existing hook contents and permissions stay unchanged; read/write errors propagate
 from `init` and `hooks inject`, and Git-started pulls record them. An unreadable
 project config prevents sync and keeps its reason in `~/.teamai/debug.log`.
@@ -277,6 +284,14 @@ session's runs, recalled docs and adopted docs. Per agent:
 A read after the session's last Stop is credited at SubagentStop, at Copilot CLI's
 SessionEnd, or at the next `teamai pull`.
 
+## OpenCode V2 rejects the hooks plugin
+
+If OpenCode reports “Plugin must export a default definition”, upgrade TeamAI,
+run `teamai hooks inject` or `teamai pull`, and restart OpenCode. The generated
+built-in and enterprise plugins support both OpenCode 1.18.23 (`server`) and V2
+(`setup`). V1 shell recall uses `TEAMAI_AGENT_SESSION_ID`; V2 supplies its native
+`OPENCODE_SESSION_ID`.
+
 ## Still stuck
 
 - Re-run the failing command with `-v` / `--verbose` for detail.

package/skill-data/setup/references/manage-admin.md

@@ -134,14 +134,24 @@ teamai projects remove <id>  # remove a project
 
 A member gets the union of their role resources and their active project's
 resources. Admins declare projects in `manifest/projects.yaml` with the commands
-above, each of which opens a PR. Until #971 lands and restores the guard
-classification, `roles init/add/update/remove` and `projects add/update/remove`
-refuse `--dry-run` before pulling the team repo. After `projects remove`,
+above, each of which opens a PR. `roles init/add/update/remove` and
+`projects add/update/remove` support `--dry-run` without pulling the team repo.
+Clone previews use the contents after a real pull on the checked-out branch: an
+ahead branch stays ahead, a behind branch advances, and a diverged branch uses
+origin/current-branch. `roles init` preview checks that manifest before asking
+for overwrite confirmation. After `projects remove`,
 keep the project's content in the team repo until members have pulled: that is
 what lets their next pull clean up the copies they deployed.
 
+`roles init/add/update/remove` and `projects add/update/remove` previews, and resource removal
+previews, refuse a team clone with uncommitted changes. Commit or stash them before retrying. Single-repo
+previews still work with dirty business files because they read origin. Clone
+previews refresh the configured upstream first, even when its branch or remote
+name differs. A failed fast-forward or missing upstream uses origin/current-branch
+for the real reset fallback. Removal refuses when that refresh also fails.
+
 Every namespace that names a directory — `knowledge`, `skills`, `agents`, `env`,
-`hooks`, `mcp`, `models` and `docs` in either manifest, and `learnings` in `projects.yaml` (a role's `learnings:` is
+`hooks`, `mcp`, `models`, `docs` and `wiki` in either manifest, and `learnings` in `projects.yaml` (a role's `learnings:` is
 ignored and unchecked) — must be a single path segment: no `/`, `\`, `:` or control character, no trailing
 `.` or space, and not a Windows device name (`CON`, `NUL`, `COM1`, …). `team-codebase`
 cannot be a `docs` namespace (`docs/team-codebase/` is the legacy codebase output). Two
@@ -173,6 +183,12 @@ namespace, their next pull removes its docs that still match the team copy and
 keeps (and names) the ones they edited. Recall and `teamai doctor` follow the
 same filter.
 
+Wiki codebase slugs follow the same rule under `resources.wiki`: once any role
+or project lists a `teamwiki/evidence/code/<slug>/` slug there, `recall` only
+surfaces it for members with that namespace active; an undeclared slug stays
+shared. The slug is whatever `teamai codebase --project <slug>` wrote, not
+necessarily the project's manifest id.
+
 ## Team dashboard (web UI)
 
 ```bash
@@ -253,7 +269,7 @@ and push it with git. `teamai doctor` lists each override.
   and also set in `env.yaml` is a secret: its `env.yaml` value is not delivered. A
   secrets file that does not parse keeps `env.sh` and MCP servers as they were, and
   `teamai doctor` fails a check naming the file.
-- Have every member upgrade before declaring `env`, `hooks`, `mcp`, `models` or `docs` in a
+- Have every member upgrade before declaring `env`, `hooks`, `mcp`, `models`, `docs` or `wiki` in a
   manifest: teamai 0.25.0 and the 0.26.0 betas reject those keys and their pull stops.
 
 ## When sync fails

package/skill-data/setup/references/uninstall.md

@@ -102,9 +102,9 @@ and give it your team repo URL."*
 - If the user only wants to stop auto-sync for one tool but keep TeamAI otherwise,
   that is the `--agent <tool>` form, not a full uninstall.
 - In a project, uninstall also removes teamai's git hook: the
-  `hook.teamai-post-checkout` / `hook.teamai-post-merge` entries in the repo's git
-  config and the `# >>> teamai git hook` block in `.git/hooks/post-checkout` and
-  `post-merge`. Other hooks stay; a script left with only its shebang is deleted.
+  `hook.teamai-post-checkout`, `hook.teamai-post-merge` and `hook.teamai-post-rewrite` entries in the repo's git
+  config and the `# >>> teamai git hook` block in `.git/hooks/post-checkout`,
+  `post-merge` and `post-rewrite`. Other hooks stay; a script left with only its shebang is deleted.
 - In a project, uninstall also takes teamai's lines out of `.git/info/exclude`
   (the `# [teamai:mcp-exclude:start]` block) for MCP configs it proves hold no
   resolved `${VAR}` value. A line names the path a write lands in: for a config