Bug: New fields don’t automatically update completeness scoring UI

[afogel]

Problem:

When new fields are added to the AIBOM schema, the results UI doesn’t automatically reflect the updated scoring/point totals. This creates a
mismatch between backend scoring logic and what the UI displays.

Impact:

• Users see stale or misleading point totals and category breakdowns.
• Requires manual template updates for each schema change.

Repro:

1. Add a new field to any completeness category.
2. Generate a report.
3. Observe that the displayed max points / category descriptions do not reflect the new field.

Expected:

• UI derives category max points and descriptions from the same source of truth used to compute the completeness score.
• Adding fields updates totals and labels automatically.

Proposed fix:

• Ensure completeness_score.category_details.*.max_points (and field counts) are used everywhere in the template instead of hard-coded values.
• Consider moving category labels/weights into the scoring payload or a shared config to avoid drift.

Acceptance criteria:

• Adding/removing a field updates displayed totals without template changes.
• Category scoring summary matches computed results across all categories.
• No hard-coded point totals remain in the results template.