Renma v0.38.1

Renma v0.38.1 includes 5 changelog entries across changed.

This release covers changes from v0.38.0 to v0.38.1.

Highlights

Changed

• Improved the CI report’s diagnostic severity policy section with a comparison
  table, direction indicators, and concise CI-impact guidance. Policy evaluation
  and JSON output are unchanged.
• Aligned remaining guide help, scaffold handoff, and execution-constraint
  warning text with evidence-first, conditional clarification. Diagnostic
  consumer guidance scopes blocked recommendations to their dependent changes
  and avoids rerunning unchanged evidence solely because a user replied.
  Diagnostic detection, severity, approval gates, and JSON schemas are unchanged.
• Clarified model-neutral Skill authoring: decision tables and progress formats
  are optional working aids, questions concern unresolved blocking decisions,
  and independent investigation can continue while preserving the creation
  gate, source authority, ownership, and separate approval requirements.
• Reduced default guide repetition while retaining disposition and
  platform-handoff reference tables in the complete JSON guide. Guide and
  handoff schema identities, fields, and governance boundaries are unchanged.
• Aligned guide, scaffold, and authoring documentation on relevant validation,
  conditional report commands, and evidence-based repetition of checks.
  Required CI and release checks retain their scope. Clarified that a metadata
  no-proposal result does not stop separately requested Skill-body work.

Upgrade

npm install
npm run build
npm test

If using the published package:

npm install -g renma@0.38.1

Validation

Validated with:

npm test
npm run build
npm run verify:api
node dist/index.js scan . --fail-on high --strict
node dist/index.js catalog . --format markdown
node dist/index.js readiness . --format markdown
node dist/index.js graph . --focus skill.release-prep --format mermaid
node dist/index.js diff . --from v0.38.0 --to v0.38.1 --format markdown
node dist/index.js ci-report . --from v0.38.0 --to v0.38.1 --format markdown

Summary

v0.38.1 includes 5 changelog entries across changed.

Renma v0.38.0

Renma v0.38.0 includes 2 changelog entries across added.

This release covers changes from v0.37.2 to v0.38.0.

Highlights

Added

• Added revoked as a first-class inactive lifecycle status for explicit
  withdrawal of trust or authorization because of a known problem. Revoked
  assets require reviewed reason/date evidence, remain unusable for active
  composition and Discovery, retain lifecycle evidence across catalog,
  inspect, Readiness, BOM, and Trust Graph projections, and produce dedicated
  required/optional dependency findings without propagating status to
  dependents. Required revoked dependencies default to High and optional ones
  to Low, with repository overrides through diagnostics.severity.
• Added repository-wide scan-finding severity policy through
  diagnostics.severity, keyed by stable diagnostic ID. Effective severity now
  feeds scan output, suppression evidence, failure thresholds, Readiness, diff,
  and CI projections while retaining the producer default as traceability.
  diagnostics.ci_policy governs severity-policy weakening with the stricter
  compared endpoint, including attempts to weaken the guard in the same change.
  Policy diff resolves built-in severity independently of emitted findings,
  compares effective values for both added and removed overrides, represents
  equal transitions as neutral, and requires review when the built-in severity
  cannot be resolved to one static value. Existing catalog error diagnostics
  retain their established High scan-Finding conversion. Configuration now
  accepts only IDs registered on the configurable scan-Finding surface and
  rejects stable raw-diagnostic IDs that the policy cannot affect.

Upgrade

npm install
npm run build
npm test

If using the published package:

npm install -g renma@0.38.0

Validation

Validated with:

npm test
npm run build
npm run verify:api
node dist/index.js scan . --fail-on high --strict
node dist/index.js catalog . --format markdown
node dist/index.js readiness . --format markdown
node dist/index.js graph . --focus skill.release-prep --format mermaid
node dist/index.js diff . --from v0.37.2 --to v0.38.0 --format markdown
node dist/index.js ci-report . --from v0.37.2 --to v0.38.0 --format markdown

Summary

v0.38.0 includes 2 changelog entries across added.

Renma v0.37.2

Renma v0.37.2 includes 1 changelog entry across changed.

This release covers changes from v0.37.1 to v0.37.2.

Highlights

Changed

