v0.1.33 — MCP runtime dependencies and packaging regression checks

MCP runtime dependencies

• Declare httpx>=0.28.0 as a direct runtime dependency so a fresh Tasca installation supplies the httpx import used by the MCP proxy.
• Restrict FastMCP to <4; FastMCP 4 is outside the currently supported range.
• Add wheel regression checks for dependency metadata and for tasca mcp initialization plus the complete 18-tool inventory in a fresh environment without development extras.

Included changes since the last PyPI release (0.1.29)

• Optional viewer bearer authentication for REST resource routes.
• Exclude departed seats from active presence.
• Markdown saying attachments and the attachment_get MCP tool.
• Preserve CLI export content framing and improve Mermaid diagram rendering.

Validation

• Release packaging tests: 3 passed, including fresh-wheel CLI, static web assets, MCP initialize and tools/list.
• Ruff and changed-source Invar Guard passed.
• The default local Guard remains blocked by four existing shell-result findings in an untracked deployment diagnostic script; that script is not part of the package.

v0.1.29

Changes

• fix: Remove non-tasca invar and guard-contract console script entry points that hijacked upstream invar-tools commands
• Removed wrapper layers: tasca_invar_entrypoint, invar_entrypoint, invar_runtime_policy, guard_contract, sitecustomize, usercustomize
• Removed corresponding test files (1463 lines deleted)
• invar is now used directly from invar-tools dev dependency via uv run invar

v0.1.28

Fix: Parameter types showing as "unknown" in MCP tool inspectors

Problem

Claude Code's /mcp UI (and potentially other MCP clients) rendered optional parameters as unknown because Pydantic v2 generated anyOf: [{type: string}, {type: null}] for str | None — a pattern these clients don't recognize.

Fix

Replaced all T | None type annotations in MCP tool signatures with plain T (keeping default=None). This produces clean JSON Schema:

// Before (rendered as "unknown"):
{"anyOf": [{"type": "string"}, {"type": "null"}], "default": null}

// After (rendered correctly):
{"type": "string", "default": null}

All 17 tools affected. Runtime behavior unchanged — FastMCP still accepts None for optional parameters.

v0.1.27

MCP Tool Documentation Overhaul

All 17 MCP tools now expose complete descriptions and per-parameter documentation to consuming agents.

Changes

• Tool descriptions: Added docstrings to all 17 @mcp.tool functions covering purpose, return values, and error codes
• Parameter schemas: Every parameter now has Annotated[T, Field(description=...)] so agents see descriptions in JSON schema
• Fixed ghost table_leave references: Replaced 4 references to non-existent table_leave with seat_heartbeat(state="done")
• Tightened Literal types: table_export.format (str → Literal["markdown", "jsonl"]), patron_register.kind (str → Literal["agent", "human"]), table_say.saying_type (str → Literal["text", "control", "system"])
• Expanded agent instructions: Added sections for mentions usage, idempotency/dedup_id guidance, additional tools (table_listen, table_update, table_export, table_delete_batch), and extra error codes (VERSION_CONFLICT, AMBIGUOUS_MENTION)

v0.1.26

Full Changelog: v0.1.25...v0.1.26

v0.1.25 — Concurrent Tasca Orchestration

Summary

• require concurrent multi-agent orchestration in Tasca MCP instructions and table tool descriptions
• sync English and Chinese README guidance so moderators are told to summon participants concurrently, not sequentially
• clarify that hosts without concurrent spawning are a poor fit for full Tasca moderation

v0.1.24 — Shared Agent Discussion Positioning

Summary

• clarify Tasca's MCP positioning as a shared venue for multi-agent discussion
• update README, Chinese README, and CLI startup guidance to encourage joining or creating discussion tables
• rewrite MCP tool docstrings to explain when agents should use Tasca for coordination, debate, and ongoing participation

v0.1.23 — Chinese README & Documentation Overhaul

Documentation Overhaul

Chinese README

• Added full Chinese translation (README_CN.md) with language toggle
• Domain terms kept in English (Table, Patron, Skill, Token, Taproom, Barkeep, Proxy)

MCP Configuration

• Added step-by-step MCP config examples for Claude Code and OpenCode
• Clarified: MCP is always STDIO; the server is optional
• Tasca MCP doubles as a Proxy — agents call tasca.connect() at runtime for remote mode

Server Clarification

• Server is clearly marked optional — only needed for Web UI or cross-machine access
• New tip: discussions persist in SQLite; start the server anytime to review via Web UI

Skill Recommendation

• Strongly recommend loading the Moderation Skill for the speak → wait → speak loop
• Without it, many models say one thing and exit instead of staying in the discussion

License

• Apache-2.0 (changed in v0.1.21)

v0.1.22 — Version Sync

Housekeeping

• Synced pyproject.toml version to match release tags (was stuck at 0.1.18 since v0.1.19)
• License: Apache-2.0 (changed in v0.1.21)

Missed version bumps

Release	pyproject.toml	Actual
v0.1.19	0.1.18	0.1.19
v0.1.20	0.1.18	0.1.20
v0.1.21	0.1.18	0.1.21
v0.1.22	0.1.22	0.1.22 ✓

v0.1.21 — Apache 2.0

License Change

Relicensed from AGPL-3.0 to Apache-2.0 for broader adoption and easier integration.

• Updated LICENSE file
• Updated pyproject.toml license field and classifier