sigit-code 1.0.3__tar.gz → 1.1.0__tar.gz

{sigit_code-1.0.3 → sigit_code-1.1.0}/.agents/skills/agent-client-protocol/SKILL.md

@@ -1,3 +1,8 @@
+---
+name: agent-client-protocol
+description: Implement or debug Agent Client Protocol (ACP) support in Rust for siGit Code. Use when working on ACP JSON-RPC over stdio, the agent-client-protocol crate, session or prompt handlers, streaming notifications, or editor integration.
+---
+
 # Skill: Agent Client Protocol (ACP) — Rust Implementation
 
 ## Overview
@@ -311,4 +316,4 @@ Editor                          Agent
 10. **Never write to stdout except JSON-RPC** — any library that prints to
     stdout (`mistralrs` model metadata, stray `println!`, whatever) will
     corrupt the wire. Redirect diagnostics to stderr. If a dependency writes
-    to stdout internally, fix it or suppress it before shipping.
+    to stdout internally, fix it or suppress it before shipping.

{sigit_code-1.0.3 → sigit_code-1.1.0}/.agents/skills/ai-assisted-coding/SKILL.md

@@ -1,3 +1,8 @@
+---
+name: ai-assisted-coding
+description: Build or maintain AI-assisted coding features in Rust using Onde Inference. Use when working on ChatEngine integration, model loading, streaming inference, history management, sampling config, or local coding-agent architecture.
+---
+
 # Skill: AI-Assisted Coding Agents — Onde Inference Integration
 
 ## Overview
@@ -358,4 +363,4 @@ For sandboxed environments (iOS, tvOS, Android):
 6. **Forgetting that `generate()` doesn't update history** — use it for
    one-shot enhancements (prompt expansion, code review) that shouldn't pollute
    the main conversation. Use `send_message()` / `stream_message()` for the
-   primary turn loop.
+   primary turn loop.

sigit_code-1.1.0/.agents/skills/branding/SKILL.md