• Replaced the stable renma.skill-authoring-guide.v1 JSON contract with
  renma.skill-authoring-guide.v2. V2 preserves Renma's creation-gate, evidence,
  asset-boundary, handoff, and human-review guarantees while changing interaction
  semantics from a prescribed clarification protocol to adaptive authoring
  activities. Clarification is conditional, question batching and blocker
  presentation are adaptive, prerequisite-aware questioning is required,
  human-review rules have an explicit field, and recursive external traversal has
  a compact applicability pointer. The gate may be declared passed only after
  every requirement, including the smallest justified asset structure, is
  established and no Blocking decision remains; this dependency does not
  prescribe an internal reasoning sequence. Consumers must branch on
  schemaVersion and must not apply v1 phase-order, mandatory-clarification,
  fixed-batch, or last-phase assumptions to v2.

Upgrade

npm install
npm run build
npm test

If using the published package:

npm install -g renma@0.37.2

Validation

Validated with:

npm test
npm run build
npm run verify:api
node dist/index.js scan . --fail-on high --strict
node dist/index.js catalog . --format markdown
node dist/index.js readiness . --format markdown
node dist/index.js graph . --focus skill.release-prep --format mermaid
node dist/index.js diff . --from v0.37.1 --to HEAD --format markdown
node dist/index.js ci-report . --from v0.37.1 --to HEAD --format markdown

Summary

v0.37.2 includes 1 changelog entry across changed.

Renma v0.37.1

Renma v0.37.1 includes 2 changelog entries across changed.

This release covers changes from v0.37.0 to v0.37.1.

Highlights

Changed

• Clarified the default Skill guide prompt and stable JSON guide so generated
  artifacts retain bounded producer-scoped evidentiary value without becoming
  governing authority, review consequences are evidence-backed or potential
  impacts are labeled Proposed or Unresolved, and material handoff evidence is
  rechecked when current applicability cannot be established.
• Made npm test emit a single summary on success and failure-only diagnostics
  on error to reduce LLM context usage. Full per-test output remains available
  through npm run test:verbose.

Upgrade

npm install
npm run build
npm test

If using the published package:

npm install -g renma@0.37.1

Validation

Validated with:

npm test
npm run build
npm run verify:api
node dist/index.js scan . --fail-on high --strict
node dist/index.js catalog . --format markdown
node dist/index.js readiness . --format markdown
node dist/index.js graph . --focus skill.release-prep --format mermaid
node dist/index.js diff . --from v0.37.0 --to v0.37.1 --format markdown
node dist/index.js ci-report . --from v0.37.0 --to v0.37.1 --format markdown

Summary

v0.37.1 includes 2 changelog entries across changed.

Renma v0.37.0

Renma v0.37.0 includes 1 changelog entry across changed.

This release covers changes from v0.36.1 to v0.37.0.

Highlights

Changed

• Made the typed Diagnostics v2 repair model the standard Finding contract.
  The typed verificationStepsV2 field is now verificationSteps, and the
  legacy string-only constraints and verificationSteps projections were
  removed together with their internal compatibility layer. Findings now expose
  repairConstraints and verificationSteps directly as typed guidance.

Upgrade

npm install
npm run build
npm test

If using the published package:

npm install -g renma@0.37.0

Validation

Validated with:

npm test
npm run build
npm run verify:api
node dist/index.js scan . --fail-on high --strict
node dist/index.js catalog . --format markdown
node dist/index.js readiness . --format markdown
node dist/index.js graph . --focus skill.release-prep --format mermaid
node dist/index.js diff . --from v0.36.1 --to HEAD --format markdown
node dist/index.js ci-report . --from v0.36.1 --to HEAD --format markdown

Summary

v0.37.0 includes 1 changelog entry across changed.

Renma v0.36.1

Renma v0.36.1 includes 28 changelog entries across changed.

This release covers changes from v0.36.0 to v0.36.1.

Highlights

Changed

• Narrowed 27 security-analysis helper types to their owning modules. Their
  definitions and the function signatures that use them are unchanged, while
  unsupported internal deep-import surfaces no longer expose local-only names.
• Narrowed body-policy lexical exports to the completed patterns and
  recognizers used by neighboring analyzers. Regex vocabulary fragments used
  only to assemble those patterns now remain private to their owner module;
  diagnostic behavior is unchanged.
