feat(registry): extend TemplateType and integrate PackageReference into template system #27

New issue

Open

opened 2026-06-05 17:34:19 +00:00 by CoreRasurae · 0 comments

CoreRasurae commented

2026-06-05 17:34:19 +00:00

Member

Metadata

Commit Message: feat(registry): extend TemplateType and integrate PackageReference into template system
Branch: feature/m1-registry-template-alignment

Background and context

The existing template system supports only 3 types (AGENT, GRAPH, STREAM) with local name-based lookups via ComponentReference. The Package Registry Standard v1.0.0 introduces 6 offline package types (actor, graph, stream, agent, template, skill). We need to extend TemplateType, add PackageReference support to ComponentReference, and wire registry resolution into template instantiation so templates can reference external packages.

Part of Epic: Package Registry Client — Support Package Registry Standard v1.0.0

Current behavior

TemplateType enum has only AGENT, GRAPH, STREAM. ComponentReference uses simple ref_type/ref_name strings with no concept of external registry references.

Expected behavior

TemplateType extended with TEMPLATE, SKILL, ACTOR, MCP, LSP
ComponentReference gains optional package_ref: PackageReference | None
When a template key resolves to a registry reference (e.g. template: "registry.example.com:ns/helper@latest"), the registry client fetches and caches the content
Resolved components carry _original_reference in metadata for debug traceability
Local templates (current behavior) continue unchanged
Multi-server support: one RegistryClient per server URL

Acceptance criteria

TemplateType.TEMPLATE and TemplateType.SKILL register and instantiate
Template with "git.cleverthis.com:acme/helper@v1.0.0" resolves via registry client
Resolved component metadata includes _original_reference
Local templates unaffected
Registry fetch failures produce descriptive TemplateError with original reference

Subtasks

Extend TemplateType enum in base.py with TEMPLATE, SKILL, ACTOR, MCP, LSP
Extend ComponentReference dataclass with optional package_ref field
Add registry-aware lookup in EnhancedTemplateRegistry and TemplateRegistry
Propagate _original_reference through instantiation chain to component metadata
Wire ReferenceResolver + RegistryClient pool for multi-server support
Tests (Behave): features/registry_template_integration.feature — registry ref in template, local fallback, error paths
Validate existing template tests still pass unchanged
Verify coverage >=97% via nox -s coverage_report
Run nox (all default sessions), fix any errors

Definition of Done

This issue is complete when:

All subtasks above are completed and checked off.
A Git commit is created where the first line matches the Commit Message in Metadata exactly.
The commit is pushed to the branch matching the Branch in Metadata exactly.
The commit is submitted as a PR to master, reviewed, and merged.

## Metadata Commit Message: feat(registry): extend TemplateType and integrate PackageReference into template system Branch: feature/m1-registry-template-alignment ## Background and context The existing template system supports only 3 types (AGENT, GRAPH, STREAM) with local name-based lookups via `ComponentReference`. The Package Registry Standard v1.0.0 introduces 6 offline package types (actor, graph, stream, agent, template, skill). We need to extend `TemplateType`, add `PackageReference` support to `ComponentReference`, and wire registry resolution into template instantiation so templates can reference external packages. Part of Epic: Package Registry Client — Support Package Registry Standard v1.0.0 ## Current behavior `TemplateType` enum has only AGENT, GRAPH, STREAM. `ComponentReference` uses simple `ref_type`/`ref_name` strings with no concept of external registry references. ## Expected behavior - `TemplateType` extended with TEMPLATE, SKILL, ACTOR, MCP, LSP - `ComponentReference` gains optional `package_ref: PackageReference | None` - When a template key resolves to a registry reference (e.g. `template: "registry.example.com:ns/helper@latest"`), the registry client fetches and caches the content - Resolved components carry `_original_reference` in metadata for debug traceability - Local templates (current behavior) continue unchanged - Multi-server support: one `RegistryClient` per server URL ## Acceptance criteria - `TemplateType.TEMPLATE` and `TemplateType.SKILL` register and instantiate - Template with `"git.cleverthis.com:acme/helper@v1.0.0"` resolves via registry client - Resolved component metadata includes `_original_reference` - Local templates unaffected - Registry fetch failures produce descriptive `TemplateError` with original reference ## Subtasks - [ ] Extend `TemplateType` enum in `base.py` with TEMPLATE, SKILL, ACTOR, MCP, LSP - [ ] Extend `ComponentReference` dataclass with optional `package_ref` field - [ ] Add registry-aware lookup in `EnhancedTemplateRegistry` and `TemplateRegistry` - [ ] Propagate `_original_reference` through instantiation chain to component metadata - [ ] Wire `ReferenceResolver` + `RegistryClient` pool for multi-server support - [ ] Tests (Behave): features/registry_template_integration.feature — registry ref in template, local fallback, error paths - [ ] Validate existing template tests still pass unchanged - [ ] Verify coverage >=97% via nox -s coverage_report - [ ] Run nox (all default sessions), fix any errors ## Definition of Done This issue is complete when: - All subtasks above are completed and checked off. - A Git commit is created where the first line matches the Commit Message in Metadata exactly. - The commit is pushed to the branch matching the Branch in Metadata exactly. - The commit is submitted as a PR to master, reviewed, and merged.

CoreRasurae added this to the v2.1.0 milestone

2026-06-05 17:34:19 +00:00

~~CoreRasurae referenced this issue 2026-06-05 17:36:35 +00:00~~

Epic: Package Registry Client — Support Package Registry Standard v1.0.0 #22

~~CoreRasurae referenced this issue 2026-06-05 17:36:55 +00:00~~

feat(registry): implement BDD test features and compliance test vectors #30

CoreRasurae added a new dependency

2026-06-05 17:41:16 +00:00

#22 Epic: Package Registry Client — Support Package Registry Standard v1.0.0

CoreRasurae changed title from ~~Template system alignment — extend TemplateType, integrate PackageReference~~ to feat(registry): extend TemplateType and integrate PackageReference into template system

2026-06-05 17:47:44 +00:00

CoreRasurae referenced this issue from a commit

2026-06-07 20:23:58 +00:00

feat(registry): extend TemplateType and integrate PackageReference into template system

CoreRasurae referenced this issue from a pull request that will close it,

2026-06-07 20:25:16 +00:00

feat(registry): extend TemplateType and integrate PackageReference into template system #35

CoreRasurae referenced this issue from a commit

2026-06-07 21:26:45 +00:00

feat(registry): extend TemplateType and integrate PackageReference into template system

CoreRasurae added a new dependency

2026-06-07 22:33:03 +00:00