cleveragents/cleveractors-core
0
0
Fork 0
Code Issues 17 Pull Requests 3 Actions Packages Projects Releases Wiki Activity

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

New Issue
Open
opened 2026-06-05 17:33:15 +00:00 by CoreRasurae · 1 comment
CoreRasurae commented 2026-06-05 17:33:15 +00:00
Member
Copy Link
Copy Source

Metadata

Commit Message: feat(registry): implement Package Registry Standard v1.0.0 client

Background and context

The Package Registry Standard v1.0.0 (per actor-registry-standard.md) defines a protocol and data model for storing, retrieving, and managing versioned packages of AI components. This Epic covers the implementation of a compliant client — not a server — that fetches, resolves, caches, and integrates registry packages into the CleverActors template system.

Expected behavior

When complete, templates and Actor configurations will be able to reference external packages via registry references (server:namespace/name@version), direct SHA-1 IDs (ID:pkg_act_<40-hex>), and local references. Internally all IDs are SHA-1; debug traces carry the original user-specified reference.

Acceptance criteria

All child issues are closed AND:

  • src/cleveractors/registry/ module exists with types, client, canonicalizer, resolver, exceptions, cache
  • A template referencing registry.example.com:acme/helper@v1.0.0 resolves, fetches, and instantiates correctly
  • Canonicalization produces deterministic SHA-1 per the standard
  • HTTP client uses httpx for async registry operations
  • 97%+ coverage on all new registry modules
  • nox full suite passes

Subtasks

  • Core data types (PackageType, PackageId, PackageReference, PackageContent)
  • Registry HTTP client using httpx (async, 4 endpoints, error mapping)
  • Canonicalization engine (NFC, key sorting, RFC-8785, SHA-1)
  • Reference resolution (parse refs, version aliases, local scheme)
  • Template system alignment (extend TemplateType, integrate PackageReference)
  • Client-side caching (LRU, TTL, ID validation)
  • Exception hierarchy (RegistryError + 8 typed errors)
  • BDD features + test vectors (mock server, canonicalization matrices)

Definition of Done

This Epic is complete when:

  • All subtasks above are completed and checked off.
  • All child issues are closed and their Definition of Done criteria are met.
  • The src/cleveractors/registry/ module is fully implemented and tested.
  • nox returns all-green.
  • A stakeholder can demonstrate a template using a registry reference that resolves correctly.

Dependency graph

#22 Epic
├── #23 Core types
│   ├── #25 Canonicalization
│   ├── #26 Reference resolution
│   └── #29 Exceptions
├── #24 HTTP client
├── #27 Template alignment
├── #28 Caching
└── #30 BDD features

New module structure

src/cleveractors/registry/
    __init__.py          # Public exports
    types.py             # PackageType, PackageId, PackageReference, PackageContent
    client.py            # RegistryClient (async httpx)
    canonical.py          # Canonicalizer (SHA-1 computation)
    resolver.py           # ReferenceResolver (parse + version resolution)
    exceptions.py         # Error type hierarchy
    cache.py              # Client-side caching (TTL, LRU)
## Metadata Commit Message: feat(registry): implement Package Registry Standard v1.0.0 client ## Background and context The Package Registry Standard v1.0.0 (per `actor-registry-standard.md`) defines a protocol and data model for storing, retrieving, and managing versioned packages of AI components. This Epic covers the implementation of a compliant **client** — not a server — that fetches, resolves, caches, and integrates registry packages into the CleverActors template system. ## Expected behavior When complete, templates and Actor configurations will be able to reference external packages via registry references (`server:namespace/name@version`), direct SHA-1 IDs (`ID:pkg_act_<40-hex>`), and local references. Internally all IDs are SHA-1; debug traces carry the original user-specified reference. ## Acceptance criteria All child issues are closed AND: - `src/cleveractors/registry/` module exists with types, client, canonicalizer, resolver, exceptions, cache - A template referencing `registry.example.com:acme/helper@v1.0.0` resolves, fetches, and instantiates correctly - Canonicalization produces deterministic SHA-1 per the standard - HTTP client uses `httpx` for async registry operations - 97%+ coverage on all new registry modules - `nox` full suite passes ## Subtasks - [ ] Core data types (PackageType, PackageId, PackageReference, PackageContent) - [ ] Registry HTTP client using httpx (async, 4 endpoints, error mapping) - [ ] Canonicalization engine (NFC, key sorting, RFC-8785, SHA-1) - [ ] Reference resolution (parse refs, version aliases, local scheme) - [ ] Template system alignment (extend TemplateType, integrate PackageReference) - [ ] Client-side caching (LRU, TTL, ID validation) - [ ] Exception hierarchy (RegistryError + 8 typed errors) - [ ] BDD features + test vectors (mock server, canonicalization matrices) ## Definition of Done This Epic is complete when: - All subtasks above are completed and checked off. - All child issues are closed and their Definition of Done criteria are met. - The `src/cleveractors/registry/` module is fully implemented and tested. - `nox` returns all-green. - A stakeholder can demonstrate a template using a registry reference that resolves correctly. ## Dependency graph ``` #22 Epic ├── #23 Core types │ ├── #25 Canonicalization │ ├── #26 Reference resolution │ └── #29 Exceptions ├── #24 HTTP client ├── #27 Template alignment ├── #28 Caching └── #30 BDD features ``` ## New module structure ``` src/cleveractors/registry/ __init__.py # Public exports types.py # PackageType, PackageId, PackageReference, PackageContent client.py # RegistryClient (async httpx) canonical.py # Canonicalizer (SHA-1 computation) resolver.py # ReferenceResolver (parse + version resolution) exceptions.py # Error type hierarchy cache.py # Client-side caching (TTL, LRU) ```
CoreRasurae added this to the v2.1.0 milestone 2026-06-05 17:33:15 +00:00
CoreRasurae added a new dependency 2026-06-05 17:41:00 +00:00
#24 feat(registry): implement async HTTP client using httpx
CoreRasurae removed this from the v2.1.0 milestone 2026-06-05 17:45:41 +00:00
CoreRasurae commented 2026-06-11 20:28:20 +00:00
Author
Member
Copy Link
Copy Source