• Narrowed internal security-command dependencies to import destination
  analysis functions and types from their owning modules instead of routing
  through the security-destination subsystem entrypoint. Public exports and
  runtime behavior remain unchanged.
• Simplified the security-destination subsystem entrypoint so bindings used
  only for forwarding are re-exported directly from their owners. The cohesive
  entrypoint and all destination-analysis consumers remain unchanged.
• Moved the public JSON schema inventory from production commands to test
  support, its only consumer. Compatibility tests still derive every identifier
  from its runtime owner, while the unused production module is no longer built
  or packaged.
• Folded the single-consumer Markdown source-to-visible offset projection into
  MarkdownSecurityView. The standalone implementation module and its exported
  working types were removed without changing Markdown parsing or diagnostic
  source mapping.
• Replaced the single-consumer rule-engine abstraction with a local function
  registry in rules.ts. Eleven decorative registry IDs, object wrappers, and
  the unreachable optional-config guard were removed without changing finding
  IDs, evaluation order, or diagnostics.
• Removed two destination-analysis composition wrappers that were used only by
  tests. Production consumers continue to use the underlying typed analysis and
  intent projections directly; test-only convenience stays in test code.
• Enabled TypeScript's unused-local and unused-parameter checks across source
  and tests, and removed the nine unused imports, locals, parameters, and test
  helpers they exposed. Runtime behavior and test coverage remain unchanged.
• Removed the remaining cross-owner internal type re-exports from executable
  inventory, body-policy clause analysis, and security-command working types.
  Consumers now import those contracts from their defining modules; intentional
  public facades and cohesive subsystem entrypoints remain unchanged.
• Made 63 command- and CLI-local types module-private after verifying that they
  have no cross-file consumers. Cross-module command contracts and every public
  package entrypoint remain unchanged.
• Narrowed the internal runtime surface by making 33 helpers module-private
  after verifying that they have no cross-file consumers. Public package
  entrypoints, schema identities, and type contracts remain unchanged.
• Removed five zero-consumer internal declarations: the historical Agent Skill
  name-validation wrapper, three unused derived types, and one unused body-policy
  test projection helper.
• Consolidated internal module ownership by removing cross-owner re-exports
  from metadata parsing, discovery, repository paths, and security diagnostics.
  Internal consumers now import metadata definitions, Skill path contracts,
  helper-command evidence, and destination analysis from their cohesive owners;
  the supported renma/discovery public surface remains unchanged.
• Removed the internal AGENT_SKILLS_TOP_LEVEL_FIELDS re-export from
  agent-skills.ts; internal contract tests now import the metadata definition
  owner directly.
• Removed the unused internal CanonicalSecurityOperationalField re-export
  from security-policy.ts; its definition remains owned by
  metadata-definitions.ts.
• Removed the one-line internal context-language-diagnostics.ts facade;
  catalog analysis now imports its implementation owner directly.
• Removed the internal AssetOwnership re-export from model.ts; command
  consumers now import the cohesive governance type owner directly.
• Removed Catalog Finding compatibility re-exports from scanner.ts; the
  ordered definition registry and diagnostic conversion remain owned only by
  catalog-findings.ts.
• Removed internal result-type and renderer compatibility re-exports from the
  inspect and suggest-metadata command modules. Internal consumers now import
  the evidence, decision, and renderer owners directly.
• Removed the final internal dependency-layer exception by keeping the
  single-use classification index projection inside repository snapshot
  construction instead of a higher-layer evidence module.
• Removed the unused internal src/types.ts compatibility facade and updated
  tests to import cohesive type owners directly. The supported renma/types
  package export remains owned by src/public-types.ts and is unchanged.
• Froze the Renma 1.0 release-candidate top-level JSON schema identities while
  retaining the existing whole-document, published-schema, semantic-contract,
  and public TypeScript API compatibility checks. The experimental execution
  contract and internal working models remain outside the freeze.
• Made normalized scan diagnostics the canonical internal
  ScanResult.diagnostics collection behind the v2 serializer. Renamed the
  producer-level collection to internal rawDiagnostics and moved scan
  normalization and review bundling from the version-named module to
  scan-diagnostics without changing public output.
