@fjell/registry 4.4.84 → 4.4.86

package/LICENSE

@@ -187,7 +187,7 @@
       same "printed page" as the copyright notice for easier
       identification within third-party archives.
 
-   Copyright 2025 Fjell Project
+   Copyright 2026 Tim O'Brien
 
    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.

package/guide/index.md

@@ -0,0 +1,30 @@
+# @fjell/registry - Agentic Guide
+
+## Purpose
+
+Dependency injection and service registry utilities for composing Fjell systems.
+
+This guide is optimized for AI-assisted code generation and integration workflows.
+
+## Documentation
+
+- **[Usage Guide](./usage.md)** - API-oriented usage patterns and model-safe examples
+- **[Integration Guide](./integration.md)** - Architecture placement, composition rules, and implementation guidance
+
+## Key Capabilities
+
+- Registers and resolves service instances with typed lookups
+- Supports registry hubs and stats for larger multi-service deployments
+- Centralizes dependency wiring for app bootstrap and tests
+
+## Installation
+
+```bash
+npm install @fjell/registry
+```
+
+## Public API Highlights
+
+- `Registry`, `RegistryHub`, and `Instance` helpers
+- `RegistryStats` for observability
+- Registry error and type exports for safe composition

package/guide/integration.md

@@ -0,0 +1,32 @@
+# Integration Guide
+
+Guide for integrating `@fjell/registry` into larger Fjell-based systems.
+
+## Where It Fits
+
+Dependency injection and service registry utilities for composing Fjell systems.
+
+## Recommended Integration Pattern
+
+- Create one root registry per runtime process and pass scoped registries into modules
+- Prefer constructor injection from registry values over hidden singleton imports
+- Mock registry entries in tests to isolate network and storage dependencies
+
+## System Composition Checklist
+
+- Define package boundaries: schema/types, transport, operations, adapters, and UI.
+- Keep contracts stable by sharing @fjell/types interfaces where applicable.
+- Centralize retries/timeouts/logging around infrastructure-facing operations.
+- Validate inputs at API boundaries before invoking persistence or provider layers.
+- Add contract and integration tests for every generated workflow.
+
+## Cross-Library Pairings
+
+- Pair with @fjell/types for shared contracts.
+- Pair with @fjell/validation for input and schema checks.
+- Pair with @fjell/logging for observability in integration flows.
+- Pair with storage/router/provider packages based on your runtime architecture.
+
+## Integration Example Shape
+
+Use this package behind an application service layer that exposes stable domain methods. Generated code should call those service methods, not raw infrastructure primitives, unless your architecture intentionally keeps infrastructure at the edge.

package/guide/usage.md

@@ -0,0 +1,41 @@
+# Usage Guide
+
+Comprehensive usage guidance for `@fjell/registry`.
+
+## Installation
+
+```bash
+npm install @fjell/registry
+```
+
+## API Highlights
+
+- `Registry`, `RegistryHub`, and `Instance` helpers
+- `RegistryStats` for observability
+- Registry error and type exports for safe composition
+
+## Quick Example
+
+```ts
+import { Registry } from "@fjell/registry";
+
+const registry = new Registry();
+registry.register("logger", { info: console.log });
+
+const logger = registry.get("logger");
+logger.info("Registry wired");
+```
+
+## Model Consumption Rules
+
+1. Import from the package root (`@fjell/registry`) instead of deep-internal paths unless explicitly documented.
+2. Keep usage aligned with exported public symbols listed in this guide.
+3. Prefer explicit typing at package boundaries so generated code remains robust during upgrades.
+4. Keep error handling deterministic and map infrastructure failures into domain-level errors.
+5. Co-locate integration wrappers in your app so model-generated code has one canonical entry point.
+
+## Best Practices
+
+- Keep examples and abstractions consistent with existing Fjell package conventions.
+- Favor composable wrappers over one-off inline integration logic.
+- Add targeted tests around generated integration code paths.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@fjell/registry",
   "description": "Dependency injection and service location system for the Fjell ecosystem",
-  "version": "4.4.84",
+  "version": "4.4.86",
   "keywords": [
     "registry",
     "dependency-injection",
@@ -39,14 +39,14 @@
     "docs:test": "cd docs && npm run test"
   },
   "dependencies": {
-    "@fjell/core": "^4.4.77",
-    "@fjell/logging": "^4.4.67",
-    "@fjell/types": "^4.4.7"
+    "@fjell/core": "^4.4.79",
+    "@fjell/logging": "^4.4.72",
+    "@fjell/types": "^4.4.9"
   },
   "devDependencies": {
     "@eslint/eslintrc": "^3.3.1",
     "@eslint/js": "^9.39.1",
-    "@fjell/common-config": "^1.1.37",
+    "@fjell/common-config": "^1.1.38",
     "@swc/core": "^1.15.2",
     "@tsconfig/recommended": "^1.0.13",
     "@types/node": "^24.10.1",