Skip to content

v1.35.0

Choose a tag to compare

@github-actions github-actions released this 28 Oct 11:26
· 8 commits to main since this release

Added

  • Claude Code marketplace: the repository is a plugin marketplace (.claude-plugin/marketplace.json)
    with the d9c plugin in plugins/d9c: its manifest, an optional saved-host option and .mcp.json,
    which starts d9c mcp, so installing the plugin wires up the MCP server.
  • Agent skills: ten skills in plugins/d9c/skills in the open Agent Skills format, each
    usable through the CLI and the MCP tools: the base d9c (install, hosts, output and error
    contract, write policy, untrusted data) and d9c-troubleshoot, d9c-logs, d9c-lifecycle,
    d9c-compose (backup → pull → up → wait healthy → restore on failure), d9c-images,
    d9c-cleanup, d9c-fleet, d9c-security-audit (read-only) and d9c-net-storage. The MCP
    server serves all of them as prompts. Tests parse every CLI command a skill names with the real
    CLI parser and check every MCP tool, action and argument against the tool schemas.
  • d9c skills install: the skills are embedded in the binary; d9c skills install --target <agent>
    writes them into an agent's user-level skills directory (claude → ~/.claude/skills, agents/codex
    → ~/.agents/skills, gemini, cursor, copilot, opencode) or --dir <path> (e.g. a project's
    .claude/skills), stamped with the binary version in metadata.d9c-version; --dry-run reports
    created/updated/unchanged without writing, other skills in the directory are left alone.
    d9c skills ls lists the skills and targets.
  • Demo scenarios (-demo-scenario <name>, D9C_DEMO_SCENARIO): demo data with one planted
    problem per skill — oom, restart-loop, staging, unhealthy-compose, stale-images,
    disk-full, fleet, insecure, isolated-network (plus default) — in the TUI, the CLI and
    d9c mcp. Container and network inspect there has the real Docker layout. A scenario that
    exercises writes admits them up to its own tier, on the fake only; -read-only still wins.
    d9c skills ls lists them.
  • Skill evals: a claude plugin eval suite in plugins/d9c/evals (a case per skill plus a
    trigger-discipline case) runs the agent against the plugin's real MCP server on those scenarios
    (EVAL_D9C_SCENARIO), grading the diagnosis and the tool calls — including that destructive
    steps are only planned, never run without the user's approval. go test replays each skill's
    commands on its scenario and validates the suite for free.
  • CI checks for the plugin: a plugin job runs claude plugin validate --strict on the
    marketplace and the plugin; make check verifies the Agent Skills frontmatter (name = directory,
    description with "Use when", only format keys), unknown manifest keys, that every CLI command a
    skill names parses and every MCP tool/action/argument exists, and the eval suite.
  • README "For AI agents" / «Для ИИ-агентов»: the skills, installing the plugin and the skills for
    other agents, demo scenarios and evals.
  • Image commands for agents: image history <image> (read), image tag <source> <target>,
    image push <image>, image build <dir> [-t tag] (safe) and image rm <image> [-f] (destructive),
    in the CLI and the MCP tools (d9c_resources image_history, d9c_deploy image_build/image_tag/
    image_push, d9c_remove image_rm). Push credentials come only from D9C_REGISTRY_USERNAME /
    D9C_REGISTRY_PASSWORD; the plans name the registry, the containers using an image and a tag that
    moves.