plm-skill-kernel 1.0.1__tar.gz → 1.0.2__tar.gz

{plm_skill_kernel-1.0.1 → plm_skill_kernel-1.0.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: plm-skill-kernel
-Version: 1.0.1
+Version: 1.0.2
 Summary: TracePulse PLM Skill Kernel — Wave 2 Conv A. Decorator-based Skill SDK + V1 in-process dispatcher + Kernel HTTP server stub matching CR.10 §7.bis (POST /v1/skills/{id}/invoke). Ships 3 starter skills (cleansing.normalise, cleansing.dedupe, bpmn.generate). Sibling of plm-engine-core; the two communicate over the V1.1 HTTP loopback (SKILL_KERNEL_LOOPBACK=on) — no Python-level coupling at the dispatch boundary.
 Author: TracePulse
 License: Proprietary

{plm_skill_kernel-1.0.1 → plm_skill_kernel-1.0.2}/plm_skill_kernel/__init__.py

@@ -14,7 +14,7 @@ sanctioned interaction is the V1.1 HTTP loopback (env-flagged on
 ``SKILL_KERNEL_LOOPBACK``); any Python-level reach-in is forbidden by
 the import-linter contract in ``pyproject.toml``.
 """
-__version__ = "1.0.1"
+__version__ = "1.0.2"
 
 # The decorator + sdk surface is the public authoring API. Re-exported
 # here so callers write ``from plm_skill_kernel import skill`` rather

{plm_skill_kernel-1.0.1 → plm_skill_kernel-1.0.2}/plm_skill_kernel/skills_legacy/skill_orchestrator.py

@@ -9,7 +9,6 @@ import json
 import logging
 from dataclasses import dataclass, field
 
-from plm_engine_core.runtime.llm_service import llm_service
 from plm_skill_kernel.skills_legacy.plm_skill_registry import PLMSkillRegistry
 
 logger = logging.getLogger(__name__)
@@ -105,6 +104,16 @@ class SkillOrchestrator:
                 "Tu réponds uniquement en JSON structuré, sans texte supplémentaire."
             )
 
+            # FTR-1713 — imported HERE, not at module scope. `runtime.llm_service`
+            # executes `from litellm import acompletion` on import, so a top-level
+            # import made LiteLLM load in every process that merely imported this
+            # module — including plm-agent-studio, whose FTR-1713 gate requires a
+            # runtime proof that it holds no provider path. The singleton is
+            # process-wide and lazily constructed anyway, so deferring the import
+            # changes no behaviour: the chain loads when a legacy skill actually
+            # runs, and not before.
+            from plm_engine_core.runtime.llm_service import llm_service
+
             result_text = await llm_service.generate_reply(
                 system_prompt=system_prompt,
                 user_prompt=user_prompt,

{plm_skill_kernel-1.0.1 → plm_skill_kernel-1.0.2}/plm_skill_kernel.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: plm-skill-kernel
-Version: 1.0.1
+Version: 1.0.2
 Summary: TracePulse PLM Skill Kernel — Wave 2 Conv A. Decorator-based Skill SDK + V1 in-process dispatcher + Kernel HTTP server stub matching CR.10 §7.bis (POST /v1/skills/{id}/invoke). Ships 3 starter skills (cleansing.normalise, cleansing.dedupe, bpmn.generate). Sibling of plm-engine-core; the two communicate over the V1.1 HTTP loopback (SKILL_KERNEL_LOOPBACK=on) — no Python-level coupling at the dispatch boundary.
 Author: TracePulse
 License: Proprietary

{plm_skill_kernel-1.0.1 → plm_skill_kernel-1.0.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "plm-skill-kernel"
-version = "1.0.1"
+version = "1.0.2"
 description = "TracePulse PLM Skill Kernel — Wave 2 Conv A. Decorator-based Skill SDK + V1 in-process dispatcher + Kernel HTTP server stub matching CR.10 §7.bis (POST /v1/skills/{id}/invoke). Ships 3 starter skills (cleansing.normalise, cleansing.dedupe, bpmn.generate). Sibling of plm-engine-core; the two communicate over the V1.1 HTTP loopback (SKILL_KERNEL_LOOPBACK=on) — no Python-level coupling at the dispatch boundary."
 readme = "README.md"
 requires-python = ">=3.12"