v0.3.0

[sachin-panayil]

v0.3.0

Problem

mergeWith previously used a shallow spread ({ ...baseline, ...existing, ...observed, ...derived }), which caused nested objects to be replaced wholesale. For example, an observed permissions.usageType could overwrite a manually set permissions.licenses. Observed values also always replaced manual edits, so fields like name were lost on subsequent runs (DSACMS/automated-codejson-generator#31). In addition, observed fields not defined by the active profile, such as repositoryHost on neutral, could leak into the output.

Solution

This release replaces the shallow merge with policy-based recursive merging. mergeWith now filters observed data through filterValidFields, dropping unknown fields, and a new mergeValue function applies rules based on each field's dotted path. Observed values take precedence for fields such as repositoryURL, repositoryVisibility, laborHours, reuseFrequency.forks, and repository dates. tags and reusedCode are unioned, with reused-code entries deduplicated case-insensitively by URL or name. For all other fields, existing manual values are preserved and detected values only fill fields considered unset (undefined, null, or equal to the baseline default).

Result

Manual edits now survive repeated runs at any nesting depth. Fields such as name and description retain manual values unless blank, while tags and dependencies are unioned instead of replaced. Deleted detected tags or dependencies are restored on the next run, and baseline values such as maturityModelTier: 0 are treated as unset so detection can update them.

Test Plan

Testing includes bun install && bun test && bun run typecheck && bun run lint && bun run build, with 73 tests passing.

[natalialuzuriaga]

LGTM! Amazing work on this