kyro-ai 3.2.0

package/.claude-plugin/README.md

@@ -0,0 +1,29 @@
+# Kyro Claude Code Adapter
+
+This directory packages Kyro for Claude Code. Kyro itself is a portable, markdown-first workflow kit for AI coding agents; this adapter registers its commands, orchestrator, and skills in Claude Code.
+
+## Installation
+
+### Via Marketplace
+
+```bash
+/plugin marketplace add SynapSync/kyro-ai
+/plugin install kyro-ai@kyro-ai
+```
+
+Or via CLI:
+
+```bash
+claude plugin marketplace add SynapSync/kyro-ai
+claude plugin install kyro-ai@kyro-ai
+```
+
+### Local Install
+
+```bash
+claude --plugin-dir /path/to/kyro-ai
+```
+
+## Documentation
+
+See the main [README](../README.md) and [agent adapters guide](../docs/agent-adapters.md) for the portable workflow contract and non-Claude setup paths.

package/.claude-plugin/marketplace.json

@@ -0,0 +1,52 @@
+{
+  "name": "kyro-ai",
+  "owner": {
+    "name": "SynapSync",
+    "email": "synapsync@proton.me"
+  },
+  "metadata": {
+    "description": "Claude Code adapter for Kyro, a portable sprint workflow kit for AI coding agents"
+  },
+  "plugins": [
+    {
+      "name": "kyro-ai",
+      "source": "./",
+      "description": "Claude Code adapter for Kyro: one orchestrator agent, 3 slash commands, 2 skills, markdown artifacts, and formal debt tracking.",
+      "author": {
+        "name": "SynapSync"
+      },
+      "homepage": "https://synapsync.dev/cognitives/kyro-ai",
+      "repository": "https://github.com/SynapSync/kyro-ai",
+      "license": "Apache-2.0",
+      "keywords": [
+        "ai-agents",
+        "agent-workflow",
+        "llm-workflow",
+        "agentic-development",
+        "markdown-workflow",
+        "claude-code",
+        "workflow",
+        "sprint",
+        "planning",
+        "agents",
+        "adaptive",
+        "debt-tracking",
+        "self-correction",
+        "worktrees",
+        "orchestration"
+      ],
+      "category": "workflow",
+      "tags": [
+        "workflow",
+        "sprint",
+        "planning",
+        "agents",
+        "commands",
+        "productivity",
+        "debt-tracking",
+        "self-correction",
+        "orchestration"
+      ]
+    }
+  ]
+}

package/.claude-plugin/plugin.json

@@ -0,0 +1,40 @@
+{
+  "name": "kyro-ai",
+  "version": "3.2.0",
+  "description": "Claude Code adapter for Kyro, a portable sprint workflow kit for AI coding agents",
+  "author": {
+    "name": "SynapSync",
+    "email": "synapsync@proton.me"
+  },
+  "homepage": "https://synapsync.dev/cognitives/kyro-ai",
+  "repository": "https://github.com/SynapSync/kyro-ai",
+  "license": "Apache-2.0",
+  "keywords": [
+    "ai-agents",
+    "agent-workflow",
+    "llm-workflow",
+    "agentic-development",
+    "markdown-workflow",
+    "claude-code",
+    "workflow",
+    "sprint",
+    "planning",
+    "execution",
+    "debt-tracking",
+    "roadmap",
+    "iterative",
+    "adaptive",
+    "agents",
+    "self-correction",
+    "worktrees",
+    "context-persistence"
+  ],
+  "skills": [
+    "./skills/sprint-forge",
+    "./skills/qa-review"
+  ],
+  "agents": [
+    "./agents/orchestrator.md"
+  ],
+  "commands": ["./commands/"]
+}

package/.claude-plugin/settings.json

