kd-cli 2.6.4__tar.gz → 2.6.5__tar.gz

{kd_cli-2.6.4/kd_cli.egg-info → kd_cli-2.6.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: kd-cli
-Version: 2.6.4
+Version: 2.6.5
 Summary: Knowledge Dispatcher for issue trackers and knowledge bases
 Author: Sergiy Gladkyy
 License-Expression: MIT

{kd_cli-2.6.4 → kd_cli-2.6.5}/kd/api/youtrack.py

@@ -20,7 +20,7 @@ import re
 from typing import Any
 
 from kd.api.http import HttpClient
-from kd.exceptions import KdError
+from kd.exceptions import FieldDiscoveryError, KdError
 from kd.models import (
     AssistResponse,
     Attachment,
@@ -257,13 +257,15 @@ class YouTrackAPI:
         admin_fields: list[dict[str, Any]] = admin.get("customFields") or []
         if admin_fields:
             return admin_fields
-        raise KdError(
+        raise FieldDiscoveryError(
             f"No custom fields discovered for project '{project_id}'.",
             suggestion=(
                 "Either the project has no issues to sample from, or the "
                 "active token lacks Read Project Full on this project. "
                 "Create one issue (any contributor token works), or use a "
-                "token with project-administration rights. See KDCLI-A-22."
+                "token with project-administration rights. Or omit "
+                "--type / --priority / --state to create a minimal first "
+                "issue, then update it via `/issue update`. See KDCLI-A-22."
             ),
         )
 

{kd_cli-2.6.4 → kd_cli-2.6.5}/kd/client.py

@@ -45,7 +45,14 @@ from kd.article_marker import (
 from kd.config import ResolvedConfig
 from kd.connection import ConnectionContext
 from kd.debug import DebugLog
-from kd.exceptions import APIError, ConfigError, KdError, NotFoundError, ValidationError
+from kd.exceptions import (
+    APIError,
+    ConfigError,
+    FieldDiscoveryError,
+    KdError,
+    NotFoundError,
+    ValidationError,
+)
 from kd.query_parser import youtrack_query_literal
 from kd.models import (
     Article,
@@ -178,6 +185,19 @@ _SLOT_DEFAULTS: dict[str, str] = {
 }
 
 
+# Bootstrap synthesis dispatch: semantic slot -> project-side field
+# ``$type`` used to look up the issue-side ``$type`` and payload builder
+# in :data:`_FIELD_DISPATCH` when schema discovery returned no fields
+# (KDCLI-171). All three semantic slots are wired: HITL #2 confirmed
+# YouTrack accepts a synthetic ``StateIssueCustomField`` payload with a
+# ``name``-only value reference on an empty fresh project.
+_BOOTSTRAP_SLOT_TO_PROJECT_TYPE: dict[str, str] = {
+    "type": "EnumProjectCustomField",
+    "priority": "EnumProjectCustomField",
+    "state": "StateProjectCustomField",
+}
+
+
 # ---------------------------------------------------------------------------
 # Article push — types and helpers
 # ---------------------------------------------------------------------------
@@ -806,9 +826,61 @@ class IssueOperations:
         ``project`` is the project shortName (KEY).
         ``slots`` maps semantic names to values, e.g. ``{"type": "Bug"}``.
         ``aliases`` maps semantic names to actual field names from config.
+
+        On a fresh (zero-issue + non-admin) project, schema discovery
+        returns no fields and ``resolve_semantic_fields`` raises
+        :class:`FieldDiscoveryError`. For semantic-slot creates we
+        synthesize a best-effort payload using the post-discovery
+        ``$type`` mapping and let YouTrack accept or reject (KDCLI-171).
+        Generic ``--field`` flows route through
+        :meth:`resolve_generic_fields` instead and stay uncaught — without
+        server-side ``$type`` knowledge, synthesizing a guess is unsafe.
         """
         project_obj = self._yt.get_project(project)
-        return self._field_schema.resolve_semantic_fields(project_obj.id, slots, aliases)
+        try:
+            return self._field_schema.resolve_semantic_fields(project_obj.id, slots, aliases)
+        except FieldDiscoveryError as e:
+            return self._synthesize_for_empty_discovery(slots, aliases, original=e)
+
+    def _synthesize_for_empty_discovery(
+        self,
+        slots: dict[str, str],
+        aliases: dict[str, str] | None,
+        original: FieldDiscoveryError,
+    ) -> builtins.list[CustomField]:
+        """Synthesize CustomField payloads when schema discovery is empty.
+
+        Honors the alias layer (``state`` -> ``Stage`` for Scrum projects)
+        via ``aliases.get(slot, _SLOT_DEFAULTS[slot])`` — same shape as
+        :meth:`FieldSchema.resolve_semantic_fields`. Re-raises the
+        *original* :class:`FieldDiscoveryError` (full three-bullet hint
+        preserved verbatim) when any slot is not in
+        :data:`_BOOTSTRAP_SLOT_TO_PROJECT_TYPE` — partial-bootstrap is
+        not a valid posture; the operator either gets all slots they
+        asked for, or the unchanged improved hint pointing at all three
+        workarounds (sample issue, admin token, or omit-and-update).
+        """
+        aliases = aliases or {}
+        unsupported = [s for s in slots if s not in _BOOTSTRAP_SLOT_TO_PROJECT_TYPE]
+        if unsupported:
+            raise original
+
+        result: builtins.list[CustomField] = []
+        for slot, value in slots.items():
+            project_field_type = _BOOTSTRAP_SLOT_TO_PROJECT_TYPE[slot]
+            issue_type, builder = _FIELD_DISPATCH[(project_field_type, "")]
+            field_name = aliases.get(slot, _SLOT_DEFAULTS.get(slot, slot))
+            self._debug.debug(
+                "fields",
+                f"synthesizing slot '{slot}' -> field '{field_name}' "
+                f"($type={issue_type}) on empty discovery",
+            )
+            result.append(
+                CustomField.model_validate(
+                    {"name": field_name, "value": builder(value), "$type": issue_type}
+                )
+            )
+        return result
 
     def resolve_generic_fields(
         self,

{kd_cli-2.6.4 → kd_cli-2.6.5}/kd/exceptions.py

@@ -95,6 +95,19 @@ class ValidationError(KdError):
     """Invalid input before API call."""
 
 
+class FieldDiscoveryError(KdError):
+    """Schema discovery returned no fields for a project.
+
+    Raised by ``list_project_custom_fields`` when both the per-issue
+    projection and the admin projection produce empty results — the
+    'fresh project + non-admin token' bootstrap shape. Caught at the
+    SDK layer (``IssueOperations.resolve_custom_fields``) so semantic
+    create-with-slots flows can synthesize a best-effort payload;
+    generic ``--field`` flows let it propagate so the operator sees
+    the improved hint.
+    """
+
+
 class QueryLiteralError(KdError):
     """Name cannot be encoded as a YouTrack DSL value literal.
 

{kd_cli-2.6.4 → kd_cli-2.6.5}/kd/resources/CHANGELOG.md

@@ -4,6 +4,31 @@ All notable changes to kd-cli are recorded here. The project follows [Semantic V
 
 ## [Unreleased]
 
+## [2.6.5] — 2026-04-30
+
+This release closes M011 by adding empty-project bootstrap support to
+`/issue create`. Together with M011 S1 + S2 (the Windows UTF-8 audit in
+2.6.4), the milestone delivers a kd-only path from a fresh primer to
+the first ticket on a brand-new project on Windows: file IO, stdin,
+and field-resolution all work without falling back to the web UI.
+
+### Fixed
+- `/issue create` semantic bootstrap now succeeds on fresh
+  (zero-issue, contributor-token) projects: when both schema-discovery
+  paths return empty, kd synthesizes a best-effort payload for
+  `--type`, `--priority`, and `--state` using the post-discovery
+  `$type` mapping and lets YouTrack accept or reject. Pre-fix, kd
+  bailed before the API call with `Error: No custom fields discovered
+  for project '<id>'`, telling the operator to fall back to the web UI
+  for the very first issue — a kd-only bootstrap workflow could not
+  populate Type / Priority / State on a brand-new project.
+  `--field NAME=VALUE` still raises with the improved hint (kd cannot
+  guess server-side `$type` for arbitrary fields). The hint gains a
+  third bullet pointing at the simplest workaround: `Or omit --type /
+  --priority / --state to create a minimal first issue, then update it
+  via `/issue update``. See KDCLI-A-22 for the empty-project bootstrap
+  detail (KDCLI-171).
+
 ## [2.6.4] — 2026-04-30
 
 This release closes the Windows UTF-8 audit started in 2.6.3. The

{kd_cli-2.6.4 → kd_cli-2.6.5}/kd/resources/operating-guide.md

@@ -126,6 +126,8 @@ Clear optional custom fields with an empty value, for example `kd /issue update
 
 `--field` supports bundle families (enum, state, owned, version, build), user fields, period, and string `SimpleProjectCustomField` subtypes; whitespace inside the value is preserved. Unsupported families (text, `Multi*` enum/user variants, and `SimpleProjectCustomField` with `integer` / `float` / `date` subtypes) fail client-side with a message naming both the project `$type` and the `fieldType.id` subtype so a follow-on bug report can skip the probe.
 
+On fresh (zero-issue, contributor-token) projects where schema discovery returns no fields, kd synthesizes a best-effort bootstrap payload for `--type`, `--priority`, and `--state` and lets YouTrack accept or reject; YouTrack's rejection text surfaces unchanged so an unusual project setup is auditable upstream. `--field NAME=VALUE` still requires a sample issue or admin token because kd lacks server-side `$type` knowledge to synthesize generic fields safely. KDCLI-A-22 carries the detail.
+
 Attachment metadata download URLs may start with `/api/`. kd handles this internally on download commands; do not assume the raw URL can be appended unchanged to an API base URL in custom scripts.
 
 Tag existence, tag visibility, and tag sharing rights are different concerns. A visible tag may not be usable for every operation, and sharing settings are provider-specific security posture, not just display metadata.

{kd_cli-2.6.4 → kd_cli-2.6.5/kd_cli.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: kd-cli
-Version: 2.6.4
+Version: 2.6.5
 Summary: Knowledge Dispatcher for issue trackers and knowledge bases
 Author: Sergiy Gladkyy
 License-Expression: MIT

{kd_cli-2.6.4 → kd_cli-2.6.5}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "kd-cli"
-version = "2.6.4"
+version = "2.6.5"
 description = "Knowledge Dispatcher for issue trackers and knowledge bases"
 readme = "README.md"
 requires-python = ">=3.11"