kd-cli 2.0.4__tar.gz → 2.0.5__tar.gz

kd_cli-2.0.5/PKG-INFO

@@ -0,0 +1,166 @@
+Metadata-Version: 2.4
+Name: kd-cli
+Version: 2.0.5
+Summary: Knowledge dispatcher for live knowledge systems
+Author: Sergiy Gladkyy
+License-Expression: MIT
+Keywords: youtrack,cli,sdk,knowledge-management,knowledge-network
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: POSIX
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Topic :: Utilities
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: httpx>=0.27
+Requires-Dist: pydantic>=2.0
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: tabulate>=0.9
+Provides-Extra: dev
+Requires-Dist: pytest>=7.0; extra == "dev"
+Requires-Dist: pytest-httpx>=0.30; extra == "dev"
+Requires-Dist: ruff>=0.1.0; extra == "dev"
+Requires-Dist: mypy>=1.0; extra == "dev"
+Requires-Dist: pre-commit>=3.0; extra == "dev"
+Requires-Dist: types-PyYAML; extra == "dev"
+Requires-Dist: types-tabulate; extra == "dev"
+Dynamic: license-file
+
+# kd
+
+**Knowledge Dispatcher.** A command-line and Python tool for accessing and managing information that lives in issue trackers and knowledge bases — designed to be equally natural for humans and large language models.
+
+Today kd speaks **YouTrack**. On the roadmap: **JIRA**, **GitHub Issues**, **GitLab**, and possibly **Obsidian**. One tool, one set of verbs, many backends.
+
+## What kd does
+
+- **Full issue CRUD from the terminal or a script.** Create, update, comment, link, time-log, assign, query — no web UI round-trips, no ad-hoc REST glue.
+- **Knowledge-base article workflows.** Idempotent `push` from local markdown, `pull` as markdown for editing, moves across projects, tag-driven queries. Articles round-trip cleanly through an HTML-comment marker so repeated LLM-driven edits preserve upstream identity instead of creating duplicates.
+- **Cross-project visibility via tokens.** kd sees exactly what the token's connection permits on the upstream server — nothing more, nothing less. Access control stays upstream where it belongs, not in a parallel local config.
+- **Cross-entity search** spanning issues and articles in a single query.
+- **Structured output** (JSON, YAML, table, markdown) because the primary consumer is often another program — an LLM, a shell pipeline, a CI job — not a human eyeballing a terminal.
+
+## The primer — and why it exists
+
+The **primer** (`kd /primer`) is the centerpiece: a small, workspace-local file of pinned references and curated notes that every kd session can surface on demand.
+
+It exists to solve a problem that has gotten worse as LLMs have become central to real work:
+
+- **Visible memory.** Agentic tools accumulate hidden "memories" in opaque per-LLM buckets you cannot easily read, edit, or audit. The primer is a plain file you can open, version, and review. If an LLM appears to "remember" something load-bearing, you can see exactly where that came from.
+- **LLM-portable.** One primer works for any model. Switch from Claude to GPT-5 to the next generation — the primer travels with the project, not with a vendor.
+- **Shared by humans and LLMs.** A developer jotting "on this project the sprint field is called `Board`" in the primer is building the same artifact an LLM would build, in the same place, readable by both. No separate convention to maintain.
+- **A routing layer, not a copy.** The primer can pin real knowledge-base articles (`kd /primer/article add FB-A-42`). It never duplicates their content — it points at them. The rest of kd extends this shape: pull what the current task needs from live systems, reason, push updates back. Nothing gets mirrored into a parallel store.
+
+## What kd is not
+
+- **Not a migration platform.** Cross-system moves are deliberate lossy cherry-picks — a stub on the target side with a backref to the source, not a faithful reproduction.
+- **Not a data warehouse.** Data lives in the upstream tracker; kd sits on top.
+- **Not a faithful replica.** kd reads what a task needs and writes what actually changed. It never claims to be a complete mirror.
+
+If you need a migration tool or a comprehensive import/export platform, kd is the wrong tool.
+
+## Install
+
+```bash
+# pipx (recommended)
+pipx install kd-cli
+
+# or uv
+uv tool install kd-cli
+```
+
+The PyPI distribution name is `kd-cli` (two-letter `kd` is reserved by PyPI policy). The installed command, the import name, and the CLI entry point are all `kd`.
+
+## Configure
+
+```bash
+# Scaffold a project-local config in the current directory.
+kd init
+
+# Or set via environment (overrides workspace + global config).
+export KD_TOKEN=your_token
+export KD_CONNECTION=main
+```
+
+Global config lives at `~/.config/kd/config.yaml`; workspace config lives at `.kd/config.yaml`.
+
+## Usage
+
+### CLI
+
+```bash
+# Projects
+kd /project list
+kd /project show FB
+
+# Issues
+kd /issue list --project FB --query "#Unresolved"
+kd /issue create "Fix router configuration" -p FB --type Task
+kd /issue show FB-1
+
+# Time tracking
+kd /time log FB-1 45 --type Development --description "Router reconfiguration"
+
+# Articles
+kd /article list --project CMCSA
+kd /article push guide.md --project CMCSA --title "Setup Guide" --tag "type:guide"
+kd /article pull FB-A-42 > setup.md
+
+# Tags
+kd /tag list
+kd /tag articles type:case --project CMCSA
+
+# Saved queries
+kd /query list
+kd /query issues "Sprint 47" --project FB
+
+# Primer (workspace knowledge, LLM context)
+kd /primer/note add "Sprint field is called 'Board'"
+kd /primer/article add FB-A-42 --summary "Architecture Overview"
+kd /primer show
+
+# Cross-entity search
+kd /search "router" --types issue,article --project FB
+
+# Output formats
+kd /project list --output json | jq '.[].key'
+kd /issue list --output yaml
+```
+
+### Python SDK
+
+The CLI is a thin wrapper over a Python library. Same capabilities, programmatic interface:
+
+```python
+from kd import YouTrackClient
+
+client = YouTrackClient(
+    url="https://your-instance.youtrack.cloud",
+    token="your_token",
+)
+
+projects = client.projects.list()
+issue = client.issues.create(project="FB", summary="Fix router config")
+client.time.log(issue_id="FB-1", minutes=45, work_type="Development")
+articles = client.tags.articles(["type:case"], project="CMCSA")
+results = client.search.search("router", types=["issue", "article"])
+```
+
+## Development
+
+```bash
+pytest tests/ -v --tb=short
+
+ruff format kd/ tests/
+ruff check --fix kd/ tests/
+mypy kd/
+```
+
+---
+Updated: 2026-04-14