@@ -0,0 +1,16 @@
+{
+  "$schema": "https://json.schemastore.org/claude-code-settings.json",
+  "permissions": {
+    "allow": [
+      "Read",
+      "Glob",
+      "Grep",
+      "Bash(git status)",
+      "Bash(git diff *)",
+      "Bash(git log *)",
+      "Bash(npm run build)",
+      "Bash(npm run typecheck)",
+      "Bash(git worktree *)"
+    ]
+  }
+}

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,331 @@
+<p align="center">
+  <h1 align="center">Kyro AI</h1>
+</p>
+
+<p align="center">
+  <a href="https://github.com/SynapSync/kyro-ai/stargazers"><img src="https://img.shields.io/github/stars/SynapSync/kyro-ai?style=for-the-badge&logo=github&color=D97757&labelColor=1e1e2e" alt="Stars"/></a>
+  <a href="https://www.npmjs.com/package/kyro-ai"><img src="https://img.shields.io/npm/v/kyro-ai?style=for-the-badge&logo=npm&color=E8926F&labelColor=1e1e2e" alt="npm"/></a>
+  <a href="https://github.com/SynapSync/kyro-ai/blob/main/LICENSE"><img src="https://img.shields.io/badge/license-Apache--2.0-22c55e?style=for-the-badge&labelColor=1e1e2e" alt="License"/></a>
+  <a href="https://github.com/SynapSync/kyro-ai/actions/workflows/ci.yml"><img src="https://img.shields.io/github/actions/workflow/status/SynapSync/kyro-ai/ci.yml?style=for-the-badge&logo=githubactions&logoColor=white&label=CI&labelColor=1e1e2e" alt="CI"/></a>
+</p>
+
+<p align="center">
+  <b>Multi-agent sprint harness for AI coding agents.</b><br/>
+  One install command &bull; portable markdown core &bull; command skills &bull; project-local state &bull; agent adapters
+</p>
+
+---
+
+## What Kyro AI Does
+
+Kyro AI installs a project-local workflow harness that helps AI coding agents analyze, plan, execute, review, and close software work through repeatable sprint cycles.
+
+It is designed for teams that switch between agents and do not want every agent to relearn the workflow from a giant prompt.
+
+Kyro gives agents:
+
+- a **managed core** with orchestrator, command, skill, and template instructions
+- **command-like skills** such as `kyro-forge`, `kyro-status`, and `kyro-wrap-up`
+- **workspace state** that tracks installed adapters and future scopes
+- **human-readable artifacts** for roadmaps, phase documents, debt, retros, and re-entry context
+- **doctor/sync/uninstall commands** so setup can be validated instead of guessed
+
+---
+
+## Quick Start
+
+Install Kyro AI into the current project:
+
+```bash
+npx kyro-ai install --agent opencode,codex --scope workspace --yes
+npx kyro-ai doctor
+```
+
+Use one agent only if needed:
+
+```bash
+npx kyro-ai install --agent opencode --scope workspace --yes
+npx kyro-ai install --agent codex --scope workspace --yes
+```
+
+After install, open your agent and invoke the installed Kyro command skill:
+
+```text
+kyro-forge auth-refactor
+```
+
+Other installed command skills:
+
+```text
+kyro-status
+kyro-wrap-up
+```
+
+If the host exposes slash commands, the equivalent public command namespace is:
+
+```text
+/kyro:forge
+/kyro:status
+/kyro:wrap-up
+```
+
+---
+
+## Installed Workspace Layout
+
+A workspace install writes Kyro into `.agents/`:
+
+```text
+.agents/
+├── kyro/
+│   ├── internal/
+│   │   ├── core/
+│   │   │   ├── agents/
+│   │   │   ├── config.json
+│   │   │   └── WORKFLOW.yaml
+│   │   ├── commands/
+│   │   ├── skills/
+│   │   │   ├── sprint-forge/
+│   │   │   └── qa-review/
+│   │   ├── KYRO.md
+│   │   ├── kyro.json
+│   │   └── manifest.json
+│   └── scopes/
+│       └── {scope}/
+│           ├── state.json
+│           ├── ROADMAP.md
+│           └── phases/
+└── skills/
+    ├── kyro-forge/SKILL.md
+    ├── kyro-status/SKILL.md
+    └── kyro-wrap-up/SKILL.md
+```
+
+Important invariant: `kyro install` creates the root project state at `.agents/kyro/internal/kyro.json`. It does **not** create `.agents/kyro/scopes/{scope}/state.json`; scoped state belongs to future scope/forge creation.
+
+---
+
+## Who Invokes Whom
+
+```text
+User
+  ↓
+kyro / kyro-ai CLI
+  ↓
+installs managed core + adapter projections
+  ↓
+agent opens the project
+  ↓
+agent discovers AGENTS.md and/or .agents/skills
+  ↓
+user invokes kyro-forge / kyro-status / kyro-wrap-up
+  ↓
+projected skill reads .agents/kyro/internal/commands/*.md
+  ↓
+orchestrator reads .agents/kyro/internal/core/agents/orchestrator.md
+  ↓
+sprint-forge skill assets guide the workflow
+  ↓
+artifacts are written under .agents/kyro/scopes/{scope}/
+```
+
+The user should not have to explain the workflow in natural language. If an agent cannot discover the installed command skills, that agent needs a better adapter.
+
+---
+
+## CLI Reference
+
+Kyro AI exposes two equivalent bins:
+
+```bash
+kyro
+kyro-ai
+```
+
+Commands:
+
+| Command          | Purpose                                                            |
+| ---------------- | ------------------------------------------------------------------ |
+| `kyro`           | Open the basic interactive configuration TUI                       |
+| `kyro install`   | Install managed core and selected agent adapters                   |
+| `kyro doctor`    | Validate package health, workspace state, core files, and adapters |
+| `kyro sync`      | Refresh managed assets without rewriting unmanaged files           |
+| `kyro uninstall` | Remove managed workspace assets                                    |
+
+Common usage:
+
+```bash
+kyro install --agent opencode,codex --scope workspace --yes
+kyro doctor
+kyro sync --agent codex --dry-run
+kyro uninstall --dry-run
+```
+
+Supported install adapters today:
+
+| Adapter    | Status                            | What it installs                                                      |
+| ---------- | --------------------------------- | --------------------------------------------------------------------- |
+| `opencode` | Implemented                       | `.agents/skills/kyro-*` command skill projections                     |
+| `codex`    | Implemented                       | `.agents/skills/kyro-*` plus a managed Kyro block in root `AGENTS.md` |
+| `claude`   | Planned for CLI workspace install | Claude plugin remains first-class through `.claude-plugin/`           |
+| `cursor`   | Planned                           | Not installed by the CLI yet                                          |
+
+There is intentionally no `generic` adapter. Cross-agent instructions belong in root `AGENTS.md`; install adapters should target concrete agent capabilities.
+
+---
+
+## Core Workflow
+
+Kyro has three stable workflow intents:
+
+| Intent  | Skill / command                  | What it does                                                    |
+| ------- | -------------------------------- | --------------------------------------------------------------- |
+| Forge   | `kyro-forge` / `/kyro:forge`     | Analyze, plan, execute, review, and close a sprint cycle        |
+| Status  | `kyro-status` / `/kyro:status`   | Report project progress, roadmap health, and technical debt     |
+| Wrap-up | `kyro-wrap-up` / `/kyro:wrap-up` | Close a session, update handoff context, and preserve learnings |
+
+Forge follows this lifecycle:
+
+```text
+Detect project state
+  → analyze codebase or scope
+  → build/update roadmap
+  → generate the next sprint
+  → implement task by task
+  → review quality and debt
+  → write retro, handoff, and re-entry context
+```
+
+Kyro is intentionally sprint-by-sprint. It should not pre-generate a huge static plan and pretend reality will follow it.
+
+---
+
+## Architecture
+
+The source package is organized around portable markdown instructions plus a small deterministic CLI:
+
+```text
+kyro-ai/
+├── src/cli/                 # installer, doctor, sync, uninstall, adapters
+├── agents/                  # orchestrator instruction
+├── commands/                # forge, status, wrap-up command definitions
+├── skills/
+│   ├── sprint-forge/        # main workflow skill and assets
+│   └── qa-review/           # senior QA review skill
+├── docs/                    # architecture, CLI, adapter, and command docs
+├── rules/                   # reusable operating rules
+├── templates/               # context templates
+├── .claude-plugin/          # Claude plugin adapter packaging
+├── WORKFLOW.yaml
+└── config.json
+```
+
+Runtime contract:
+
+| Layer           | Responsibility                                                                |
+| --------------- | ----------------------------------------------------------------------------- |
+| CLI             | Install, sync, uninstall, validate, and project managed files                 |
+| Adapter         | Translate Kyro into each agent's native/compatible instruction surface        |
+| Projected skill | Give the agent a short command entrypoint without duplicating lifecycle prose |
+| Orchestrator    | Coordinate phases, gates, review, debugging, and handoff                      |
+| Sprint Forge skill | Define workflow modes, helpers, templates, and discipline rules |
+| Artifacts       | Persist roadmap, phases, debt, retros, and re-entry context in markdown       |
+
+---
+
+## Claude Plugin Support
+
+Claude remains first-class.
+
+The Claude plugin adapter lives in `.claude-plugin/` and is shipped with the package. The CLI workspace installer does not replace the Claude plugin; it complements it for agents that need workspace-local command skills and `AGENTS.md` instructions.
+
+Claude plugin install:
+
+```bash
+/plugin marketplace add SynapSync/kyro-ai
+/plugin install kyro-ai@kyro-ai
+```
+
+Local plugin development:
+
+```bash
+git clone https://github.com/SynapSync/kyro-ai.git
+cd kyro-ai
+npm install
+npm run build
+claude --plugin-dir /path/to/kyro-ai
+```
+
+---
+
+## Development
+
+Requirements:
+
+- Node.js 18+
+- npm
+
+Useful commands:
+
+```bash
+npm ci
+npm run check
+npm run build
+npm pack --dry-run
+```
+
+`npm run check` runs:
+
+- TypeScript typecheck
+- package/plugin/workflow version validation
+- relative markdown link validation
+
+Release tags publish to npm through GitHub Actions when the tag matches `package.json.version`:
+
+```bash
+git tag v3.2.0
+git push origin v3.2.0
+```
+
+The release workflow expects the repository secret `NPM_TOKEN`.
+
+---
+
+## Documentation
+
+| Guide                                            | Description                                              |
+| ------------------------------------------------ | -------------------------------------------------------- |
+| [CLI](docs/cli.md)                               | Installer, doctor, sync, uninstall, and adapter commands |
+| [Commands Reference](docs/commands-reference.md) | `/kyro:*` command semantics                              |
+| [Architecture](docs/architecture.md)             | System architecture and data flow                        |
+| [Agent Adapters](docs/agent-adapters.md)         | Adapter setup and host-specific notes                    |
+| [Harness Migration](docs/harness-migration.md)   | Direction for the multi-agent runtime                    |
+| [Getting Started](docs/getting-started.md)       | Introductory workflow guide                              |
+| [Rules Guide](docs/rules-guide.md)               | Persistent learning rules                                |
+| [Context Management](docs/context-management.md) | Re-entry prompts and continuity strategy                 |
+| [Programmatic Usage](docs/programmatic-usage.md) | Using Kyro instructions from custom LLM apps             |
+
+---
+
+## Philosophy
+
+1. **Commands over prose** — users should invoke workflows, not explain them repeatedly.
+2. **Markdown remains the collaboration layer** — humans and agents can inspect the same artifacts.
+3. **The CLI owns deterministic checks** — package health should not depend on prompt discipline.
+4. **Adapters are concrete** — each supported agent gets the files it actually knows how to use.
+5. **One sprint at a time** — each cycle adapts from evidence, retro, and technical debt.
+6. **Claude stays first-class** — multi-agent support does not mean retiring the Claude plugin.
+
+---
+
+<p align="center">
+  <br/>
+  <b>If this helps your AI coding workflow, star the repo so other builders can find it.</b>
+  <br/><br/>
+  <a href="https://github.com/SynapSync/kyro-ai/stargazers"><img src="https://img.shields.io/github/stars/SynapSync/kyro-ai?style=for-the-badge&logo=github&color=D97757&labelColor=1e1e2e" alt="Stars"/></a>
+  <br/><br/>
+  <a href="https://github.com/SynapSync/kyro-ai/issues">Report Issues</a> &bull;
+  <a href="https://synapsync.dev">SynapSync</a>
+  <br/><br/>
+  <sub>Built by <a href="https://github.com/SynapSync">SynapSync</a> — a practical harness for multi-agent software delivery.</sub>
+</p>