New child issue: #46 — feat(registry): implement local: namespace reference resolution with filesystem + canonicalization.

This covers the remaining LOCAL reference scheme resolution, which was parsed but not implemented in #26 (ReferenceResolver raises 'not yet implemented'). The work introduces LocalPackageStore for filesystem-based package resolution with canonicalization + SHA-1 PackageId assignment.

New child issue: #46 — feat(registry): implement local: namespace reference resolution with filesystem + canonicalization. This covers the remaining LOCAL reference scheme resolution, which was parsed but not implemented in #26 (ReferenceResolver raises 'not yet implemented'). The work introduces `LocalPackageStore` for filesystem-based package resolution with canonicalization + SHA-1 PackageId assignment.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
auto/blocked-by-deps
PR blocked by an open issue dependency. Operator must close the dep (or remove the dependency link) before the merge driver can act. Auto-cleared by merge_drive when no open deps remain.
 auto/ci-timeout
Most recent merge cycle hit CI timeout. Driver excludes this PR while last merge_cycle row is < 30 min old; label persists thereafter as visible history.
 auto/claimed-implementer
Currently being processed by an implementer worker.
 auto/claimed-merge
Currently being processed by the merge driver.
 auto/claimed-reviewer
Currently being processed by a reviewer worker.
 auto/driver-down
Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.
 auto/invariant-violation
Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.
 auto/last-attempt-tier-0
In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.
 auto/last-attempt-tier-1
In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.
 auto/last-attempt-tier-2
In-cycle escalation: most recent attempt ran at the Tier 2 slot (`tier-2`). Slot's model defined in .opencode/models/tiers.yaml. Gated behind IMPLEMENTER_ESCALATION_TIER2_ENABLED.
 auto/last-attempt-tier-min
In-cycle escalation: most recent attempt ran at the Tier -1 slot (`tier-min`). Slot's model defined in .opencode/models/tiers.yaml. Suffix is ``-min`` (not ``--1``) so the Forgejo UI reads naturally.
 Automation Tracking
Tracking issues used by the AI Automation system for agents to communicate and report.
 auto/needs-conflict-resolution
Rebase conflict needs LLM conflict-resolver.
 auto/needs-implementer
Failing CI needs implementer attention.
 auto/postmortem
Documenting a driver incident or rollback.
 auto/ready-to-merge
Reviewer has APPROVED this PR and no later REQUEST_CHANGES is outstanding. The merge driver requires this label to even consider a PR for merging. Set by the reviewer worker on APPROVE; cleared on REQUEST_CHANGES.
 auto/restart-throttled
Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.
 auto/revert
Revert PR backing out an invariant violation. Fast-tracked through the merge driver.
 auto/sentinel
Sentinel PR duplicated from upstream into a personal fork by tools/duplicate_prs_to_fork.py for pipeline testing. Lives only in the fork; the canonical pipeline never sees it.
 auto/stale-inactivity
No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.
 auto/unstable
Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.
 Blocked