• Replaced the three overlapping pre-1.0 scan JSON projections with the
  renma.scan.v2 contract. Active results now use one normalized diagnostics
  array, suppressed results use suppressedDiagnostics, and the wire-level
  findings, suppressedFindings, and diagnosticsV2 fields were removed.
• Made diff and ci-report collect each archived repository revision once.
  CI now applies its fail-closed endpoint boundary while building the shared
  target snapshot, then derives both semantic diff and CI policy output from
  that snapshot instead of rediscovering the target revision.
• Reduced prose-only safeguard-bypass, risky-failure-suppression,
  instruction-hierarchy, and untrusted-content inference to explicit local
  line or clause evidence and advisory severity. Structural POSIX shell,
  PowerShell, and Windows batch analysis remains in place.
• Documented the Renma 1.0 stabilization boundary, including retention of the
  existing ci-report GitHub Actions workflow and the separation between
  structural command evidence and incomplete natural-language review aids.

Upgrade

npm install
npm run build
npm test

If using the published package:

npm install -g renma@0.36.1

Validation

Validated with:

npm test
npm run build
npm run verify:api
node dist/index.js scan . --fail-on high --strict
node dist/index.js catalog . --format markdown
node dist/index.js readiness . --format markdown
node dist/index.js graph . --focus skill.release-prep --format mermaid
node dist/index.js diff . --from v0.36.0 --to HEAD --format markdown
node dist/index.js ci-report . --from v0.36.0 --to HEAD --format markdown

Summary

v0.36.1 includes 28 changelog entries across changed.

Renma v0.36.0

Renma v0.36.0 includes 11 changelog entries across added and changed.

This release covers changes from v0.35.0 to v0.36.0.

Highlights

Added

• Added a concise public security policy covering supported versions, private
  vulnerability reporting, and coordinated disclosure without promising a
  response SLA.
• Added SEC-RISKY-OPERATION-ERROR-SUPPRESSION for bounded shell and prose
  instructions that explicitly hide failure from an already-recognized
  destructive, privileged, upload, or sensitive-data operation. Destructive
  and privileged shell evidence requires the risky executable in command
  position instead of a quoted argument mention, while static executable paths,
  bounded wrappers, and existing upload classification remain supported.
• Added SEC-INSTRUCTION-HIERARCHY-OVERRIDE for explicit, bounded attempts to
  supersede system, developer, platform, prior, or higher-level instructions
  without treating ordinary persona wording, correct authority ordering,
  bounded questions, explicit attribution, or defensive statements as
  violations; bare prompt mentions and earlier independent clauses cannot
  suppress an operational override.

Changed

• Clarified that a Context Asset is a Git-reviewed governance entry point for
  independently maintained knowledge whose authoritative content may remain in
  an external governed system without being copied into contexts/.
• Defined the 1.x diagnostic and rule evolution policy, including stable-ID,
  severity, and behavioral CI compatibility expectations for patch, minor, and
  major releases.
• Release preparation now verifies both the document-level and root-package
  versions in lockfile v3 against the target release version.
• Destructive and privileged shell diagnostics now classify bounded shell text
  as literal-only, operational, or unknown. Quoted risky text is suppressed
  only along proven literal-only command and data paths; shell -c/eval
  contexts and standard input consumed as shell code remain operational, while
  unrecognized wrappers, consumers, and shell options use conservative
  matching.
• Shell-wrapper execution evidence now distinguishes proven execution, known
  non-execution modes, and unknown options, so lookup, help, or version modes
  stay inert while unrecognized options retain conservative command-risk
  matching.
• The npm publication workflow now blocks its OIDC-enabled publish job on the
  existing deterministic release metadata contract as well as exact annotated
  tag, origin/main, and package-version identity.
• Bounded negative-subject safeguard instructions such as “No Skill … may
  bypass” no longer overlap with SEC-SAFEGUARD-BYPASS-INSTRUCTION; a later
  independently expressed bypass remains reportable.
• Made the pre-1.0 compatibility boundary explicit without changing stable CLI
  behavior or stable JSON output: scan JSON now uses an explicit wire
  projection, supported TypeScript entrypoints have a checked declaration
  snapshot, classification wire enums are documented and typed as open while
  known-value helpers remain closed, typed diagnostic repair guidance is the
  internal authority for legacy text projections, and asset path normalization
  rejects every parent-directory segment without an unreachable normalization
  branch.