@@ -0,0 +1,203 @@
+---
+name: branding
+description: Keep siGit Code branding, naming, and package references consistent. Use when editing docs, release notes, UI copy, package metadata, setup guides, or any prose that mentions the product, CLI, company, or Onde Inference.
+---
+
+# Branding
+
+## Overview
+
+Use this file when writing docs, release notes, UI copy, package metadata, or setup guides for this repository.
+
+The short version:
+
+- **Product / brand name:** `siGit Code`
+- **CLI command:** `sigit`
+- **Rust crate:** `sigit`
+- **npm package:** `@smbcloud/sigit`
+- **PyPI package:** `sigit-code`
+- **Company name:** `smbCloud`
+- **LLM backend name:** `Onde Inference`
+
+The most common mistake is mixing the product name with the command name.
+
+
+---
+
+# Branding: siGit Code naming and voice
+
+Use this skill when you are writing docs, release notes, UI copy, package descriptions, setup guides, or anything else user-facing in this repo.
+
+The main job is simple: keep the names straight.
+
+## The name map
+
+These names are case-sensitive.
+
+- **Product / brand:** `siGit Code`
+- **CLI command:** `sigit`
+- **Rust crate:** `sigit`
+- **Repository slug:** `getsigit/sigit`
+- **npm package:** `@smbcloud/sigit`
+- **PyPI package:** `sigit-code`
+- **Company:** `smbCloud`
+- **LLM backend in prose:** `Onde Inference`
+- **Rust crate for the backend:** `onde`
+- **Protocol acronym:** `ACP`
+- **Long form when needed:** `Agent Client Protocol (ACP)`
+
+## First rule
+
+When you mean the product, write **`siGit Code`** exactly like that.
+
+Correct:
+
+- `siGit Code is a local coding agent.`
+- `siGit Code works in Zed over ACP.`
+- `siGit Code shares its model cache with the desktop app on macOS.`
+
+Wrong:
+
+- `Sigit Code`
+- `SiGit Code`
+- `siGit`
+- `sigit Code`
+- `SIGIT`
+
+Do not shorten the product name to just `siGit` in docs or marketing copy unless there is a very specific reason and the sentence still reads clearly.
+
+## Second rule
+
+When you mean something users type, install, import, or clone, use the literal lowercase name.
+
+That means:
+
+- `sigit` for the command, crate, and repo slug
+- `@smbcloud/sigit` for npm
+- `sigit-code` for PyPI
+- `onde` for the Rust crate
+
+Examples:
+
+- Run `sigit` in a terminal.
+- Install with `cargo install sigit`.
+- Install with `npm install -g @smbcloud/sigit`.
+- Install with `pip install sigit-code`.
+- The repository is `getsigit/sigit`.
+
+A good gut-check:
+
+> If this is the thing a user types or installs, keep the literal package or command name.
+> If this is the thing you are describing, use the branded product name.
+
+## Preferred wording
+
+Keep the prose plain and direct.
+
+Prefer:
+
+- `siGit Code is a local coding agent.`
+- `siGit Code runs on your machine.`
+- `siGit Code works with any codebase.`
+- `Install siGit Code with Cargo:`
+- `To start siGit Code, run `sigit`.`
+
+Avoid:
+
+- `siGit is a local coding agent.`
+- `sigit is a coding assistant.`
+- `The siGit product...`
+- inflated marketing language that makes the copy sound generic
+
+If a sentence feels awkward because of the brand name, rewrite the sentence. Do not change the name.
+
+## Editor setup rules
+
+In UI-facing examples, the visible label should stay `siGit Code`.
+The executable should stay `sigit`.
+
+Example:
+
+```/dev/null/branding-example.json#L1-8
+{
+  "agent_servers": {
+    "siGit Code": {
+      "type": "custom",
+      "command": "/absolute/path/to/sigit"
+    }
+  }
+}
+```
+
+The same rule applies in VS Code ACP examples, screenshots, panel labels, and release notes.
+
+## Other names that must stay exact
+
+### smbCloud
+
+Always write `smbCloud` with lowercase `smb` and uppercase `C`.
+
+Wrong:
+
+- `SMBCloud`
+- `SmbCloud`
+- `smbcloud`
+
+### Onde Inference
+
+Use `Onde Inference` when you mean the product or project.
+Use `onde` when you mean the Rust crate.
+
+Examples:
+
+- `siGit Code uses Onde Inference as its local LLM backend.`
+- `The Rust dependency is `onde`.`
+
+### ACP
+
+Use `ACP` for the acronym.
+Use `Agent Client Protocol (ACP)` on first mention when the long form helps.
+
+## Humanizing without breaking branding
+
+If you are also cleaning up AI-ish writing, preserve every case-sensitive name exactly as written.
+
+That includes:
+
+- `siGit Code`
+- `smbCloud`
+- `Onde Inference`
+- `ACP`
+- `sigit`
+- `@smbcloud/sigit`
+- `sigit-code`
+- `onde`
+
+Do not "smooth out" a brand name. Do not re-case package names to make a sentence look nicer. Rewrite around them.
+
+## Quick checklist
+
+Before you finish any doc or release-note edit, check these:
+
+1. Did you use `siGit Code` when referring to the product?
+2. Did you keep `sigit` lowercase for commands, crates, and repo references?
+3. Did you keep `@smbcloud/sigit` and `sigit-code` exact?
+4. Did you keep `smbCloud` and `Onde Inference` cased correctly?
+5. In setup examples, does the visible editor label say `siGit Code` while the command stays `sigit`?
+
+## Fast replacements
+
+Common fixes:
+
+- `siGit is` -> `siGit Code is`
+- `siGit works` -> `siGit Code works`
+- `siGit knows` -> `siGit Code knows`
+- `On macOS, siGit` -> `On macOS, siGit Code`
+- `Sigit` -> usually `siGit Code` or `sigit`, depending on context
+
+When in doubt, ask one question:
+
+> Am I talking about the product, or the literal thing a user types?
+
+If it is the product, use `siGit Code`.
+If it is the command or package, use the exact lowercase name.

sigit_code-1.1.0/.agents/skills/sigit-code-release/SKILL.md

