renma 0.15.1 → 0.16.0

package/CHANGELOG.md

@@ -6,6 +6,37 @@ This project follows the spirit of [Keep a Changelog](https://keepachangelog.com
 
 ## [Unreleased]
 
+## [0.16.0] - 2026-07-11
+
+### Added
+
+- Added Agent Skills specification validation to `scan`, including stable diagnostics for entrypoint naming, frontmatter, metadata, and body requirements.
+- Added deterministic migration assistance to `suggest-metadata` for pre-0.16 Skill entrypoints and metadata, with conflict detection and canonical candidate validation.
+- Added comprehensive Agent Skills compatibility and migration documentation, canonical authoring guidance, and a Context Lens example for boundary-value spec review.
+
+### Changed
+
+- Required operational Skills to use specification-valid Agent Skills frontmatter with Renma extensions under flat, string-valued `metadata.renma.*` keys.
+- Updated catalog, graph, ownership, readiness, BOM, security, scaffold, and reporting consumers to use canonical Skill metadata while retaining legacy forms only as migration input.
+- Expanded the README, architecture, design, user manual, security guidance, and example repository for the 0.16.0 Skill format and repository model.
+
+### Fixed
+
+- Corrected the repository-owned release-prep Skill syntax and kept its operational workflow in the required release context.
+
+## [0.15.2] - 2026-07-10
+
+### Added
+
+- Added an authoritative Repository Context BOM v1 contract document covering schema compatibility, snapshot consistency, reproducibility, provenance, and future consumed-context evidence boundaries.
+- Added a normalized BOM v1 contract-shape test that pins stable JSON fields, nested shapes, deterministic ordering, and scope declarations.
+
+### Changed
+
+- Hardened `renma bom` so graph, readiness, diagnostics, Context Lens evidence, security posture, and security policy inventory are derived from the same collected repository snapshot as catalog assets.
+- Captured referenced helper and dependency path existence in `RepositorySnapshot` so snapshot-derived BOM and scan reports do not query the live filesystem during rule evaluation.
+- Clarified `--omit-generated-at` as a same-environment reproducibility option that removes only the run-time `generatedAt` field and does not normalize freshness metadata, absolute paths, file moves, UTC evaluation date changes, or cross-runner portability.
+
 ## [0.15.1] - 2026-07-10
 
 ### Added
@@ -279,7 +310,9 @@ Tag-only release. No GitHub Release entry was published for this version.
 - Added metadata governance, advisory diagnostics, local path checks, and semantic split suggestions.
 - Added the initial project documentation, architecture notes, package metadata, tests, and license.
 
-[Unreleased]: https://github.com/KazuCocoa/renma/compare/v0.15.1...HEAD
+[Unreleased]: https://github.com/KazuCocoa/renma/compare/v0.16.0...HEAD
+[0.16.0]: https://github.com/KazuCocoa/renma/compare/v0.15.2...v0.16.0
+[0.15.2]: https://github.com/KazuCocoa/renma/compare/v0.15.1...v0.15.2
 [0.15.1]: https://github.com/KazuCocoa/renma/compare/v0.15.0...v0.15.1
 [0.15.0]: https://github.com/KazuCocoa/renma/compare/v0.14.1...v0.15.0
 [0.14.1]: https://github.com/KazuCocoa/renma/compare/v0.14.0...v0.14.1

package/README.md

@@ -4,11 +4,16 @@
 [![Downloads](http://img.shields.io/npm/dm/renma.svg)](https://npmjs.org/package/renma)
 
 
-Renma is an opinionated Context Repository toolkit for LLM-era software teams.
+Renma is a Git-native context repository and deterministic governance tool for
+LLM-facing knowledge. It manages reusable Skills, Context Lenses, Context
+Assets, references, ownership, lifecycle, dependencies, and evidence as
+maintainable software assets.
 
-It helps teams manage reusable, human-curated context assets in Git so agents, coding tools, and future AI runtimes can consume team knowledge more safely and consistently.
-
-Renma is the deterministic governance and health layer around that repository knowledge. Instead of letting critical knowledge get copied into many prompts or buried in one-off Markdown files, Renma treats it as a software asset: named, owned, versioned, linked, checked in CI, and reviewed with deterministic diagnostics and scan findings.
+Instead of letting critical knowledge get copied into prompts or buried in
+one-off Markdown files, Renma keeps it named, owned, versioned, linked, checked
+in CI, and reviewed through deterministic diagnostics. Agents, coding tools,
+and other runtimes consume those repository assets according to their own
+runtime behavior.
 
 Renma now supports `scan`, `catalog`, `ownership`, `graph`, focused graph views, `trust-graph`, `readiness`, Repository Context BOM reports, repeated-context diagnostics, semantic diff, `ci-report`, `inspect`, `scaffold`, `suggest-metadata`, `suggest-semantic-split`, and security diagnostics.
 
@@ -20,7 +25,10 @@ Renma is especially useful when a repository contains agent-facing material such
 - Team-owned context assets that should outlive a single prompt
 - References and examples that agents should be able to cite or inspect
 
-Renma is not an agent runtime, not a prompt library, not a vector database, and not a general Markdown linter. Markdown is the storage format today; the product is the catalog, dependency graph, ownership model, and readiness checks around agent-consumable repository knowledge.
+Renma is not an agent runtime, prompt builder, live context selector, workflow
+engine, telemetry collector, vector database, or general Markdown linter.
+Markdown is the storage format today; the product is the repository model and
+the deterministic governance views around agent-consumable knowledge.
 
 Use Renma when you need to answer repository-level questions such as:
 
@@ -38,29 +46,66 @@ It is not a prompt library. It is not a vector database. It is not an agent memo
 
 It is a place where teams maintain context assets with ownership, lifecycle state, dependencies, references, and review history.
 
-## The Layer Model
+## Agent Skills Compatibility
 
-```text
-Tools
-  Codex, Claude, Cursor, CI, editors, internal CLIs
+Renma recognizes and validates [Agent Skills-compatible syntax](https://agentskills.io/specification)
+as a familiar, portable authoring entrypoint. This lowers adoption cost without
+making the Agent Skills format Renma's complete repository model: shared
+Context Assets, Context Lenses, policies, references, ownership, lifecycle,
+dependencies, and evidence remain independently governed repository assets.
 
-Skills
-  agent-facing entrypoints that route an agent toward a task
+In short, Renma is **Agent Skills-compatible, but not Agent Skills-defined**. A
+repository may organize its broader knowledge assets around domains, products,
+teams, or workflows without embedding them inside Skill directories. Canonical
+Skill entrypoints in 0.16.0 are still discovered only under
+`skills/**/SKILL.md` and `.agents/skills/**/SKILL.md`; arbitrary Skill roots are
+not implemented. Renma is not an Agent Skills runtime, registry, or live
+router. For the exact 0.16.0 syntax and migration boundary, see
+[Agent Skills Compatibility and Migration](docs/agent-skills-compatibility.md).
 
-Context Lenses
-  purpose-oriented interpretation layers over context assets
+## The Layer Model
 
-Context Assets
-  Shared domain, product, testing, platform, and tool knowledge
+```mermaid
+flowchart TD
+  subgraph Repository["Git-reviewed Repository — source of truth"]
+    Skills["Skills: agent-facing entrypoints and usage guides"]
+    Lenses["Context Lenses: purpose-oriented interpretation"]
+    Assets["Context Assets: reusable source-of-truth knowledge"]
+    Skills -->|may reference| Lenses
+    Skills -->|may reference directly| Assets
+    Lenses -->|interprets| Assets
+  end
+  Renma["Renma: discover, parse, normalize, and validate"]
+  Catalog["Catalog: generated projection of IDs, ownership, lifecycle, dependencies, evidence"]
+  Views["Graph, Trust Graph, Readiness, and BOM projections"]
+  Consumers["External tools and agents — runtime behavior outside Renma"]
+  Skills --> Renma
+  Lenses --> Renma
+  Assets --> Renma
+  Renma --> Catalog
+  Renma --> Views
+  Consumers -->|consume according to their runtime behavior| Skills
+  Consumers -->|may also consume| Lenses
+  Consumers -->|may also consume| Assets
+```
 
-Catalog
-  Deterministic IDs, ownership, lifecycle state, dependencies, evidence
+Skills may point through a Context Lens or directly to a Context Asset; a Lens
+is not required for every asset. Renma generates the Catalog and other
+governance projections from repository source assets and declarations; the
+Catalog describes those assets rather than creating them. Renma validates
+static declarations but does not select a Skill, choose or inject task Context,
+assemble a prompt, or execute the consumer's workflow.
 
-Repository
-  Git-reviewed source of truth for agent-consumable knowledge
-```
+## Primary Workflows
 
-Tools decide what to do at runtime. Skills tell an agent when and how to use a capability. Context lenses describe purpose-oriented interpretation over reusable knowledge. Context assets hold that reusable knowledge. Renma catalogs and validates the layer underneath so tools and agents are not guessing from stale, orphaned, duplicated, or unowned files.
+Renma supports two common user journeys:
+
+1. [Create a new Skill with `scaffold`](docs/user-manual.md#user-story-create-a-new-skill-with-scaffold), add reusable Context, validate the repository, and review the result.
+2. [Improve an existing Skill or context repository](docs/user-manual.md#user-story-improve-existing-skills-with-diagnostics) from deterministic diagnostics, optionally using a coding agent to propose a patch that a human reviews.
+
+The [`examples/context-repo`](examples/context-repo) fixture demonstrates the
+second journey as a repository-aware, statically navigable specification review
+with an explicit Renma, agent, and human responsibility boundary.
 
 ## How Renma Relates to RAG and Agent Memory
 
@@ -97,9 +142,12 @@ Renma supports existing skill-local references, profiles, and examples. The pref
 ```text
 skills/
   testing/
-    test-case-generation.skill.md
-    spec-review.skill.md
-    regression-planning.skill.md
+    test-case-generation/
+      SKILL.md
+    spec-review/
+      SKILL.md
+    regression-planning/
+      SKILL.md
 
 contexts/
   testing/
@@ -128,7 +176,12 @@ lenses/
     spec-review-boundary-values.md
 ```
 
-`contexts/` is preferred. `context/` is also scanned for compatibility. Files under either root are cataloged as first-class `context` assets, while experimental `context_lens` assets live under `lenses/` or opt in from context files with `type: context_lens`. Skill-local `references/` remain supported as `reference` assets.
+This is an illustrative domain-oriented layout, not a required repository
+schema. `contexts/` is preferred and `context/` is also scanned for
+compatibility. Files under either root are cataloged as first-class `context`
+assets, while `context_lens` assets live under `lenses/` or opt in from context
+files with `type: context_lens`. Skill-local `references/` remain supported as
+`reference` assets.
 
 ## What Renma Does Today
 
@@ -199,7 +252,7 @@ renma bom . --format json --omit-generated-at
 
 ### Repository Context BOM
 
-`renma bom` prints a declared Repository Context BOM generated from existing Renma evidence.
+`renma bom` prints a declared Repository Context BOM generated from existing Renma evidence. See the [Repository Context BOM contract](docs/repository-context-bom.md) for the authoritative v1 schema, snapshot, reproducibility, provenance, and future consumed-context evidence boundaries.
 
 ```bash
 renma bom . --format json
@@ -209,11 +262,11 @@ renma bom . --format json --omit-generated-at
 
 The BOM is a repository manifest, not a runtime usage report. It combines the catalog asset inventory, content hashes, owners, lifecycle metadata, declared dependency graph evidence, diagnostics, readiness checks, security posture, and security policy inventory into one reviewable artifact.
 
-Renma collects one shared repository evidence snapshot for BOM catalog assets and graph dependencies so those sections stay internally consistent.
+Renma derives each BOM from one in-memory repository snapshot: configuration, discovered artifacts, parsed documents, catalog, graph evidence, diagnostics, readiness, and security summaries all come from the same collected state.
 
 It does not describe what an LLM actually used, assemble prompts, select task-specific context, inject context into agents, import consumed-context evidence, or collect telemetry. JSON is the source of truth; Markdown is the compact pull-request review view.
 
-By default, `generatedAt` records the actual generation time. Use `--omit-generated-at` when CI or review automation needs to avoid clock-based diffs. This option only removes the run-time generation timestamp; it does not ignore repository metadata timestamps such as `lastReviewedAt` or `expiresAt`, and it does not normalize absolute `root` or `configPath` values.
+By default, `generatedAt` records the actual generation time. Use `--omit-generated-at` when CI or review automation needs to avoid clock-based diffs. With the same checkout path, config path, repository contents, Renma version, and UTC evaluation date, repeated `--omit-generated-at` runs should produce byte-identical JSON. The option does not remove metadata freshness dates, suppress freshness diagnostics, normalize absolute `root` or `configPath`, hide file moves, or guarantee portable byte-for-byte output across runners.
 
 ### Repeated context diagnostics
 
@@ -292,6 +345,10 @@ npx renma scaffold context contexts/testing/boundary-value-analysis.md --id cont
 npx renma scaffold context_lens lenses/testing/spec-review-boundary-values.md --id lens.testing.spec-review.boundary-values --title "Spec Review Boundary Values Lens" --owner qa-platform --tags testing,spec-review
 ```
 
+The Skill scaffold writes a canonical Agent Skills `SKILL.md` directly, with
+Renma governance values under flat, string-valued `metadata.renma.*` keys.
+Context and context-lens scaffolds retain their existing top-level metadata.
+
 Inspect a focused graph for the new skill:
 
 ```bash
@@ -322,7 +379,8 @@ Renma does not require an LLM for this loop. Its core analysis is deterministic
 
 ## Example repository
 
-See [`examples/context-repo`](examples/context-repo) for a small skill and shared-context repository you can scan with renma.
+See [`examples/context-repo`](examples/context-repo) for a repository-aware
+Skill and shared-context fixture you can inspect with Renma.
 
 See [`examples/context-lens`](examples/context-lens) for a Context Lens governance example with valid lenses, readiness output, inspect output, and expected diagnostics for an invalid lens.
 
@@ -330,6 +388,7 @@ See [`examples/context-lens`](examples/context-lens) for a Context Lens governan
 
 ```bash
 renma scan <path>
+renma bom <path>
 renma catalog <path>
 renma ownership <path>
 renma graph <path>
@@ -339,6 +398,7 @@ renma diff <path> --from <ref> --to <ref>
 renma ci-report <path> --from <ref> --to <ref>
 renma inspect <file>
 renma inspect <file> --lines L10-L42
+renma scaffold <skill|context|context_lens> <path>
 renma suggest-metadata <file>
 renma suggest-semantic-split <file>
 ```
@@ -379,15 +439,41 @@ Trust Graph helps reviewers inspect owner evidence, lifecycle status evidence, d
 
 ## What Gets Scanned
 
-By default, Renma looks for:
+Canonical Agent Skills entrypoints use the exact `SKILL.md` filename:
 
 ```text
 skills/**/SKILL.md
+.agents/skills/**/SKILL.md
+```
+
+Renma 0.16.0 requires Agent Skills format for operational Skills. Renma
+governance and security values use flat, string-valued `metadata.renma.*`
+entries; list values are JSON-array strings and booleans are the exact strings
+`"true"` or `"false"`. Pre-0.16 top-level Skill metadata is discovered only as
+migration input for `suggest-metadata`; catalog, ownership, graph, readiness,
+BOM, Trust Graph, lifecycle, and security consumers do not use it. Contexts and
+other non-Skill assets keep their existing top-level metadata syntax. See
+[Agent Skills Compatibility and Migration](docs/agent-skills-compatibility.md)
+for the normative boundary.
+
+Renma also discovers these historical spellings so `scan` can report migration
+diagnostics; they are not Agent Skills-compatible entrypoints:
+
+```text
 skills/**/skill.md
 skills/**/*.skill.md
-.agents/skills/**/SKILL.md
 .agents/skills/**/skill.md
 .agents/skills/**/*.skill.md
+```
+
+For migration, `skills/demo/skill.md` targets `skills/demo/SKILL.md`, while
+`skills/testing/spec-review.skill.md` targets
+`skills/testing/spec-review/SKILL.md`. `suggest-metadata` reports these path
+changes explicitly and does not edit files.
+
+Other default scan inputs include:
+
+```text
 .agents/**/*.md
 AGENTS.md
 README.md
@@ -435,7 +521,6 @@ Add `renma.config.json` at the repository root to tune discovery and CI behavior
   "format": "json",
   "globs": [
     "skills/**/SKILL.md",
-    "skills/**/skill.md",
     ".agents/skills/**/SKILL.md",
     "AGENTS.md",
     "contexts/**/*.md"
@@ -474,7 +559,9 @@ Each suppression requires a rule `id`, one or more path patterns, and an audit `
 
 ## Asset Metadata
 
-Renma works best when reusable assets declare lightweight metadata in front matter:
+Contexts and other non-Skill assets declare lightweight metadata in frontmatter
+using the existing top-level syntax. Skills use canonical Agent Skills
+frontmatter and `metadata.renma.*` as described above.
 
 ```markdown
 ---
@@ -491,7 +578,9 @@ requires_context:
 # Boundary Value Analysis
 ```
 
-Useful metadata includes:
+Useful metadata semantics include the following. The spellings shown here are
+the top-level non-Skill form; canonical Skills use the corresponding
+`metadata.renma.*` keys.
 
 - `id`: Stable catalog ID
 - `title`: Human-readable asset title
@@ -527,7 +616,10 @@ renma suggest-metadata skills/testing/spec-review/SKILL.md --format prompt
 
 `suggest-metadata` is not an auto-fixer. It tells a human or coding agent to inspect the existing asset, preserve existing frontmatter and Markdown body content, add only compact missing metadata that is clearly supported, and rerun `renma scan .` and `renma ownership .`. It does not infer owners. If you pass `--owner qa-platform`, the output may include that owner because it was explicitly provided; otherwise missing owner remains allowed and is reported as unowned by `ownership`. If an existing asset already declares an owner, `suggest-metadata` preserves it; a different `--owner` value is treated as a human-review ownership change, not an automatic metadata suggestion.
 
-Renma reads deterministic frontmatter from skills and context assets. YAML-style block lists are supported for selected metadata fields, which keeps authored metadata explicit and reviewable:
+For non-Skill assets, YAML-style block lists are supported for selected
+metadata fields, which keeps authored metadata explicit and reviewable.
+Pre-0.16 Skill fields may use this shape as migration input, but are not
+operational in Renma 0.16.0:
 
 ```yaml
 ---
@@ -557,7 +649,11 @@ superseded_by:
 ---
 ```
 
-Supported YAML-style block-list fields are `tags`, `when_to_use`, `when_not_to_use`, `requires_context`, `optional_context`, `conflicts`, and `superseded_by`. Renma supports lists for those metadata fields, not arbitrary nested maps; it does not infer missing dependencies with an LLM during `scan`.
+Supported YAML-style block-list fields in that syntax are `tags`,
+`when_to_use`, `when_not_to_use`, `requires_context`, `optional_context`,
+`conflicts`, and `superseded_by`. Canonical Skills instead encode the
+corresponding `renma.*` values as JSON-array strings. Renma does not infer
+missing dependencies with an LLM during `scan`.
 
 Catalog and scan diagnostics preserve field-level evidence for metadata. For
 block-list dependency fields such as `requires_context` and `optional_context`,
@@ -675,11 +771,14 @@ Renma reports deterministic safety findings for agent-facing operational instruc
 
 These findings are guardrails for review. They do not replace secret scanning, SAST, dependency scanning, or human security review.
 
-Near-term security work is focused on stabilizing these diagnostics for the 0.7.0 line. Renma now summarizes security posture in readiness and CI reports, and exposes Trust Graph evidence for effective policy, security profile resolution, approved destinations, forbidden inputs, human approval requirements, and high-risk findings.
+Renma summarizes security posture in Readiness and CI reports, and exposes
+Trust Graph evidence for effective policy, security profile resolution,
+approved destinations, forbidden inputs, human approval requirements, and
+high-risk findings.
 
 Trust Graph interprets existing catalog, graph, scan, and security evidence as deterministic repository evidence. It is not a runtime system, not enforcement, not context selection or prompt assembly, not telemetry collection, not an LLM call, and not a subjective trust score.
 
-Repository Context BOM is a declared repository manifest of assets, hashes, owners, lifecycle states, dependencies, security posture, diagnostics, and readiness evidence. It does not claim what an LLM actually used at runtime. Later external consumed-context evidence may be imported and validated against Renma's repository model, while telemetry collection remains outside Renma.
+Repository Context BOM is a declared repository manifest of assets, hashes, owners, lifecycle states, dependencies, security posture, diagnostics, and readiness evidence. It does not claim what an LLM actually used at runtime. The v1 contract deliberately keeps Git revision identity in the surrounding CI/PR artifact context and keeps any future consumed-context evidence separate from the declared BOM meaning. See the [Repository Context BOM contract](docs/repository-context-bom.md).
 
 ## Design Notes
 
@@ -708,6 +807,7 @@ node dist/index.js scan .
 
 ## Documentation
 
+- [Agent Skills Compatibility and Migration](docs/agent-skills-compatibility.md)
 - [User Manual](docs/user-manual.md)
 - [Authoring Guide](docs/authoring-guide.md)
 - [Security Policy Guide](docs/security-policy.md)

package/dist/agent-skills.d.ts

@@ -0,0 +1,77 @@
+import { type AgentSkillDiagnosticId } from "./diagnostic-ids.js";
+import type { ParsedDocument } from "./types.js";
+import { type ParsedYamlFrontmatter } from "./yaml-frontmatter.js";
+export declare const AGENT_SKILLS_SPECIFICATION = "https://agentskills.io/specification";
+export declare const AGENT_SKILLS_VALIDATION_PROFILE = "agentskills.io/specification@2026-07-11";
+export declare const AGENT_SKILLS_TOP_LEVEL_FIELDS: readonly ["name", "description", "license", "compatibility", "metadata", "allowed-tools"];
+export declare const LEGACY_RENMA_SKILL_FIELDS: readonly ["id", "title", "version", "owner", "status", "purpose", "last_reviewed_at", "review_cycle", "expires_at", "tags", "when_to_use", "when_not_to_use", "requires_context", "optional_context", "requires_lens", "optional_lens", "conflicts", "superseded_by", "allowed_data", "network_allowed", "external_upload_allowed", "secrets_allowed", "requires_human_approval", "forbidden_inputs", "approved_network_destinations", "approved_upload_destinations", "security_profile"];
+export type AgentSkillFormat = "agent-skills" | "renma-legacy" | "hybrid" | "unknown";
+export interface AgentSkillValidationIssue {
+    code: AgentSkillDiagnosticId;
+    severity: "error" | "warning";
+    category: "specification" | "renma-authoring";
+    path: string;
+    startLine: number;
+    endLine: number;
+    message: string;
+    field?: string;
+    details?: Record<string, unknown>;
+}
+export interface AgentSkillValidationResult {
+    path: string;
+    format: AgentSkillFormat;
+    valid: boolean;
+    name?: string;
+    description?: string;
+    migrationRecommended: boolean;
+    migrationDirection?: "legacy-to-agent-skills";
+    migrationCommand?: AgentSkillMigrationCommand;
+    legacyFields: string[];
+    canonicalRenmaFields: string[];
+    errorCount: number;
+    warningCount: number;
+    issues: AgentSkillValidationIssue[];
+}
+export interface AgentSkillInspection {
+    frontmatter: ParsedYamlFrontmatter;
+    validation: AgentSkillValidationResult;
+}
+export interface AgentSkillMigrationCommand {
+    command: "renma";
+    args: ["suggest-metadata", string];
+    display: string;
+}
+export interface AgentSkillsValidationSummary {
+    specification: string;
+    profile: string;
+    totalSkillCount: number;
+    validSkillCount: number;
+    invalidSkillCount: number;
+    canonicalSkillCount: number;
+    legacySkillCount: number;
+    hybridSkillCount: number;
+    warningCount: number;
+    results: AgentSkillValidationResult[];
+}
+export interface AgentSkillNameValidation {
+    normalized: string | undefined;
+    problems: string[];
+}
+/** Validate every discovered Skill using one locally versioned Agent Skills profile. */
+export declare function validateAgentSkills(documents: ParsedDocument[]): AgentSkillsValidationSummary;
+/** Validate one discovered Skill without changing any operational metadata reader. */
+export declare function validateAgentSkill(document: ParsedDocument): AgentSkillValidationResult;
+/** Parse and validate a Skill once for canonical operational consumers. */
+export declare function inspectAgentSkill(document: ParsedDocument): AgentSkillInspection;
+/** Resolve the YAML description value used by Skill quality rules. */
+export declare function resolvedAgentSkillDescription(document: ParsedDocument): string | undefined;
+/** Normalize and validate an Agent Skills YAML name field. */
+export declare function normalizeAgentSkillNameField(value: unknown): AgentSkillNameValidation;
+/** Normalize and validate a Skill directory name without changing filesystem identity. */
+export declare function normalizeAgentSkillDirectoryName(value: unknown): AgentSkillNameValidation;
+/** Backward-compatible name for validating an Agent Skills YAML name field. */
+export declare function validateAgentSkillName(value: unknown): AgentSkillNameValidation;
+export declare function legacyRenmaMetadataKey(field: string): string | undefined;
+/** Return all Markdown line numbers occupied by backtick or tilde fences. */
+export declare function agentSkillFenceLines(lines: string[], bodyStartLine: number): Set<number>;
+//# sourceMappingURL=agent-skills.d.ts.map

package/dist/agent-skills.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"agent-skills.d.ts","sourceRoot":"","sources":["../src/agent-skills.ts"],"names":[],"mappings":"AAEA,OAAO,EAEL,KAAK,sBAAsB,EAC5B,MAAM,qBAAqB,CAAC;AAE7B,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,YAAY,CAAC;AACjD,OAAO,EAEL,KAAK,qBAAqB,EAE3B,MAAM,uBAAuB,CAAC;AAE/B,eAAO,MAAM,0BAA0B,yCACC,CAAC;AACzC,eAAO,MAAM,+BAA+B,4CACD,CAAC;AAE5C,eAAO,MAAM,6BAA6B,2FAOhC,CAAC;AAEX,eAAO,MAAM,yBAAyB,4dA4B5B,CAAC;AAQX,MAAM,MAAM,gBAAgB,GACxB,cAAc,GACd,cAAc,GACd,QAAQ,GACR,SAAS,CAAC;AAEd,MAAM,WAAW,yBAAyB;IACxC,IAAI,EAAE,sBAAsB,CAAC;IAC7B,QAAQ,EAAE,OAAO,GAAG,SAAS,CAAC;IAC9B,QAAQ,EAAE,eAAe,GAAG,iBAAiB,CAAC;IAC9C,IAAI,EAAE,MAAM,CAAC;IACb,SAAS,EAAE,MAAM,CAAC;IAClB,OAAO,EAAE,MAAM,CAAC;IAChB,OAAO,EAAE,MAAM,CAAC;IAChB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,OAAO,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;CACnC;AAED,MAAM,WAAW,0BAA0B;IACzC,IAAI,EAAE,MAAM,CAAC;IACb,MAAM,EAAE,gBAAgB,CAAC;IACzB,KAAK,EAAE,OAAO,CAAC;IACf,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,oBAAoB,EAAE,OAAO,CAAC;IAC9B,kBAAkB,CAAC,EAAE,wBAAwB,CAAC;IAC9C,gBAAgB,CAAC,EAAE,0BAA0B,CAAC;IAC9C,YAAY,EAAE,MAAM,EAAE,CAAC;IACvB,oBAAoB,EAAE,MAAM,EAAE,CAAC;IAC/B,UAAU,EAAE,MAAM,CAAC;IACnB,YAAY,EAAE,MAAM,CAAC;IACrB,MAAM,EAAE,yBAAyB,EAAE,CAAC;CACrC;AAED,MAAM,WAAW,oBAAoB;IACnC,WAAW,EAAE,qBAAqB,CAAC;IACnC,UAAU,EAAE,0BAA0B,CAAC;CACxC;AAED,MAAM,WAAW,0BAA0B;IACzC,OAAO,EAAE,OAAO,CAAC;IACjB,IAAI,EAAE,CAAC,kBAAkB,EAAE,MAAM,CAAC,CAAC;IACnC,OAAO,EAAE,MAAM,CAAC;CACjB;AAED,MAAM,WAAW,4BAA4B;IAC3C,aAAa,EAAE,MAAM,CAAC;IACtB,OAAO,EAAE,MAAM,CAAC;IAChB,eAAe,EAAE,MAAM,CAAC;IACxB,eAAe,EAAE,MAAM,CAAC;IACxB,iBAAiB,EAAE,MAAM,CAAC;IAC1B,mBAAmB,EAAE,MAAM,CAAC;IAC5B,gBAAgB,EAAE,MAAM,CAAC;IACzB,gBAAgB,EAAE,MAAM,CAAC;IACzB,YAAY,EAAE,MAAM,CAAC;IACrB,OAAO,EAAE,0BAA0B,EAAE,CAAC;CACvC;AAED,MAAM,WAAW,wBAAwB;IACvC,UAAU,EAAE,MAAM,GAAG,SAAS,CAAC;IAC/B,QAAQ,EAAE,MAAM,EAAE,CAAC;CACpB;AAED,wFAAwF;AACxF,wBAAgB,mBAAmB,CACjC,SAAS,EAAE,cAAc,EAAE,GAC1B,4BAA4B,CA0B9B;AAED,sFAAsF;AACtF,wBAAgB,kBAAkB,CAChC,QAAQ,EAAE,cAAc,GACvB,0BAA0B,CAG5B;AAED,2EAA2E;AAC3E,wBAAgB,iBAAiB,CAC/B,QAAQ,EAAE,cAAc,GACvB,oBAAoB,CAMtB;AAED,sEAAsE;AACtE,wBAAgB,6BAA6B,CAC3C,QAAQ,EAAE,cAAc,GACvB,MAAM,GAAG,SAAS,CAKpB;AA0LD,8DAA8D;AAC9D,wBAAgB,4BAA4B,CAC1C,KAAK,EAAE,OAAO,GACb,wBAAwB,CAE1B;AAED,0FAA0F;AAC1F,wBAAgB,gCAAgC,CAC9C,KAAK,EAAE,OAAO,GACb,wBAAwB,CAE1B;AAED,+EAA+E;AAC/E,wBAAgB,sBAAsB,CACpC,KAAK,EAAE,OAAO,GACb,wBAAwB,CAE1B;AA+BD,wBAAgB,sBAAsB,CAAC,KAAK,EAAE,MAAM,GAAG,MAAM,GAAG,SAAS,CAIxE;AAsXD,6EAA6E;AAC7E,wBAAgB,oBAAoB,CAClC,KAAK,EAAE,MAAM,EAAE,EACf,aAAa,EAAE,MAAM,GACpB,GAAG,CAAC,MAAM,CAAC,CAgCb"}