Current campaign
PT-001Caregiver 1.2.19 · build v8aWarren / Nadeem · 11 findings · 1.2.21 response ready
1Extracted bug reportWhat the tester found
Contribution evidenceThe work behind PT-001.
Each capture connects this tester’s fieldwork to the findings below.
Name accepts arbitrary symbols
Identity input saves malformed text without format or length controls.
Primary-contact input is unclear and unvalidated
The field accepts malformed text and does not explain whether it expects a name, phone number, or both.
Impossible age is accepted
Age 999 saves without warning or a realistic range check.
Stored-script safety needs complete retesting
A synthetic script payload still needs verification across every display and export surface.
Dashboard tiles may remain at zero
A controlled add-person retest is needed to distinguish refresh behavior from incorrect counting.
Age displays as a corrupted overflow value
The patient view showed 3268586758386868600000 years after extreme input.
Unset weight displays as 0 kg
Missing information is presented as an entered clinical value.
Injury time displays as raw ISO text
The timestamp is inconsistent with the nearby formatted admission time.
All four vital fields accept impossible values
Heart rate, systolic BP, SpO2, and temperature save values far outside valid ranges.
Family Lookup defaults to visible
A new record becomes visible to family search without an explicit tester choice.
Free-text fields accept unbounded garbage strings
The data-quality and safe-output pattern extends across condition, dietary, and general notes.
2Build responseWhat changes and what must pass
Response buildHALT Caregiver 1.2.21Signed · immutable · ready for Warren / Nadeem to verify
Download response build
Safe, realistic identity input
Names are required, capped at 200 characters, and reject control characters. Unicode, apostrophes, and hyphens remain valid by design; output encoding handles unsafe markup.
Contact purpose is explicit
The field now says “name or phone,” includes an example, and applies a 500-character/control-character boundary while remaining optional.
Impossible ages stop before save
Caregiver accepts whole-year ages from 0–130 only, with the same range enforced again by the shared core.
The real stored-script sinks are closed
React already rendered normal screens as text. The patient and shift-handoff HTML exports were the exposed paths; patient-controlled values are now encoded and covered by a script-payload regression test.
Understanding gap—not a confirmed count defect
Returning to Care Home reloads the count immediately; a Home view left open polls every 15 seconds. Retest add → Care Home before changing that path.
Unbounded age pass-through is blocked
This was not an integer overflow: the extreme number was stored and displayed as entered. UI and core boundaries now reject it.
Missing weight reads as missing
An unset weight now displays as an em dash instead of “0 kg,” and the editor accepts only blank or 0.1–1000 kg.
Injury time matches admission time
Both timestamps now use the same guarded local date-and-time formatter; invalid legacy text remains visible instead of crashing the panel.
Vitals have field-specific safety boundaries
Caregiver and the shared save boundary reject impossible heart rate, systolic BP, SpO₂, and temperature values. Missing observations no longer become fake normal graph points.
Family Lookup is explicit opt-in
New Caregiver records now start hidden. Visibility changes only when the checkbox is deliberately enabled.
Free text is bounded without breaking languages
Concern, dietary notes, general notes, allergies, and contact text now have appropriate size/control-character limits; exports encode the saved content.
Public-safe summary. Tester identity, screenshots, raw logs, and internal evidence remain in the controlled handoff record.