@@ -0,0 +1,57 @@
+---
+name: sigit-code-release
+description: Prepare and verify siGit Code releases. Use when bumping versions, checking Cargo, npm, or PyPI package metadata, validating release notes, confirming CI readiness, or assembling a release checklist for a new siGit Code version.
+---
+
+# siGit Code Release
+
+Use this skill when preparing a release for this repository.
+
+## Focus areas
+
+- Keep the branded product name as `siGit Code` in prose and `sigit` for commands, crate names, repo paths, and package identifiers.
+- Verify version consistency across release surfaces, but respect which files are real sources of truth versus generated or release-time rewritten artifacts.
+- Check release-facing docs such as `README.md`, `CHANGELOG.md`, workflow notes, and package metadata for stale version references or incorrect naming.
+- Validate the local release path pragmatically: formatting, linting, targeted tests, and any repo-specific release checks that matter for the requested version.
+
+## Working approach
+
+1. Read the files that define the release version and distribution metadata before proposing any changes.
+2. Treat `Cargo.toml` as the primary release version source for the Rust crate and the PyPI package in this repository.
+3. Check how the release workflows rewrite or derive versions before editing checked-in npm or Python metadata.
+4. Prefer targeted verification commands that match CI or packaging workflows already present in the repository.
+5. Report blockers clearly: failed checks, version mismatches, missing changelog entries, or unpublished packaging changes.
+
+## Repo-specific release rules
+
+- Bump the crate version in `Cargo.toml`.
+- Update the root `sigit` package entry in `Cargo.lock` when the crate version changes.
+- Add or update the top changelog entry in `CHANGELOG.md` for the release being cut.
+- Do not treat `npm/sigit/package.json` `0.0.0-dev` as a bug by default. The npm release workflow rewrites it at publish time using `npm/scripts/render-main-package.cjs` and the release tag.
+- Do not add a hardcoded version to `pypi/pyproject.toml` for normal releases. PyPI uses `maturin` with `dynamic = ["version"]` and derives the published package version from `Cargo.toml`.
+- Release workflows are tag-driven. `release-github.yml`, `release-npm.yml`, and `release-pypi.yml` all derive `RELEASE_VERSION` from a `v*.*.*` tag or a manually supplied tag input.
+
+## Typical files to inspect
+
+- `Cargo.toml`
+- `Cargo.lock`
+- `CHANGELOG.md`
+- `README.md`
+- `npm/sigit/package.json`
+- `npm/scripts/render-main-package.cjs`
+- `npm/`
+- `pypi/`
+- `.github/workflows/`
+
+## Release checklist
+
+- Version bump is applied everywhere it needs to be.
+- `Cargo.toml` and the root crate entry in `Cargo.lock` match.
+- `CHANGELOG.md` has a correct top entry for the new release.
+- `npm/sigit/package.json` is left at `0.0.0-dev` unless the packaging flow itself changed.
+- `pypi/pyproject.toml` still uses dynamic versioning unless there is a deliberate packaging change.
+- Release workflows still derive their version from the tag as expected.
+- Release notes or changelog entries match the actual changes.
+- CI-equivalent local checks pass for the relevant platform or target.
+- Package names, install commands, and branding stay consistent.
+- Any known release limitations are called out explicitly.

{sigit_code-1.0.3 → sigit_code-1.1.0}/.agents/skills/tool-calling/SKILL.md

@@ -1,3 +1,8 @@
+---
+name: tool-calling
+description: Implement or debug tool calling in siGit Code across the app, Onde Inference, and mistral.rs. Use when working on tool schemas, execution loops, model support, session cwd handling, or tool-call troubleshooting.
+---
+
 # Skill: Tool Calling in siGit Code
 
 ## Overview
@@ -287,4 +292,4 @@ The `qwen3_8b()` constructor only exists in the local Onde SDK until it's pushed
 | `sigit/src/setup.rs` | HF cache setup pointing to shared App Group container |
 | `onde/src/inference/types.rs` | `ToolDefinition`, `ToolCallRequest`, `ToolResult`, `ToolAwareResult` |
 | `onde/src/inference/engine.rs` | `send_message_with_tools()`, `send_tool_results()`, `attach_tools()`, `parse_tool_calls()`, `replay_history_with_tools()`, `GgufModelConfig::qwen3_8b()` |