kd_cli-2.0.5/README.md

@@ -0,0 +1,132 @@
+# kd
+
+**Knowledge Dispatcher.** A command-line and Python tool for accessing and managing information that lives in issue trackers and knowledge bases — designed to be equally natural for humans and large language models.
+
+Today kd speaks **YouTrack**. On the roadmap: **JIRA**, **GitHub Issues**, **GitLab**, and possibly **Obsidian**. One tool, one set of verbs, many backends.
+
+## What kd does
+
+- **Full issue CRUD from the terminal or a script.** Create, update, comment, link, time-log, assign, query — no web UI round-trips, no ad-hoc REST glue.
+- **Knowledge-base article workflows.** Idempotent `push` from local markdown, `pull` as markdown for editing, moves across projects, tag-driven queries. Articles round-trip cleanly through an HTML-comment marker so repeated LLM-driven edits preserve upstream identity instead of creating duplicates.
+- **Cross-project visibility via tokens.** kd sees exactly what the token's connection permits on the upstream server — nothing more, nothing less. Access control stays upstream where it belongs, not in a parallel local config.
+- **Cross-entity search** spanning issues and articles in a single query.
+- **Structured output** (JSON, YAML, table, markdown) because the primary consumer is often another program — an LLM, a shell pipeline, a CI job — not a human eyeballing a terminal.
+
+## The primer — and why it exists
+
+The **primer** (`kd /primer`) is the centerpiece: a small, workspace-local file of pinned references and curated notes that every kd session can surface on demand.
+
+It exists to solve a problem that has gotten worse as LLMs have become central to real work:
+
+- **Visible memory.** Agentic tools accumulate hidden "memories" in opaque per-LLM buckets you cannot easily read, edit, or audit. The primer is a plain file you can open, version, and review. If an LLM appears to "remember" something load-bearing, you can see exactly where that came from.
+- **LLM-portable.** One primer works for any model. Switch from Claude to GPT-5 to the next generation — the primer travels with the project, not with a vendor.
+- **Shared by humans and LLMs.** A developer jotting "on this project the sprint field is called `Board`" in the primer is building the same artifact an LLM would build, in the same place, readable by both. No separate convention to maintain.
+- **A routing layer, not a copy.** The primer can pin real knowledge-base articles (`kd /primer/article add FB-A-42`). It never duplicates their content — it points at them. The rest of kd extends this shape: pull what the current task needs from live systems, reason, push updates back. Nothing gets mirrored into a parallel store.
+
+## What kd is not
+
+- **Not a migration platform.** Cross-system moves are deliberate lossy cherry-picks — a stub on the target side with a backref to the source, not a faithful reproduction.
+- **Not a data warehouse.** Data lives in the upstream tracker; kd sits on top.
+- **Not a faithful replica.** kd reads what a task needs and writes what actually changed. It never claims to be a complete mirror.
+
+If you need a migration tool or a comprehensive import/export platform, kd is the wrong tool.
+
+## Install
+
+```bash
+# pipx (recommended)
+pipx install kd-cli
+
+# or uv
+uv tool install kd-cli
+```
+
+The PyPI distribution name is `kd-cli` (two-letter `kd` is reserved by PyPI policy). The installed command, the import name, and the CLI entry point are all `kd`.
+
+## Configure
+
+```bash
+# Scaffold a project-local config in the current directory.
+kd init
+
+# Or set via environment (overrides workspace + global config).
+export KD_TOKEN=your_token
+export KD_CONNECTION=main
+```
+
+Global config lives at `~/.config/kd/config.yaml`; workspace config lives at `.kd/config.yaml`.
+
+## Usage
+
+### CLI
+
+```bash
+# Projects
+kd /project list
+kd /project show FB
+
+# Issues
+kd /issue list --project FB --query "#Unresolved"
+kd /issue create "Fix router configuration" -p FB --type Task
+kd /issue show FB-1
+
+# Time tracking
+kd /time log FB-1 45 --type Development --description "Router reconfiguration"
+
+# Articles
+kd /article list --project CMCSA
+kd /article push guide.md --project CMCSA --title "Setup Guide" --tag "type:guide"
+kd /article pull FB-A-42 > setup.md
+
+# Tags
+kd /tag list
+kd /tag articles type:case --project CMCSA
+
+# Saved queries
+kd /query list
+kd /query issues "Sprint 47" --project FB
+
+# Primer (workspace knowledge, LLM context)
+kd /primer/note add "Sprint field is called 'Board'"
+kd /primer/article add FB-A-42 --summary "Architecture Overview"
+kd /primer show
+
+# Cross-entity search
+kd /search "router" --types issue,article --project FB
+
+# Output formats
+kd /project list --output json | jq '.[].key'
+kd /issue list --output yaml
+```
+
+### Python SDK
+
+The CLI is a thin wrapper over a Python library. Same capabilities, programmatic interface:
+
+```python
+from kd import YouTrackClient
+
+client = YouTrackClient(
+    url="https://your-instance.youtrack.cloud",
+    token="your_token",
+)
+
+projects = client.projects.list()
+issue = client.issues.create(project="FB", summary="Fix router config")
+client.time.log(issue_id="FB-1", minutes=45, work_type="Development")
+articles = client.tags.articles(["type:case"], project="CMCSA")
+results = client.search.search("router", types=["issue", "article"])
+```
+
+## Development
+
+```bash
+pytest tests/ -v --tb=short
+
+ruff format kd/ tests/
+ruff check --fix kd/ tests/
+mypy kd/
+```
+
+---
+Updated: 2026-04-14

