teamai-cli 0.26.0-beta.4 → 0.26.0-beta.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "teamai-cli",
-  "version": "0.26.0-beta.4",
+  "version": "0.26.0-beta.5",
   "description": "TeamAI — Make Every Team AI Native (skill sync + shared knowledge base, powered by Git)",
   "type": "module",
   "bin": {
@@ -28,6 +28,7 @@
     "test:watch": "vitest",
     "test:coverage": "vitest run --coverage",
     "typecheck": "tsc --noEmit",
+    "lint": "oxlint --deny-warnings --report-unused-disable-directives",
     "release": "standard-version",
     "prepublishOnly": "npm run build"
   },
@@ -82,6 +83,7 @@
     "@vitest/coverage-v8": "^3.2.7",
     "fast-check": "^4.10.2",
     "opencode-ai": "1.18.23",
+    "oxlint": "1.85.0",
     "standard-version": "^9.5.0",
     "tsup": "^8.3.0",
     "typescript": "^5.7.0",

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

@@ -20,6 +20,7 @@ Generated: do not edit by hand. Regenerate with
 - `teamai init [repo]` — Initialize teamai (configure Git provider, clone repo, register member)
   - `--repo <repo>` — Team repo (alias of the positional argument)
   - `--http <url>` — Git-free HTTP team repo (read-only consumer; only needs an API key)
+  - `--provider <name>` — Git provider for the team repo on this machine: tgit, github, cnb, gitlab, gitcode, or git. Skips auto-detection. `git` uses your existing Git auth and needs no platform token, but opens no PR/MR.
   - `--self` — Single-repo mode: the current git repo is the team repo (equivalent to `teamai init .`). Knowledge lives on main under .teamai/; reports go to the teamai-reports orphan branch.
   - `--token <key>` — API key for HTTP team repo / status reporting (stored 0600, never committed). Also reads TEAMAI_API_TOKEN.
   - `--scope <scope>` — Install scope: project (default, <cwd>/.teamai + <cwd>/.claude) or user (~/.teamai + ~/.claude)

package/skill-data/core/references/contribute-member.md

@@ -116,6 +116,14 @@ The doc lands in the team's `learnings/` and appears for teammates on their next
 - Confirm it landed: `teamai list skills` (or `teamai status`).
 - Teammates receive it automatically on their next session, or via `teamai pull`.
 
+Before listing rules, `push` refreshes copies whose bodies still match a recorded
+sync revision. Copilot's generated `applyTo` header does not count as a local
+edit: unedited old instructions update in native format, including under
+`COPILOT_HOME` in user scope. Genuine local body edits remain push candidates.
+Rule pre-sync leaves tools excluded by `enabledAgents` or `disabledAgents` untouched.
+When only team `paths` change, `applyTo` refreshes if the local file still matches
+a recorded version's generated copy; locally edited headers are kept.
+
 ## If push is denied
 
 A permission error usually means you don't have write access to the team repo.

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