Upgrade

npm install
npm run build
npm test

If using the published package:

npm install -g renma@0.36.0

Validation

Validated with:

npm test
npm run build
npm run verify:api
node dist/index.js scan . --fail-on high --strict
node dist/index.js catalog . --format markdown
node dist/index.js readiness . --format markdown
node dist/index.js graph . --focus skill.release-prep --format mermaid
node dist/index.js diff . --from v0.35.0 --to HEAD --format markdown
node dist/index.js ci-report . --from v0.35.0 --to HEAD --format markdown

Summary

v0.36.0 includes 11 changelog entries across added and changed.

Renma v0.35.0

Renma v0.35.0 includes 3 changelog entries across added and changed.

This release covers changes from v0.34.0 to v0.35.0.

Highlights

Added

• Added focused macOS and Windows CI evidence for path, filesystem,
  shell-family parsing, package startup, and representative JSON behavior while
  retaining the complete Linux quality gate.
• Added SEC-EXECUTABLE-AS-POLICY-AUTHORITY for the bounded case where a
  recognized inline Skill helper is explicitly made the allow/deny authority
  for a security-relevant operation.

Changed

• Completed whole-document golden compatibility assurance for every stable
  public JSON producer except Trust Graph v2, which retains its published JSON
  Schema and frozen exact semantic-contract test. Documented the 1.x stability
  policy and retained the published renma.trustGraph.v2 spelling.

Upgrade

npm install
npm run build
npm test

If using the published package:

npm install -g renma@0.35.0

Validation

Validated with:

npm test
npm run build
node dist/index.js scan . --fail-on high --strict
node dist/index.js catalog . --format markdown
node dist/index.js readiness . --format markdown
node dist/index.js graph . --focus skill.release-prep --format mermaid
node dist/index.js diff . --from v0.34.0 --to HEAD --format markdown
node dist/index.js ci-report . --from v0.34.0 --to HEAD --format markdown

Summary

v0.35.0 includes 3 changelog entries across added and changed.

Renma v0.34.0

Renma v0.34.0 includes 13 changelog entries across added, changed, fixed, and removed.

This release covers changes from v0.33.0 to v0.34.0.

Highlights

Added

• Added the public ScanJsonDocument type for the serialized
  renma.scan.v1 wire contract while retaining ScanResult as the internal
  core scan result, plus an internal stable/experimental registry synchronized with the
  documented public top-level JSON schema inventory.
• Added bounded inspection evidence for explicitly referenced noncanonical
  Agent Skills package files. Exact local targets remain separate from
  canonical Renma support/governance, while excluded, oversized, depth-limited,
  symlinked, and unreadable targets now block strict completeness.

Changed

• Changed Readiness from renma.readiness.v1 to renma.readiness.v2 and
  Repository Context BOM from v2 to renma.repository-context-bom.v3. The
  breaking migration replaces the producerless
  layout.disallowed_skill_assets check with skills.support_integrity, which
  is backed by authoritative static-support inspection coverage plus
  missing-reference evidence. Excluded, symlinked, unreadable, oversized,
  depth-limited, and unsupported explicit support now fail the check without
  allowing finding suppression to manufacture inspection completeness. BOM v3
  otherwise carries forward the v2 field contract.
• Narrowed renma/discovery to canonical Skill entrypoint types, renamed the
  Skill-specific path helper to normalizeRepositorySkillRelativePath, and
  kept lowercase and flat historical entrypoint recognition inside explicit
  migration tooling.
• Renamed the Renma-owned unsupported routing metadata warning to
  RN-SKILL-UNSUPPORTED-ROUTING-METADATA without changing its warning
  severity, authoring category, Skill validity, or non-operational semantics.
• Kept SecurityAnalysisCoverage on the cohesive renma/types facade without
  adding a separate focused package subpath.
• Narrowed ScanJsonDocument.format to the literal "json" and made the JSON
  serializer enforce that wire invariant without changing renma.scan.v1 CLI
  output.
• Reduced the pre-1.0 npm type surface to contracts with supported producers:
  scan JSON, diagnostics, classification/discovery, and composed security
  coverage. Low-level parser/runtime models remain available to Renma source
  modules but are no longer package exports.