-| `onde/src/inference/models.rs` | Model constants and `SUPPORTED_MODELS` array |
+| `onde/src/inference/models.rs` | Model constants and `SUPPORTED_MODELS` array |

sigit_code-1.1.0/.github/workflows/release-crates.yml

@@ -0,0 +1,70 @@
+name: Crates.io Release
+
+on:
+  push:
+    tags:
+      - "v*.*.*"
+  workflow_dispatch:
+    inputs:
+      tag:
+        description: "Release tag (e.g. v1.0.2)"
+        required: true
+
+permissions:
+  contents: read
+
+env:
+  CARGO_TERM_COLOR: always
+
+jobs:
+  publish:
+    name: Publish to crates.io
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v6
+        with:
+          ref: ${{ github.event.inputs.tag || github.ref }}
+
+      - name: Read Rust toolchain
+        shell: bash
+        run: |
+          rust_toolchain="$(sed -n 's/^channel = "\(.*\)"/\1/p' rust-toolchain.toml | head -n 1)"
+          if [ -z "$rust_toolchain" ]; then
+            echo "Failed to read Rust toolchain from rust-toolchain.toml" >&2
+            exit 1
+          fi
+          echo "RUST_TOOLCHAIN=${rust_toolchain}" >> "$GITHUB_ENV"
+
+      - name: Install Rust toolchain
+        uses: dtolnay/rust-toolchain@3c5f7ea28cd621ae0bf5283f0e981fb97b8a7af9
+        with:
+          toolchain: ${{ env.RUST_TOOLCHAIN }}
+
+      - name: Setup Rust cache
+        uses: Swatinem/rust-cache@v2
+        with:
+          key: crates-publish
+
+      - name: Check whether version already exists on crates.io
+        id: crates-check
+        shell: bash
+        run: |
+          VERSION=$(cargo metadata --no-deps --format-version 1 | \
+            python3 -c "import sys,json; pkgs=json.load(sys.stdin)['packages']; \
+            print(next(p['version'] for p in pkgs if p['name']=='sigit'))")
+          echo "version=${VERSION}" >> "$GITHUB_OUTPUT"
+
+          if curl -fsS "https://crates.io/api/v1/crates/sigit/${VERSION}" >/dev/null 2>&1; then
+            echo "sigit ${VERSION} already exists on crates.io, skipping publish"
+            echo "exists=true" >> "$GITHUB_OUTPUT"
+          else
+            echo "exists=false" >> "$GITHUB_OUTPUT"
+          fi
+
+      - name: Publish to crates.io
+        if: steps.crates-check.outputs.exists != 'true'
+        env:
+          CARGO_REGISTRY_TOKEN: ${{ secrets.CARGO_REGISTRY_TOKEN }}
+        run: cargo publish --locked

{sigit_code-1.0.3 → sigit_code-1.1.0}/CHANGELOG.md

@@ -1,5 +1,25 @@
 # Changelog
 
+## 1.1.0
+
+Bumps the ACP SDK to v0.13 and pulls in updated dependencies.
+
+### What changed
+
+- Updated `agent-client-protocol` from v0.11 to v0.13
+- Updated `onde` to 1.1.2
+- Refreshed branding and skill metadata
+
+## 1.0.4
+
+This release tightens up the terminal experience and finishes a few release-facing cleanup items.
+
+### What changed
+
+- Added bold rich-text rendering in the TUI for assistant replies, so `**text**` now displays with terminal styling instead of raw markdown markers
+- Refreshed the bundled skill metadata to follow the current Agent Skills `SKILL.md` format
+- Synced the crate release metadata for the `1.0.4` cut
+
 ## 1.0.3
 
 This is the cleanup release for the editor-side startup problems.
@@ -143,4 +163,4 @@ ACP and editor mode work on Windows. The part that is still missing is the inter
 
 ---
 
-*© 2026 [smbCloud](https://smbcloud.xyz/) (Splitfire AB).*
+*© 2026 [smbCloud](https://smbcloud.xyz/) (Splitfire AB).*