A ticket in a blocked state and unable to complete until some other task is completed first.
Bounty
$100
A bounty of $100 for any open-source contributor who provides a MR that solves this issue
Bounty
$1000
A bounty of $1000 for any open-source contributor who provides a MR that solves this issue
Bounty
$10000
A bounty of $10000 for any open-source contributor who provides a MR that solves this issue
Bounty
$20
A bounty of $20 for any open-source contributor who provides a MR that solves this issue
Bounty
$2000
A bounty of $2000 for any open-source contributor who provides a MR that solves this issue
Bounty
$250
A bounty of $250 for any open-source contributor who provides a MR that solves this issue
Bounty
$50
A bounty of $50 for any open-source contributor who provides a MR that solves this issue
Bounty
$500
A bounty of $500 for any open-source contributor who provides a MR that solves this issue
Bounty
$5000
A bounty of $5000 for any open-source contributor who provides a MR that solves this issue
Bounty
$750
A bounty of $750 for any open-source contributor who provides a MR that solves this issue
MoSCoW
Could have
Could have feature in order to satisfy the epic/legendary.
MoSCoW
Must have
Must have feature in order to satisfy the epic/legendary.
MoSCoW
Should have
Should have feature in order to satisfy the epic/legendary.
Needs Feedback
There are questions in the ticket that can not be completed until the project owner provides clarity.
Points
1
1 man-hours worth of work for an expert with no learning curve.
Points
13
13 man-hours worth of work for an expert with no learning curve.
Points
2
2 man-hours worth of work for an expert with no learning curve.
Points
21
21 man-hours worth of work for an expert with no learning curve.
Points
3
3 man-hours worth of work for an expert with no learning curve.
Points
34
34 man-hours worth of work for an expert with no learning curve.
Points
5
5 man-hours worth of work for an expert with no learning curve.
Points
55
55 man-hours worth of work for an expert with no learning curve.
Points
8
8 man-hours worth of work for an expert with no learning curve.
Points
88
88 man-hours worth of work for an expert with no learning curve.
Priority
Backlog
This ticket has backlogged priority and is not to be worked on yet
Priority
CI Blocker
Critical priority issue that blocks CI/CD pipeline and prevents PR merges
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Signed-off: Owner
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
 Signed-off: Scrum Master
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
 Signed-off: Tech Lead
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
 Spike
A ticket for learning a tool or technology that is needed to be able to do future planning and design.
State
Completed
The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.
State
Duplicate
A ticket that represents the same content as an existing ticket.
State
In Progress
A ticket that is actively being developed.
State
In Review
A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.
State
Paused
This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.
State
Unverified
All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.
State
Verified
The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.
State
Wont Do
This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.
Type
Automation
Any edits or discussion about the AI automated coding system.
Type
Bug
Something that doesnt work as intended.
Type
Discussion
Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.
Type
Documentation
An error or improvement needed in the documentation.
Type
Epic
Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.
Type
Feature
Some new functionality not present.
Type
Legendary
A type of Epic which will contain other Epics.
Type
Refactor
A code change that restructures existing code without changing its external behavior.
Type
Support
Someone needs help using the project.
Type
Task
A generic task that doesnt fit into the other type categories.
Type
Testing
Work exclusively focusing on fixing or expanding testing.
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
aditya (Aditya Chhabra) aleenaumair (Aleena Umair) brent.edwards (Brent Edwards) CoreRasurae (Luis Mendes) drew (Drew Morris) eugen.thaci (Eugen Thaci) freemo (Jeffrey Phillips Freeman) HAL9000 (HAL 9000) HAL9001 (HAL9001) hamza.khyari (Hamza Khyari) hurui200320 (Rui Hu) justin.morris khird (Kyle Hird) org.cleveragents
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Depends on
#23 feat(registry): add core data types — PackageType, PackageId, PackageReference, PackageContent
cleveragents/cleveractors-core
#24 feat(registry): implement async HTTP client using httpx
cleveragents/cleveractors-core
#25 feat(registry): implement canonicalization engine — NFC, key sorting, RFC-8785, SHA-1
cleveragents/cleveractors-core
#26 feat(registry): implement reference resolution — parse refs, version aliases, local scheme
cleveragents/cleveractors-core
#27 feat(registry): extend TemplateType and integrate PackageReference into template system
cleveragents/cleveractors-core
#28 feat(registry): implement client-side LRU cache with TTL and ID validation
cleveragents/cleveractors-core
#29 feat(registry): implement error hierarchy — RegistryError base + all 8 error types
cleveragents/cleveractors-core
#30 test(robot): add end-to-end integration tests for email categorization actor graph
cleveragents/cleveractors-core
#46 feat(registry): implement local: namespace reference resolution with filesystem + canonicalization
cleveragents/cleveractors-core
#51 docs(registry): write MkDocs API documentation with examples for Package Registry Client (Epic #22)
cleveragents/cleveractors-core
#59 LLMAgent does not implement tool calling — tools configs silently ignored
cleveragents/cleveractors-core
#88 feat(skills): add Skill package schema and agent-side skill loading support
cleveragents/cleveractors-core
Reference: cleveragents/cleveractors-core#22
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?