You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Complete Program-aware Submission reports for HAP and CAP #559
A Member or committee reviewer can read all the applicable information captured in a HAP or CAP Submission. Today the report uses fish labels such as “Spawn Date” and “# of Fry” for all Programs and omits propagation, lighting, CO₂ and supplements.
Acceptance criteria
Inventory the fields accepted by the BAP/HAP/CAP forms and explicitly map each applicable field to the report; use Program-appropriate labels for reproduction, counts, feeding and propagation.
Display propagation method, lighting, CO₂ details, and normalized supplement type/regimen rows where applicable. Distinguish an unset value from a meaningful zero or false value; handle older incomplete reports.
Load supplements with the report through the existing data boundary; avoid a second copy of Program applicability rules in the template.
Preserve visibility rules, lifecycle actions and owner-only pending points; this change does not alter scoring or Witness state.
Verify representative BAP, HAP and CAP reports, empty/legacy fields, multiple supplements and long notes. Check narrow-screen rendering on public staging with chikin-farm.
Blocked by
None. Can ship independently of the approved editor enhancement #158.
Evidence
Source review at d162221: the report template renders fish-centric labels and lacks fields already captured by the forms. This is a read/display gap, not a request to change Program rules.
Activity
Show the full, Program-aware report for HAP and CAP Submissions (#559)
Show the full, Program-aware report for HAP and CAP Submissions (#559) (