{kd_cli-2.0.4 → kd_cli-2.0.5}/kd/cli/core/namespaces.py

@@ -66,7 +66,7 @@ class NamespaceRegistry:
     """Root of the namespace tree. Resolves token sequences to commands."""
 
     def __init__(self) -> None:
-        self.root = Namespace("kd", "YouTrack CLI and SDK")
+        self.root = Namespace("kd", "Knowledge Dispatcher for issue trackers and knowledge bases")
 
     def register_namespace(self, namespace: Namespace) -> None:
         """Place a namespace in the tree by its path.

{kd_cli-2.0.4 → kd_cli-2.0.5}/kd/cli/main.py

@@ -476,7 +476,7 @@ def _show_reference(
     Generated from command metadata — always in sync with the code.
     Designed for LLM consumption: one output, full coverage.
     """
-    print(f"kd {__version__} — YouTrack CLI and SDK")
+    print(f"kd {__version__} — Knowledge Dispatcher for issue trackers and knowledge bases")
     print()
 
     # Global options line — generated from declarations
@@ -575,7 +575,7 @@ def _show_discovery(namespace: Namespace, *, file: Any = None) -> None:
     if namespace.path:
         print(f"kd /{namespace.path}", file=file)
     else:
-        print("kd — YouTrack CLI and SDK", file=file)
+        print("kd — Knowledge Dispatcher for issue trackers and knowledge bases", file=file)
     print(file=file)
 
     if namespace.sub_namespaces:

{kd_cli-2.0.4 → kd_cli-2.0.5}/kd/cli/namespaces/__init__.py

@@ -34,5 +34,5 @@ def register_all_namespaces(registry: NamespaceRegistry) -> None:
     registry.register_namespace(create_user_namespace())
     registry.register_namespace(create_time_namespace())
 
-    # Apply built-in command synonyms (YTCTL-8)
+    # Apply built-in command synonyms (KDCLI-8)
     apply_synonyms(registry.root, load_synonyms())

{kd_cli-2.0.4 → kd_cli-2.0.5}/kd/client.py

