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

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

@@ -1,4 +1,9 @@
-# Skill: Agent Client Protocol (ACP) — Rust Implementation
+---
+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.
+---
+
+# Agent Client Protocol
 
 ## 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.0.4}/.agents/skills/ai-assisted-coding/SKILL.md

@@ -1,4 +1,9 @@
-# Skill: AI-Assisted Coding Agents — Onde Inference Integration
+---
+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.
+---
+
+# AI-Assisted Coding
 
 ## 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.0.3 → sigit_code-1.0.4}/.agents/skills/branding/SKILL.md

@@ -1,4 +1,9 @@
-# Skill: Branding and naming reference
+---
+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
 

sigit_code-1.0.4/.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.0.4}/.agents/skills/tool-calling/SKILL.md

@@ -1,4 +1,9 @@
-# Skill: Tool Calling in siGit Code
+---
+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.
+---
+
+# Tool Calling
 
 ## 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.0.3 → sigit_code-1.0.4}/CHANGELOG.md

@@ -1,5 +1,15 @@
 # Changelog
 
+## 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 +153,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).*