# Changelog

## Score

- CAI 46 → 53 (+7.1)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 55 → 55 (+0.1)
- Architecture 98 → 98 (+0.0)
- Maturity 45 → 45 (+0.0)
- Readiness 60 → 60 (+0.0)
- Security 38 → 76 (+38.2)
- Performance 60 → 60 (+0.0)

## Resolved (8)

- Ambiguous separation of concerns between field generation and form generation. `generateFields` takes `FormikProps` (which implies a rendered form context) but returns fields, while `generateForm` takes config and returns the form structure. It is unclear if these are meant to be called sequentially or if one replaces the other. The naming suggests `generateForm` might be the high-level entry point, yet it doesn't seem to call `generateFields` internally based on the signature, leading to potential duplication of effort for the consumer.
- Documentation: no installation or build instructions (README.md)
- Documentation: no project overview (README.md)
- High CVE: [GHSA redacted] (yarn.lock)
- High CVE: [GHSA redacted] (yarn.lock)
- High CVE: [GHSA redacted] (yarn.lock)
- Inconsistent handling of Schema types. `getValuesFromSchema` expects `DomainSchema`, while `validate` expects the base `Schema`. This forces consumers to know which specific schema type is required for which operation, even though `DomainSchema` is a wrapper around `Schema`. This creates a fragmented API surface where the same logical entity (the schema definition) is treated differently depending on the domain (Formik vs Validation).
- Medium CVE: [GHSA redacted] (yarn.lock)

## New (6)

- High CVE: [GHSA redacted] (yarn.lock)
- High CVE: [GHSA redacted] (yarn.lock)
- High CVE: [GHSA redacted] (yarn.lock)
- doc comments repeat the names (packages/formik/src/DomainSchemaFormik.tsx)
- doc comments repeat the names (packages/validation/src/index.ts)
- redundant comment (.pnp.js)