@@ -87,6 +87,9 @@ read -rs GITLAB_TOKEN && export GITLAB_TOKEN   # paste when prompted; api scope
 teamai init https://git.example.com/yourgroup/yourrepo
 ```
 
+A member who only syncs and never needs the CLI to open merge requests can skip
+both: `teamai init <url> --provider git` uses their existing Git authentication.
+
 ## Which tools actually get hooks
 
 `teamai hooks inject` prints **"Hooks injected into all AI tool settings"** even

package/skill-data/setup/references/join-member.md

@@ -58,7 +58,11 @@ Match the login to the URL's host (do NOT create a second repo):
   before continuing. (Headless/CI only: pre-set `GITHUB_TOKEN` — a token with `repo`
   scope — instead.)
 - **`gitlab.com/...`** or self-hosted GitLab → set `GITLAB_TOKEN` (and `GITLAB_URL`
-  for self-hosted, with `api` scope)
+  for self-hosted, with `api` scope). **Exception:** a member who only syncs and
+  never needs the CLI to open merge requests (typical for non-developers) can skip
+  the token: add `--provider git` to the `init` in Step 4. Git then uses their
+  existing SSH key or credential helper, and `push` leaves the MR for them to open
+  on the web.
 
 If they have no account on that platform, they register there, then ask the admin
 to add them to the repo.

package/skill-data/wiki/references/agents/kb-doc-generator.md

@@ -130,6 +130,7 @@ Use the `Glob → Grep → Read` three-step method (**adapt to the language of t
    Java:       *Application.java / *Bootstrap.java / src/main/java/**/Main*.java
    TypeScript: app.ts / index.ts / main.ts / server.ts
    Rust:       main.rs / src/main.rs
+   Swift:      main.swift / App.swift
    
 2. Grep: locate the core Handlers/Routers (choose the pattern by language + framework)
    Go:         grep -rn 'func.*Handler\|\.GET\|\.POST\|router\.\|@handler' <dir>

package/skill-data/wiki/references/methodology/phase0-collection.md

@@ -31,7 +31,7 @@ Before generating documents, build a code knowledge graph as an intermediate rep
 **Edge types**: `[CALLS]` (synchronous RPC/HTTP) / `[PUBLISHES]` (asynchronous MQ) / `[CONSUMES]` (MQ consumption) / `[READS]` (DB read) / `[WRITES]` (DB write) / `[CONFIGURES]` (config-driven) / `[MAPS_TO]` (product → code)
 
 **Construction methods** (ordered by availability):
-1. **`teamai codebase --extract`**: Tree-sitter structural edges (**TS/JS/Python/Go** and more) + multi-language heuristic fact pages (writes `teamwiki/`)
+1. **`teamai codebase --extract`**: Tree-sitter structural edges (**TS/JS/Python/Go/Swift** and more) + multi-language heuristic fact pages (writes `teamwiki/`)
 2. Grep + Read (Agent K1/K2): supplement dynamic routes and config-driven calls
 3. Parse orchestration configs → module → command mapping
 4. Parse Proto/IDL/DDL → data structures and table relationships (structured files, can be parsed precisely)

package/skill-data/wiki/references/overview.md

@@ -22,7 +22,7 @@ Architecture reverse-engineering **compresses the huge codebase into a structure
 - Every component relation carries a confidence label (`EXTRACTED` / `INFERRED` / `AMBIGUOUS`)
 - Every generation run produces accuracy statistics, with automatic warnings when thresholds are exceeded
 - AI reads the knowledge base instead of the source and gains global architecture awareness for **about 1/50 of the tokens**
-- In Phase 0, `teamai codebase --extract` can generate evidence-backed structural edges (TS/JS/Python/Go AST + multi-language heuristics)
+- In Phase 0, `teamai codebase --extract` can generate evidence-backed structural edges (TS/JS/Python/Go/Swift AST + multi-language heuristics)
 - After extraction, `teamai codebase --deep-enrich --project <slug> --output <repo>` can generate deterministic graph documents (G1/G2/G3) and deep knowledge; no separate team-wiki CLI is needed
 
 ---

package/skill-data/wiki/references/phases/phase0-init.md

@@ -95,7 +95,7 @@ Write to `_review/metadata.json`:
 
 **Step 0D: CLI structural baseline (per code repository, recommended)**
 
-Before the K1 deep read, use TeamAI to extract evidence-backed import/call structural edges (Python/Go/TS etc., `code-ast`) and merge them with the regex baseline (`code-heuristic`):
+Before the K1 deep read, use TeamAI to extract evidence-backed import/call structural edges (Python/Go/TS/Swift etc., `code-ast`) and merge them with the regex baseline (`code-heuristic`):
 
 ```bash
 # For each repo. Writes <repo>/teamwiki/ (evidence pages + .indices/graph-index.json).

package/skill-data/wiki/scripts/scan_repo.py

@@ -53,7 +53,7 @@ KEY_FILE_PATTERNS = {
 # Language extension map
 LANG_MAP = {
     ".py": "Python", ".go": "Go", ".js": "JavaScript", ".ts": "TypeScript",
-    ".java": "Java", ".rs": "Rust", ".rb": "Ruby", ".php": "PHP",
+    ".java": "Java", ".rs": "Rust", ".swift": "Swift", ".rb": "Ruby", ".php": "PHP",
     ".c": "C", ".cpp": "C++", ".h": "C/C++ Header",
     ".proto": "Protobuf", ".thrift": "Thrift", ".graphql": "GraphQL",
     ".sql": "SQL", ".sh": "Shell", ".bash": "Shell",