@@ -1000,7 +1000,7 @@ class ArticleOperations:
         """Fetch an article and return its content with a fresh marker.
 
         The server does not store ``upstream-updated`` inside article
-        content (see YTCTL-6); pull injects it from ``article.updated``
+        content (see KDCLI-6); pull injects it from ``article.updated``
         so a pull -> edit -> push round-trip does not trip the conflict
         check.  Marker-less content passes through verbatim.  Malformed
         markers pass through verbatim so the user can see and fix them.
@@ -1246,7 +1246,7 @@ class ArticleOperations:
 
         # Step 7: build outgoing content. `upstream-updated` is intentionally
         # omitted from the server payload — storing a snapshot of `updated`
-        # inside the content creates an unsolvable chicken-and-egg (YTCTL-6).
+        # inside the content creates an unsolvable chicken-and-egg (KDCLI-6).
         # `pull` injects it from `article.updated` on read.
         if existing_remote is not None:
             marker.set("upstream-id", existing_remote.id_readable)

{kd_cli-2.0.4 → kd_cli-2.0.5}/kd/resources/command-synonyms.yaml

@@ -4,7 +4,7 @@
 # Applied globally to any namespace that has the canonical command
 # but does not already define a command with the synonym name.
 #
-# Keep this set small and curated. See YTCTL-8.
+# Keep this set small and curated. See KDCLI-8.
 
 - synonym: get
   canonical: show

kd_cli-2.0.5/kd_cli.egg-info/PKG-INFO

@@ -0,0 +1,166 @@
+Metadata-Version: 2.4
+Name: kd-cli
+Version: 2.0.5
+Summary: Knowledge dispatcher for live knowledge systems
+Author: Sergiy Gladkyy
+License-Expression: MIT
+Keywords: youtrack,cli,sdk,knowledge-management,knowledge-network
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: POSIX
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Topic :: Utilities
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: httpx>=0.27
+Requires-Dist: pydantic>=2.0
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: tabulate>=0.9
+Provides-Extra: dev
+Requires-Dist: pytest>=7.0; extra == "dev"
+Requires-Dist: pytest-httpx>=0.30; extra == "dev"
+Requires-Dist: ruff>=0.1.0; extra == "dev"
+Requires-Dist: mypy>=1.0; extra == "dev"
+Requires-Dist: pre-commit>=3.0; extra == "dev"
+Requires-Dist: types-PyYAML; extra == "dev"
+Requires-Dist: types-tabulate; extra == "dev"
+Dynamic: license-file
+
+# kd
+
+**Knowledge Dispatcher.** A command-line and Python tool for accessing and managing information that lives in issue trackers and knowledge bases — designed to be equally natural for humans and large language models.
+
+Today kd speaks **YouTrack**. On the roadmap: **JIRA**, **GitHub Issues**, **GitLab**, and possibly **Obsidian**. One tool, one set of verbs, many backends.
+
+## What kd does
+
+- **Full issue CRUD from the terminal or a script.** Create, update, comment, link, time-log, assign, query — no web UI round-trips, no ad-hoc REST glue.
+- **Knowledge-base article workflows.** Idempotent `push` from local markdown, `pull` as markdown for editing, moves across projects, tag-driven queries. Articles round-trip cleanly through an HTML-comment marker so repeated LLM-driven edits preserve upstream identity instead of creating duplicates.
+- **Cross-project visibility via tokens.** kd sees exactly what the token's connection permits on the upstream server — nothing more, nothing less. Access control stays upstream where it belongs, not in a parallel local config.
+- **Cross-entity search** spanning issues and articles in a single query.
+- **Structured output** (JSON, YAML, table, markdown) because the primary consumer is often another program — an LLM, a shell pipeline, a CI job — not a human eyeballing a terminal.
+
+## The primer — and why it exists
+
+The **primer** (`kd /primer`) is the centerpiece: a small, workspace-local file of pinned references and curated notes that every kd session can surface on demand.
+
+It exists to solve a problem that has gotten worse as LLMs have become central to real work:
+
+- **Visible memory.** Agentic tools accumulate hidden "memories" in opaque per-LLM buckets you cannot easily read, edit, or audit. The primer is a plain file you can open, version, and review. If an LLM appears to "remember" something load-bearing, you can see exactly where that came from.
+- **LLM-portable.** One primer works for any model. Switch from Claude to GPT-5 to the next generation — the primer travels with the project, not with a vendor.
+- **Shared by humans and LLMs.** A developer jotting "on this project the sprint field is called `Board`" in the primer is building the same artifact an LLM would build, in the same place, readable by both. No separate convention to maintain.
+- **A routing layer, not a copy.** The primer can pin real knowledge-base articles (`kd /primer/article add FB-A-42`). It never duplicates their content — it points at them. The rest of kd extends this shape: pull what the current task needs from live systems, reason, push updates back. Nothing gets mirrored into a parallel store.
+
+## What kd is not
+
+- **Not a migration platform.** Cross-system moves are deliberate lossy cherry-picks — a stub on the target side with a backref to the source, not a faithful reproduction.
+- **Not a data warehouse.** Data lives in the upstream tracker; kd sits on top.
+- **Not a faithful replica.** kd reads what a task needs and writes what actually changed. It never claims to be a complete mirror.
+
+If you need a migration tool or a comprehensive import/export platform, kd is the wrong tool.
+
+## Install
+
+```bash
+# pipx (recommended)
+pipx install kd-cli
+
+# or uv
+uv tool install kd-cli
+```
+
+The PyPI distribution name is `kd-cli` (two-letter `kd` is reserved by PyPI policy). The installed command, the import name, and the CLI entry point are all `kd`.
+
+## Configure
+
+```bash
+# Scaffold a project-local config in the current directory.
+kd init
+
+# Or set via environment (overrides workspace + global config).
+export KD_TOKEN=your_token
+export KD_CONNECTION=main
+```
+
+Global config lives at `~/.config/kd/config.yaml`; workspace config lives at `.kd/config.yaml`.
+
+## Usage
+
+### CLI
+
+```bash
+# Projects
+kd /project list
+kd /project show FB
+
+# Issues
+kd /issue list --project FB --query "#Unresolved"
+kd /issue create "Fix router configuration" -p FB --type Task
+kd /issue show FB-1
+
+# Time tracking
+kd /time log FB-1 45 --type Development --description "Router reconfiguration"
+
+# Articles
+kd /article list --project CMCSA
+kd /article push guide.md --project CMCSA --title "Setup Guide" --tag "type:guide"
+kd /article pull FB-A-42 > setup.md
+
+# Tags
+kd /tag list
+kd /tag articles type:case --project CMCSA
+
+# Saved queries
+kd /query list
+kd /query issues "Sprint 47" --project FB
+
+# Primer (workspace knowledge, LLM context)
+kd /primer/note add "Sprint field is called 'Board'"
+kd /primer/article add FB-A-42 --summary "Architecture Overview"
+kd /primer show
+
+# Cross-entity search
+kd /search "router" --types issue,article --project FB
+
+# Output formats
+kd /project list --output json | jq '.[].key'
+kd /issue list --output yaml
+```
+
+### Python SDK
+
+The CLI is a thin wrapper over a Python library. Same capabilities, programmatic interface:
+
+```python
+from kd import YouTrackClient
+
+client = YouTrackClient(
+    url="https://your-instance.youtrack.cloud",
+    token="your_token",
+)
+
+projects = client.projects.list()
+issue = client.issues.create(project="FB", summary="Fix router config")
+client.time.log(issue_id="FB-1", minutes=45, work_type="Development")
+articles = client.tags.articles(["type:case"], project="CMCSA")
+results = client.search.search("router", types=["issue", "article"])
+```
+
+## Development
+
+```bash
+pytest tests/ -v --tb=short
+
+ruff format kd/ tests/
+ruff check --fix kd/ tests/
+mypy kd/
+```
+
+---
+Updated: 2026-04-14

{kd_cli-2.0.4 → kd_cli-2.0.5}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "kd-cli"
-version = "2.0.4"
+version = "2.0.5"
 description = "Knowledge dispatcher for live knowledge systems"
 readme = "README.md"
 requires-python = ">=3.11"

kd_cli-2.0.4/PKG-INFO

@@ -1,149 +0,0 @@
-Metadata-Version: 2.4
-Name: kd-cli
-Version: 2.0.4
-Summary: Knowledge dispatcher for live knowledge systems
-Author: Sergiy Gladkyy
-License-Expression: MIT
-Keywords: youtrack,cli,sdk,knowledge-management,knowledge-network
-Classifier: Development Status :: 4 - Beta
-Classifier: Environment :: Console
-Classifier: Intended Audience :: Developers
-Classifier: Operating System :: POSIX
-Classifier: Programming Language :: Python :: 3
-Classifier: Programming Language :: Python :: 3.11
-Classifier: Programming Language :: Python :: 3.12
-Classifier: Programming Language :: Python :: 3.13
-Classifier: Topic :: Software Development :: Libraries :: Python Modules
-Classifier: Topic :: Utilities
-Requires-Python: >=3.11
-Description-Content-Type: text/markdown
-License-File: LICENSE
-Requires-Dist: httpx>=0.27
-Requires-Dist: pydantic>=2.0
-Requires-Dist: pyyaml>=6.0
-Requires-Dist: tabulate>=0.9
-Provides-Extra: dev
-Requires-Dist: pytest>=7.0; extra == "dev"
-Requires-Dist: pytest-httpx>=0.30; extra == "dev"
-Requires-Dist: ruff>=0.1.0; extra == "dev"
-Requires-Dist: mypy>=1.0; extra == "dev"
-Requires-Dist: pre-commit>=3.0; extra == "dev"
-Requires-Dist: types-PyYAML; extra == "dev"
-Requires-Dist: types-tabulate; extra == "dev"
-Dynamic: license-file
-
-# kd
-
-A knowledge dispatcher for live knowledge systems — pull what you need to reason, push your updates back, and stay on top of a live system rather than copying it.
-
-## Purpose
-
-**kd is a knowledge-network tool, not a data-exchange tool.** It is built around a small, primer-shaped idea: the operator reasons *on top of* live trackers, not alongside copies of them. The primary loop is **pull → reason → push updates back**. Integrating multiple sources happens in the operator's head — not in kd's data model. Occasional cross-system moves exist, but they are deliberately thin: at the limit, a stub with a similar title and a backref to the original, not a faithful reproduction. kd is not a migration tool or a comprehensive import-export platform; it is a network-of-knowledge dispatcher that speaks YouTrack fluently and will, over time, speak other trackers through narrow domain protocols.
-
-The **primer** (`kd /primer`) is the working illustration: a small set of pinned references plus curated notes, living in the workspace, sitting on top of live systems without replacing them. The rest of the tool extends that shape.
-
-**SDK-first**: the Python library (`kd.client`) is the primary interface; CLI commands are thin wrappers over it. LLMs constructing commands programmatically are the primary consumer, so syntax clarity and structured output matter more than keystroke economy.
-
-## Install
-
-```bash
-# pipx (recommended)
-pipx install kd
-
-# or uv
-uv tool install kd
-```
-
-## Configure
-
-```bash
-# Scaffold a project-local config in the current directory.
-kd init
-
-# Or set via environment (overrides workspace + global config).
-export KD_TOKEN=your_token
-export KD_CONNECTION=main
-```
-
-Global config lives at `~/.config/kd/config.yaml`; workspace config lives at `.kd/config.yaml`.
-
-## Usage
-
-### CLI
-
-```bash
-# Projects
-kd /project list
-kd /project show FB
-
-# Issues
-kd /issue list --project FB --query "#Unresolved"
-kd /issue create "Fix router configuration" -p FB --type Task
-kd /issue show FB-1
-
-# Time tracking
-kd /time log FB-1 45 --type Development --description "Router reconfiguration"
-
-# Articles
-kd /article list --project CMCSA
-kd /article push guide.md --project CMCSA --title "Setup Guide" --tag "type:guide"
-kd /article pull FB-A-42 > setup.md
-
-# Tags
-kd /tag list
-kd /tag articles type:case --project CMCSA
-
-# Saved queries
-kd /query list
-kd /query issues "Sprint 47" --project FB
-
-# Primer (local knowledge, LLM context)
-kd /primer/note add "Sprint field is called 'Board'"
-kd /primer/article add FB-A-42 --summary "Architecture Overview"
-kd /primer show
-
-# Cross-entity search
-kd /search "router" --types issue,article --project FB
-
-# Output formats
-kd /project list --output json | jq '.[].key'
-kd /issue list --output yaml
-```
-
-### Python SDK
-
-```python
-from kd import YouTrackClient
-
-client = YouTrackClient(
-    url="https://your-instance.youtrack.cloud",
-    token="your_token",
-)
-
-projects = client.projects.list()
-issue = client.issues.create(project="FB", summary="Fix router config")
-client.time.log(issue_id="FB-1", minutes=45, work_type="Development")
-articles = client.tags.articles(["type:case"], project="CMCSA")
-results = client.search.search("router", types=["issue", "article"])
-```
-
-## What kd is not
-
-- **Not a migration platform.** Cross-system moves are lossy cherry-picks: a stub on the target side with a backref to the source, nothing more.
-- **Not a faithful mirror.** kd never claims to be a complete copy of upstream state; it reads what it needs and writes what changed.
-- **Not a data warehouse.** Data lives in the upstream tracker; kd sits on top.
-
-If you need a migration tool or an import-export platform, kd is the wrong tool.
-
-## Development
-
-```bash
-pytest tests/ -v --tb=short
-
-ruff format kd/ tests/
-ruff check --fix kd/ tests/
-mypy kd/
-```
-
----
-Updated: 2026-04-13

kd_cli-2.0.4/README.md

@@ -1,115 +0,0 @@
-# kd
-
-A knowledge dispatcher for live knowledge systems — pull what you need to reason, push your updates back, and stay on top of a live system rather than copying it.
-
-## Purpose
-
-**kd is a knowledge-network tool, not a data-exchange tool.** It is built around a small, primer-shaped idea: the operator reasons *on top of* live trackers, not alongside copies of them. The primary loop is **pull → reason → push updates back**. Integrating multiple sources happens in the operator's head — not in kd's data model. Occasional cross-system moves exist, but they are deliberately thin: at the limit, a stub with a similar title and a backref to the original, not a faithful reproduction. kd is not a migration tool or a comprehensive import-export platform; it is a network-of-knowledge dispatcher that speaks YouTrack fluently and will, over time, speak other trackers through narrow domain protocols.
-
-The **primer** (`kd /primer`) is the working illustration: a small set of pinned references plus curated notes, living in the workspace, sitting on top of live systems without replacing them. The rest of the tool extends that shape.
-
-**SDK-first**: the Python library (`kd.client`) is the primary interface; CLI commands are thin wrappers over it. LLMs constructing commands programmatically are the primary consumer, so syntax clarity and structured output matter more than keystroke economy.
-
-## Install
-
-```bash
-# pipx (recommended)
-pipx install kd
-
-# or uv
-uv tool install kd
-```
-
-## Configure
-
-```bash
-# Scaffold a project-local config in the current directory.
-kd init
-
-# Or set via environment (overrides workspace + global config).
-export KD_TOKEN=your_token
-export KD_CONNECTION=main
-```
-
-Global config lives at `~/.config/kd/config.yaml`; workspace config lives at `.kd/config.yaml`.
-
-## Usage
-
-### CLI
-
-```bash
-# Projects
-kd /project list
-kd /project show FB
-
-# Issues
-kd /issue list --project FB --query "#Unresolved"
-kd /issue create "Fix router configuration" -p FB --type Task
-kd /issue show FB-1
-
-# Time tracking
-kd /time log FB-1 45 --type Development --description "Router reconfiguration"
-
-# Articles
-kd /article list --project CMCSA
-kd /article push guide.md --project CMCSA --title "Setup Guide" --tag "type:guide"
-kd /article pull FB-A-42 > setup.md
-
-# Tags
-kd /tag list
-kd /tag articles type:case --project CMCSA
-
-# Saved queries
-kd /query list
-kd /query issues "Sprint 47" --project FB
-
-# Primer (local knowledge, LLM context)
-kd /primer/note add "Sprint field is called 'Board'"
-kd /primer/article add FB-A-42 --summary "Architecture Overview"
-kd /primer show
-
-# Cross-entity search
-kd /search "router" --types issue,article --project FB
-
-# Output formats
-kd /project list --output json | jq '.[].key'
-kd /issue list --output yaml
-```
-
-### Python SDK
-
-```python
-from kd import YouTrackClient
-
-client = YouTrackClient(
-    url="https://your-instance.youtrack.cloud",
-    token="your_token",
-)
-
-projects = client.projects.list()
-issue = client.issues.create(project="FB", summary="Fix router config")
-client.time.log(issue_id="FB-1", minutes=45, work_type="Development")
-articles = client.tags.articles(["type:case"], project="CMCSA")
-results = client.search.search("router", types=["issue", "article"])
-```
-
-## What kd is not
-
-- **Not a migration platform.** Cross-system moves are lossy cherry-picks: a stub on the target side with a backref to the source, nothing more.
-- **Not a faithful mirror.** kd never claims to be a complete copy of upstream state; it reads what it needs and writes what changed.
-- **Not a data warehouse.** Data lives in the upstream tracker; kd sits on top.
-
-If you need a migration tool or an import-export platform, kd is the wrong tool.
-
-## Development
-
-```bash
-pytest tests/ -v --tb=short
-
-ruff format kd/ tests/
-ruff check --fix kd/ tests/
-mypy kd/
-```
-
----
-Updated: 2026-04-13

kd_cli-2.0.4/kd_cli.egg-info/PKG-INFO

@@ -1,149 +0,0 @@
-Metadata-Version: 2.4
-Name: kd-cli
-Version: 2.0.4
-Summary: Knowledge dispatcher for live knowledge systems
-Author: Sergiy Gladkyy
-License-Expression: MIT
-Keywords: youtrack,cli,sdk,knowledge-management,knowledge-network
-Classifier: Development Status :: 4 - Beta
-Classifier: Environment :: Console
-Classifier: Intended Audience :: Developers
-Classifier: Operating System :: POSIX
-Classifier: Programming Language :: Python :: 3
-Classifier: Programming Language :: Python :: 3.11
-Classifier: Programming Language :: Python :: 3.12
-Classifier: Programming Language :: Python :: 3.13
-Classifier: Topic :: Software Development :: Libraries :: Python Modules
-Classifier: Topic :: Utilities
-Requires-Python: >=3.11
-Description-Content-Type: text/markdown
-License-File: LICENSE
-Requires-Dist: httpx>=0.27
-Requires-Dist: pydantic>=2.0
-Requires-Dist: pyyaml>=6.0
-Requires-Dist: tabulate>=0.9
-Provides-Extra: dev
-Requires-Dist: pytest>=7.0; extra == "dev"
-Requires-Dist: pytest-httpx>=0.30; extra == "dev"
-Requires-Dist: ruff>=0.1.0; extra == "dev"
-Requires-Dist: mypy>=1.0; extra == "dev"
-Requires-Dist: pre-commit>=3.0; extra == "dev"
-Requires-Dist: types-PyYAML; extra == "dev"
-Requires-Dist: types-tabulate; extra == "dev"
-Dynamic: license-file
-
-# kd
-
-A knowledge dispatcher for live knowledge systems — pull what you need to reason, push your updates back, and stay on top of a live system rather than copying it.
-
-## Purpose
-
-**kd is a knowledge-network tool, not a data-exchange tool.** It is built around a small, primer-shaped idea: the operator reasons *on top of* live trackers, not alongside copies of them. The primary loop is **pull → reason → push updates back**. Integrating multiple sources happens in the operator's head — not in kd's data model. Occasional cross-system moves exist, but they are deliberately thin: at the limit, a stub with a similar title and a backref to the original, not a faithful reproduction. kd is not a migration tool or a comprehensive import-export platform; it is a network-of-knowledge dispatcher that speaks YouTrack fluently and will, over time, speak other trackers through narrow domain protocols.
-
-The **primer** (`kd /primer`) is the working illustration: a small set of pinned references plus curated notes, living in the workspace, sitting on top of live systems without replacing them. The rest of the tool extends that shape.
-
-**SDK-first**: the Python library (`kd.client`) is the primary interface; CLI commands are thin wrappers over it. LLMs constructing commands programmatically are the primary consumer, so syntax clarity and structured output matter more than keystroke economy.
-
-## Install
-
-```bash
-# pipx (recommended)
-pipx install kd
-
-# or uv
-uv tool install kd
-```
-
-## Configure
-
-```bash
-# Scaffold a project-local config in the current directory.
-kd init
-
-# Or set via environment (overrides workspace + global config).
-export KD_TOKEN=your_token
-export KD_CONNECTION=main
-```
-
-Global config lives at `~/.config/kd/config.yaml`; workspace config lives at `.kd/config.yaml`.
-
-## Usage
-
-### CLI
-
-```bash
-# Projects
-kd /project list
-kd /project show FB
-
-# Issues
-kd /issue list --project FB --query "#Unresolved"
-kd /issue create "Fix router configuration" -p FB --type Task
-kd /issue show FB-1
-
-# Time tracking
-kd /time log FB-1 45 --type Development --description "Router reconfiguration"
-
-# Articles
-kd /article list --project CMCSA
-kd /article push guide.md --project CMCSA --title "Setup Guide" --tag "type:guide"
-kd /article pull FB-A-42 > setup.md
-
-# Tags
-kd /tag list
-kd /tag articles type:case --project CMCSA
-
-# Saved queries
-kd /query list
-kd /query issues "Sprint 47" --project FB
-
-# Primer (local knowledge, LLM context)
-kd /primer/note add "Sprint field is called 'Board'"
-kd /primer/article add FB-A-42 --summary "Architecture Overview"
-kd /primer show
-
-# Cross-entity search
-kd /search "router" --types issue,article --project FB
-
-# Output formats
-kd /project list --output json | jq '.[].key'
-kd /issue list --output yaml
-```
-
-### Python SDK
-
-```python
-from kd import YouTrackClient
-
-client = YouTrackClient(
-    url="https://your-instance.youtrack.cloud",
-    token="your_token",
-)
-
-projects = client.projects.list()
-issue = client.issues.create(project="FB", summary="Fix router config")
-client.time.log(issue_id="FB-1", minutes=45, work_type="Development")
-articles = client.tags.articles(["type:case"], project="CMCSA")
-results = client.search.search("router", types=["issue", "article"])
-```
-
-## What kd is not
-
-- **Not a migration platform.** Cross-system moves are lossy cherry-picks: a stub on the target side with a backref to the source, nothing more.
-- **Not a faithful mirror.** kd never claims to be a complete copy of upstream state; it reads what it needs and writes what changed.
-- **Not a data warehouse.** Data lives in the upstream tracker; kd sits on top.
-
-If you need a migration tool or an import-export platform, kd is the wrong tool.
-
-## Development
-
-```bash
-pytest tests/ -v --tb=short
-
-ruff format kd/ tests/
-ruff check --fix kd/ tests/
-mypy kd/
-```
-
----
-Updated: 2026-04-13