Fixed

• Made production ordering and selection for scan, catalog, graph, Trust
  Graph, BOM, Readiness, diff/CI, executable evidence, suppressions, and the
  experimental execution-contract digest explicitly locale-independent by
  using one ECMAScript UTF-16 code-unit comparator. Existing schema identifiers
  remain unchanged for this implementation fix because those contracts already
  promised deterministic stable ordering; Readiness and BOM change versions
  only for their separate check-collection migration.
• Rejected conventional and explicit configuration paths that are symlinks,
  cross a symlinked parent, are outside the repository, or are not regular
  files. Broken conventional config symlinks now fail as caller-correctable
  configuration errors instead of silently selecting defaults.

Removed

• Removed the producerless pre-1.0 diagnostic IDs
  LAYOUT-SKILL-EXECUTABLE-COMMAND, LAYOUT-SKILL-NOT-THIN,
  PATH-HELPER-COMMAND-SKILL-SCRIPTS, and
  LAYOUT-DISALLOWED-SKILL-ASSET, including their compatibility-only
  documentation and Diagnostics V2 grouping surface.
• Removed the compatibility-only layout configuration surface, including
  tool_namespace, workflow_aliases, LayoutPolicyConfig, and normalized
  ScanConfig layout state. Authored layout objects now fail with explicit
  pre-1.0 deletion guidance and no replacement key.
• Removed package subpaths for raw artifacts, parsed metadata, normalized
  runtime configuration, internal decision/governance projections, and the
  producerless core ScanResult type before 1.0.

Upgrade

npm install
npm run build
npm test

If using the published package:

npm install -g renma@0.34.0

Validation

Validated with:

npm test
npm run build
node dist/index.js scan . --fail-on high
node dist/index.js catalog . --format markdown
node dist/index.js readiness . --format markdown
node dist/index.js graph . --focus skill.release-prep --format mermaid
node dist/index.js diff . --from v0.33.0 --to HEAD --format markdown
node dist/index.js ci-report . --from v0.33.0 --to HEAD --format markdown

Summary

v0.34.0 includes 13 changelog entries across added, changed, fixed, and removed.

Renma v0.33.0

Renma v0.33.0 includes 15 changelog entries across added, changed, fixed, and removed.

This release covers changes from v0.32.1 to v0.33.0.

Highlights

Added

• Extended renma.inspection-coverage.v1 to close statically proven
  Skill-support inspection gaps. A reachable local support target that becomes
  excluded, oversized, unreadable, depth-limited, symlinked, or otherwise
  uninspectable now contributes exact blocking evidence with static-reference
  provenance, so --strict continues to fail through
  strict_scan.incomplete_inspection and inspection-coverage diffs expose
  parsed-to-blocked regressions. Authority still requires one unambiguous
  owning Skill and a fully parsed source chain; unreferenced support and
  unknown transitive children remain outside this boundary, and unparsed
  targets do not receive synthetic security-analysis coverage rows.
• Extended CST-backed YAML frontmatter-comment security analysis from Skills
  to eligible, known non-Skill Markdown artifacts with a closed Renma
  frontmatter envelope. Comments retain the raw-agent-visible,
  no-policy-authority boundary and exact source evidence; successful
  zero-comment extraction reports yamlFrontmatterComments: "analyzed",
  while malformed input remains non-analyzable and arbitrary unknown
  Markdown remains out of scope.
• Hardened HTML-comment security projection to use the same raw-agent-visible,
  no-policy-authority trust boundary as YAML frontmatter comments. Inner
  Markdown presentation and negative-example labels can no longer opt hidden
  security-sensitive text out of analysis, and policy-looking comment text
  cannot authorize or allowlist its own projection.
• Added semantic security analysis for discovered UTF-8 .txt Skill support
  files only when the existing repository-local static-reference graph proves
  them reachable from exactly one owning Skill. Reachable plain-text support
  now reports semanticInstructions: "analyzed"; otherwise identical
  unreferenced text remains unsupported, and structured, executable, binary,
  external, escaping, symlinked, and unresolved targets remain outside this
  capability.
• Added versioned renma.security-analysis-coverage.v1 scan JSON evidence for
  every discovered and scanned artifact. The target-state rows distinguish
  executed, unsupported, inapplicable, and non-analyzable hidden-Unicode,
  Markdown semantic instruction, canonical Skill description, and YAML
  frontmatter comment layers without changing findings or CI policy.

Changed

• Finalized the pre-1.0 repository contract around one operational spelling:
  shared Context Assets use contexts/**; Skills use exact SKILL.md under a
  supported Skill root; configuration uses renma.config.jsonc or
  renma.config.json; Context Lenses use applies_to and
  expected_outputs; and security-profile policy fields use their documented
  canonical spelling. Historical paths, .renma.json, Lens aliases, profile
  aliases, and canonical_context now produce explicit migration diagnostics
  or configuration errors without operational interpretation.
• Made portable Agent Skills description the sole Skill capability and
  selection-boundary source. renma.when-to-use and renma.when-not-to-use
  are unsupported and ignored operationally with migration-oriented authoring
  warnings; pre-0.16 top-level routing fields remain one-way migration evidence
  only and may help recover description.
• Restricted non-Skill local security-policy authority to canonical, closed
  Renma frontmatter envelopes. Policy-looking Markdown body text remains
  visible instruction evidence and can no longer authorize network, secret,
  upload, approval, or floating-dependency behavior. Strict scans now also fail
  with strict_scan.incomplete_security_analysis when applicable parser-owned
  YAML frontmatter-comment analysis cannot be completed safely.
• Raised SUPPORT-MISSING-PATH from Medium to High because a statically
  referenced local resource that does not exist is a broken declared
  relationship. Missing targets remain structural findings rather than
  inspection-coverage issues.

Fixed

• Made non-Skill Renma metadata consume one shared YAML 1.2 parse before
  catalog, governance, Context Lens, and security interpretation. Quoted,
  block, and flow values now retain YAML semantics consistently, while
  malformed or non-mapping frontmatter and duplicate recognized operational
  keys fail closed with explicit diagnostics instead of selecting raw-line or
  first/last values.
• Routed Markdown link, image, autolink, and resolved reference destinations
  through parser-owned evidence for security analysis and Skill-local support
  reachability. Reference definitions remain non-operational by themselves,
  visible labels and resolved targets remain additive when distinct, and
  overlapping destination candidates preserve the governing instruction.
• Closed frontmatter security-boundary gaps by accounting for parser-hidden
  YAML comments in exact non-Skill envelopes, rejecting reviewed invisible or
  default-ignorable corruption of registered policy keys and delimiters without
  recovering their values, and treating exactly one absolute leading U+FEFF
  as an encoding BOM while additional or embedded corruption remains
  fail-closed.
• Preserved safe Skill-local support file identity across exact exclusion so a
  unique basename-only static reference still produces blocking excluded
  inspection evidence. Excluded files continue to count during basename
  disambiguation, while their contents remain unread and unparsed. When an
  excluded support directory makes a basename candidate set incomplete, Renma
  now emits blocking subtree evidence without traversing the directory or
  inventing an exact child path. Symlink targets remain unfollowed and
  uninspectable even when their path identity supplies blocking evidence.

Removed

• Removed every renma/dist/... package export and the semantic command,
  renderer, guidance, and migration exports. The intentional v1 library API is
  now the focused renma/types surface plus renma/discovery; removed paths
  fail with ERR_PACKAGE_PATH_NOT_EXPORTED, while the renma CLI remains
  available through the package binary.
• Removed operational compatibility for the context/** root, historical
  skill.md and *.skill.md entrypoints, .renma.json, Context Lens
  target/targets/output/outputs, and canonical_context. Explicit
  pre-0.16 and historical-entrypoint migration through suggest-metadata
  remains one-way.

Upgrade

npm install
npm run build
npm test

If using the published package:

npm install -g renma@0.33.0

Validation

Validated with:

npm test
npm run build
node dist/index.js scan . --fail-on high
node dist/index.js catalog . --format markdown
node dist/index.js readiness . --format markdown
node dist/index.js graph . --focus skill.release-prep --format mermaid
node dist/index.js diff . --from v0.32.1 --to HEAD --format markdown
node dist/index.js ci-report . --from v0.32.1 --to HEAD --format markdown

Summary

v0.33.0 includes 15 changelog entries across added, changed, fixed, and removed.