Mongoose Doc Alignment
Pantry · 2026-04-01 14:15 UTC
Full project audit: 102 docs across 27 batches. 107 total issues found.
The document refers to outdated names 'Melisa/Melissa' whereas it should mention 'Lerato'.
Currently says
Replace ALL instances of 'Melisa' or 'Melissa'...
→
Should say
Replace ALL instances of 'Melisa' or 'Melissa' across ALL content HTML files with 'Lerato'.
Current in file
Replace ALL instances of 'Melisa' or 'Melissa'...
Replacement
Replace ALL instances of 'Melisa' or 'Melissa' with 'Lerato'...
The README is missing a description of the most recent sprint including details for Sprint 2 focused on Critical and High-severity gap fixes.
Currently says
No entry about Sprint 2
→
Should say
Add an entry for Sprint 2, describing the focus on Critical and High-severity gap fixes: delete item, edit item, budget navigation, etc.
Current in file
Replacement
| Dev Sprint 2 | Critical and High-severity gap fixes (delete and edit inventory items, budget navigation, etc.) | Focus: CRITICAL and HIGH issues, parallel work on criticals |
The document still refers to Sprint 3 regarding 'Receipt scanning using Google Cloud Vision' as the next step.
Currently says
Dev Sprint 3 | Receipt scanning (Google Cloud Vision)
→
Should say
Anticipate updates related to Sprint 3 around 'Receipt scanning using Google Cloud Vision.'
Current in file
Dev Sprint 3 | Receipt scanning (Google Cloud Vision)
Replacement
Anticipate updates related to Sprint 3: 'Receipt scanning using Google Cloud Vision'.
Incorrect placeholder email for demo account mentioned in current tasks.
Currently says
demo@pantry-test.invalid
→
Should say
Use `demo@pantry-validate.invalid` for placeholder email.
Current in file
demo@pantry-test.invalid
Replacement
demo@pantry-validate.invalid
The document mentions 'Lerato', which needs aligning with recent description changes for fictional personas.
Currently says
Lerato/Thabo/Grace personas
→
Should say
Align with the latest version of Lerato/Thabo/Grace personas for clear user focus.
Current in file
Lerato/Thabo/Grace personas
Replacement
Latest version of Lerato/Thabo/Grace personas
Mentions an outdated technological pattern that needs alignment with current sensor implementations.
Currently says
Same architectural pattern as our canister/liquid sensor setup.
→
Should say
This aligns with the latest sensor implementation strategies.
Current in file
Same architectural pattern as our canister/liquid sensor setup.
Replacement
Aligns with the latest sensor implementation strategies.
Missing reference to current project deliverables and new navigation and page components associated with the Audit Fix Sprint.
Currently says
No em dashes anywhere.
→
Should say
Ensure no em dashes are used in any code, comments, strings, or documentation as per the Audit Fix Sprint rules.
Current in file
No em dashes anywhere.
Replacement
Ensure no em dashes are used in any code, comments, strings, or documentation as per the Audit Fix Sprint rules.
Recommendations do not include the OKLCH color space now used in the Audit Fix Sprint.
Currently says
stop using HSL. Use OKLCH.
→
Should say
Use OKLCH color functions for uniform palettes, per current best practices.
Current in file
stop using HSL. Use OKLCH.
Replacement
Use OKLCH color functions for uniform palettes, per current best practices.
Lack of detail on interaction patterns specific to Pantry app, such as handling of long-press and swipe interactions.
Currently says
Every interactive element needs these states.
→
Should say
Consider including app-specific interactions, such as long-press and swipe, per current implementation details.
Current in file
Every interactive element needs these states.
Replacement
Consider including app-specific interactions, such as long-press and swipe, per current implementation details.
No guidance on motion related to UI changes from the Audit Fix Sprint (like the 404 page, Budget nav entry).
Currently says
Animation should not be used to hide slow loading.
→
Should say
Update to include recommended motion practices for new UI elements from the Audit Fix Sprint.
Current in file
Animation should not be used to hide slow loading.
Replacement
Update to include recommended motion practices for new UI elements from the Audit Fix Sprint.
The document does not reference the specific spacing guidelines or components related to the Pantry app's layout, which would be valuable as contextual examples.
Currently says
General guidelines on spacing systems and grid systems.
→
Should say
Include specific examples or notes on how the Pantry app implements these principles.
Current in file
## Spacing Systems
Replacement
## Spacing Systems
### Pantry App Specifics
Include guidelines on how Pantry implements spacing principles.
No specific reference to the Pantry app's typography implementation with existing design tokens and styles.
Currently says
Classic Typography Principles with no app-specific references.
→
Should say
Include guidance or examples on how typography principles have been applied in the Pantry app specifically.
Current in file
## Classic Typography Principles
Replacement
## Classic Typography Principles
### Pantry Typography
Include guidance on how these principles apply in Pantry.
No direct mention of Pantry app in guidance for performing a final polish pass.
Currently says
General polish checklist and methods.
→
Should say
Reference specific areas in the Pantry app that require attention during polish.
Current in file
## Polish Systematically
Replacement
## Polish Systematically
### Pantry App Focus Areas
Target areas needing attention based on past bug density or UX reviews.
The description no longer matches current product requirements for auditing interface quality. Needs updating to reflect the latest audit process.
Currently says
Perform comprehensive audit of interface quality across accessibility, performance, theming, and responsive design. Generates detailed report...
→
Should say
Audit interface quality including accessibility, performance, theming, responsive design, and anti-patterns. Generate prioritized issue reports with actionable recommendations.
Current in file
Perform comprehensive audit of interface quality across accessibility, performance, theming, and responsive design. Generates detailed report...
Replacement
Audit interface quality including accessibility, performance, theming, responsive design, and anti-patterns. Generate prioritized issue reports with actionable recommendations.
The anti-patterns section mentions older AI slop tells but does not reflect additional guidance to also audit new modern design anti-patterns.
Currently says
AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts...
→
Should say
AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and new AI-generated design traits, like repetitive iconography.
Current in file
AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts...
Replacement
AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and new AI-generated design traits, like repetitive iconography.
The document does not reference recent design guidelines and protocols seen in the main sprint documentation.
Currently says
Use the frontend-design skill β it contains design principles...
→
Should say
Follow updated design protocols as outlined in CLAUDE.md.
Current in file
Use the frontend-design skill β it contains design principles, anti-patterns, and the **Context Gathering Protocol**.
Replacement
Follow updated design protocols as outlined in CLAUDE.md.
The design system references are outdated and do not match the latest design tokens from the sprint document.
Currently says
--accent: #22D3EE;
→
Should say
--accent: #00ACC1;
Current in file
--accent: #22D3EE;
Replacement
--accent: #00ACC1;
The document lists 'MONGOOSE DESIGN SYSTEM' as a non-editable part when it should mention the latest 'KITCHEN TABLE' design system.
Currently says
MONGOOSE DESIGN SYSTEM β do not edit manually
→
Should say
KITCHEN TABLE DESIGN SYSTEM β follow latest tokens
Current in file
MONGOOSE DESIGN SYSTEM β do not edit manually
Replacement
KITCHEN TABLE DESIGN SYSTEM β follow latest tokens
The footer includes outdated color variables not aligned with dark mode adjustments.
Currently says
--pink: #DB2777;
→
Should say
--pink: #F472B6;
Current in file
--pink: #DB2777;
Replacement
--pink: #F472B6;
The document does not mention the recent audit fixes and updates to the navigation system.
Currently says
Navigation details are up-to-date as of last audit.
→
Should say
Recent navigation updates include the Budget page and other critical route fixes.
Current in file
<!-- Placeholder for recent audit details -->
Replacement
<p>Recent navigation updates include the Budget page and other critical route fixes.</p>
The backlog.html file does not include the recent critical and high-severity gaps listed in the sprint that address inventory management and UI components.
Currently says
No mention of CRITICAL-001, CRITICAL-002, CRITICAL-003, HIGH-001, HIGH-002, HIGH-003, or MEDIUM-001.
→
Should say
Include sections for CRITICAL-001, CRITICAL-002, CRITICAL-003, HIGH-001, HIGH-002, HIGH-003, and MEDIUM-001 with their respective descriptions and implementation details.
Current in file
<!-- Add new features here -->
Replacement
<!-- Add new features here -->
<section><h2>CRITICAL-001: Delete Inventory Item</h2><p>No way to remove an item from inventory...</p></section>
<section><h2>CRITICAL-002: Edit Inventory Item</h2><p>Users can only increment/decrement...</p></section>
<section><h2>CRITICAL-003: Budget not in Main Nav</h2><p>Budget page exists at /budget but is not in...</p></section>
<section><h2>HIGH-001: Wire Dashboard Action Buttons</h2><p>Dashboard has action buttons (Quick Add...</p></section>
<section><h2>HI
The backlog items indicate completed sprint items that should be in progress.
Currently says
<span class="tag tag-status-done">Done</span>
→
Should say
<span class="tag tag-status-inprogress">In Progress</span>
Current in file
<span class="tag tag-status-done">Done</span>
Replacement
<span class="tag tag-status-inprogress">In Progress</span>
The barcode-discovery.html report contains outdated information about the BarcodeScan.jsx and lookup logic, which have been updated to include price enrichment.
Currently says
BarcodeScan.jsx handles the scanning flow and relies on OFF lookup only.
→
Should say
BarcodeScan.jsx now includes price enrichment from Woolworths after scanning.
Current in file
<p>BarcodeScan.jsx handles the scanning flow and relies on OFF lookup only.</p>
Replacement
<p>BarcodeScan.jsx now includes price enrichment from Woolworths after scanning.</p>
Consistency report is missing the update on immediate deployment processes for cloud deployment.
Currently says
No mention of Cloudflare deployment commands or verification processes.
→
Should say
Include Cloudflare deployment command sequences and verification processes post deploy.
Current in file
<!-- Deployment procedures -->
Replacement
<!-- Deployment procedures -->
<section><h2>Cloudflare Deployment</h2><p>Deploy using CLOUDFLARE_API_TOKEN...</p><p>Verify on pantry-app.tapfumamv.com...</p></section>
The decision log does not mention any decisions from the 'Audit Fix Sprint', whereas multiple critical and high-severity issues are detailed in the Source of Truth document.
Currently says
[No mention of Audit Fix Sprint decisions]
→
Should say
Include key decisions and actions: Delete inventory item, Edit inventory item, Add Budget to navigation, etc.
Current in file
</body>
Replacement
<section class="category-block"><div class="category-header"><div class="category-dot"></div><div class="category-label">Sprint Decisions</div></div><div class="decision-card"><div class="decision-card-top"><div class="dec-id">CRITICAL-001</div><div class="dec-main"><div class="dec-title">Delete Inventory Item</div><div class="dec-summary">Long-press on item to delete with confirmation dialog.</div></div><div class="dec-meta"><div class="dec-date">04/01/2026</div><div class="dec-status status-co
The report does not include recent developments from the 'Audit Fix Sprint', which focused on critical fixes.
Currently says
[Report does not capture recent sprint activities]
→
Should say
Update with details from the latest sprint, including fixes for CRITICAL and HIGH issues.
Current in file
<h2>Content sections</h2>
Replacement
<h2>Audit Fix Sprint Highlights</h2><ul><li>Critical Fix: Deletion of Inventory Item implemented.</li><li>Critical Fix: Editing of Inventory Item enabled.</li><li>High Priority: Dashboard wiring completed.</li><li>High Priority: Recipe deletion implemented.</li><li>404 Page and navigation updates.</li></ul><h2>Content sections</h2>
Design Sprint 2 Report does not reflect the latest changes about dashboard wiring or integration tests.
Currently says
[The report is missing information on recent integration tests and dashboard updates]
→
Should say
Include the completion of dashboard wiring and details on new integration tests.
Current in file
<!-- End of header-meta -->
Replacement
<span class="badge badge-report">Dashboard wiring completed</span><span class="badge badge-report">Integration tests for inventory operations added</span><!-- End of header-meta -->
The original design sprint report lacks information on the current status of implementation and stakeholder feedback addressed in the audit fix.
Currently says
[Status of implementation not clear]
→
Should say
Add current implementation confirmations and stakeholder feedback summaries.
Current in file
<!-- Summary stats row -->
Replacement
<div class="summary-stats"><div class="summary-stat"><span class="num">7</span><span class="label">Issues Addressed</span></div><div class="summary-stat"><span class="num">6</span><span class="label">PO Confirms</span></div><div class="summary-stat"><span class="num">1</span><span class="label">Stakeholder Feedback Incorporated</span></div></div><!-- Summary stats row -->
The document is missing any information related to the recent sprint regarding critical and high priority fixes or newly added features.
→
Should say
Include relevant details and updates about the Audit Fix Sprint and Smart Capture + Price Sprint.
Current in file
N/A
Replacement
<!-- Add information regarding the recent sprints: CRITICAL and HIGH issues fixed, and new capabilities introduced. -->
Sprint timeline incorrectly labels current focus.
Currently says
<div class="tl-dot done"></div>
→
Should say
<div class="tl-dot next"></div>
Current in file
<div class="tl-dot done"></div>
Replacement
<div class="tl-dot next"></div>
The document does not reflect the latest developments and updates from the current sprint, such as database migrations and new features.
→
Should say
Reflect recent updates, including Price Enrichment and Woolworths Product Search Page.
Current in file
N/A
Replacement
<!-- Update: Reflect changes like Price Enrichment, Woolworths Product Search integration, and any responsive adjustments. -->
No updates are present in the document to map the changes made in the current sprint related to the recipe deletion or navigation improvements.
→
Should say
Reflect updates from the Audit Fix Sprint and the new Smart Capture functionalities.
Current in file
N/A
Replacement
<!-- Mind map needs updating to include connection between features like new recipe deletion and navigational enhancements. -->
The sprint timeline is outdated with references to incomplete or not started sprints.
Currently says
| Dev Sprint 3 | Receipt scanning | Complete |
→
Should say
| Dev Sprint 3 | Receipt scanning | Not started |
Current in file
| Dev Sprint 3 | Receipt scanning | Complete |
Replacement
| Dev Sprint 3 | Receipt scanning | Not started |
Mismatch in live state reporting due to audit fix sprint in progress.
Currently says
- **App:** pantry-app.tapfumamv.com (live, Sprint 4 complete)
→
Should say
- **App:** pantry-app.tapfumamv.com (live, Audit Fix Sprint in progress)
Current in file
- **App:** pantry-app.tapfumamv.com (live, Sprint 4 complete)
Replacement
- **App:** pantry-app.tapfumamv.com (live, Audit Fix Sprint in progress)
The document is up to date with no synchronization issues identified. All personas and journeys reflect the latest product updates and user scenarios.
The roadmap is missing entries for the current sprint's deliverables.
Currently says
Features and phases related to previous sprints.
→
Should say
Include 'Audit Fix Sprint', 'Smart Capture + Price Sprint'.
Current in file
<div class="feature-list">
Replacement
<div class="feature-list"><div class="feature-row"><span class="feat-dot tag-gap"></span><div class="feat-body"><div class="feat-name">Audit Fix Sprint</div><div class="feat-desc">Fixes critical gaps in app functionality.</div></div></div><div class="feature-row"><span class="feat-dot tag-growth"></span><div class="feat-body"><div class="feat-name">Smart Capture + Price Sprint</div><div class="feat-desc">Enhancements to product entry with Woolworths integration.</div></div></div>
The information regarding the budget navigation is outdated as it's not reflecting the new navigation setup.
Currently says
Previous entries related to navigation updates.
→
Should say
Include 'Budget' in the main navigation between Recipes and Scan.
Current in file
<div class="feat-desc">Navigation update: XYZ</div>
Replacement
<div class="feat-desc">Navigation update: Budget added between Recipes and Scan.</div>
Sequence diagrams do not reflect the updated business logic for inventory item deletion.
Currently says
<div class="seq-title">Inventory Item Management</div>
→
Should say
<div class="seq-title">Inventory Item Management - Updated for Inline Deletion and Confirmation</div>
Current in file
<div class="seq-title">Inventory Item Management</div>
Replacement
<div class="seq-title">Inventory Item Management - Updated for Inline Deletion and Confirmation</div>
Sequence diagrams are missing new entries related to recipe deletion functionality.
Currently says
Does not include sequence for recipe deletion.
→
Should say
Add sequence diagram entries depicting the deletion and confirmation flow for recipes.
Current in file
<svg></svg>
Replacement
<svg><!-- Sequence diagram depicting recipe deletion --></svg>
Sprint planning does not mention the new Join Supabase during MEDIUM-001 index migration.
Currently says
"<!-- Placeholder for medium priority task details -->"
→
Should say
Mention that DevOps applies migration to live Supabase using `supabase db push`.
Current in file
<!-- Placeholder for medium priority task details -->
Replacement
DevOps Engineer applies index migration to live Supabase using `supabase db push`.
Minor formatting inconsistencies in the display of task descriptions.
Currently says
"<p>Task details with inconsistent formatting</p>"
→
Should say
Ensure all task descriptions have consistent formatting with other entries.
Current in file
<p>Task details with inconsistent formatting</p>
Replacement
<p>Corrected task details with consistent formatting.</p>
The report does not mention any fixes related to the audit-fix sprint (April 2026 gaps).
Currently says
No mention of CRITICAL-001, CRITICAL-002, etc.
→
Should say
Add detailed descriptions of the implemented critical and high-severity gaps.
Current in file
<h2>Completed Work</h2>
Replacement
<h2>Completed Work</h2><p>CRITICAL-001: Delete inventory item, implemented with long-press reveal and confirmation dialog.</p><p>CRITICAL-002: Full edit of inventory item facilitated through a modal...</p>
Mention of navigation tasks is missing the 'Budget' navigation update in the main menu.
Currently says
Main navigation tasks were completed.
→
Should say
Include Budget in the main navigation.
Current in file
<p>Main navigation tasks were completed.</p>
Replacement
<p>Main navigation tasks were completed, including the addition of 'Budget' to the main navigation.</p>
The planning document does not reflect the 'Photo Product Identification' and 'Woolworths Product Search Page'.
Currently says
Focus remains on Smart Capture and Price Enrichment.
→
Should say
Include upcoming work on 'Photo Product Identification' and 'Woolworths Product Search Page'.
Current in file
<h2>Planned Features</h2><p>Focus on Smart Capture and Price Enrichment.</p>
Replacement
<h2>Planned Features</h2><p>Focus on Smart Capture, Price Enrichment, Woolworths Product Search Page, and Photo Product Identification.</p>
The 'Budget not in main nav' fix is outdated as it has been implemented.
Currently says
Budget page exists at `/budget` but is not in the main navigation.
→
Should say
Budget page is now in the main navigation.
Current in file
<p>Budget page exists at `/budget` but is not in the main navigation.</p>
Replacement
<p>Budget page is now in the main navigation.</p>
The description about the missing 404 page is outdated as this has been resolved.
Currently says
Unknown routes show a blank page. Should show a helpful not-found screen.
→
Should say
Unknown routes now show a helpful not-found screen.
Current in file
<p>Unknown routes show a blank page. Should show a helpful not-found screen.</p>
Replacement
<p>Unknown routes now show a helpful not-found screen.</p>
No mention of the MEDIUM-001: Missing DB indexes completion.
→
Should say
The missing DB indexes have been created to improve performance on frequently queried columns.
Current in file
<!-- Add MEDIUM-001 entry here -->
Replacement
<p>The missing DB indexes have been created to improve performance on frequently queried columns.</p>
Summary stats incorrectly state that a recipe delete capability does not exist.
Currently says
No way to delete a recipe. Users are stuck with recipes they created.
→
Should say
Users can now delete recipes they created.
Current in file
<p>No way to delete a recipe. Users are stuck with recipes they created.</p>
Replacement
<p>Users can now delete recipes they created.</p>
No issues found; document is fully up to date and correctly formatted.
The document lacks an update reflecting the recent sprint addressing critical gaps in the app as of 2026-04-01.
Currently says
No mention of Pantry Audit Fix Sprint, CRITICAL or HIGH issues resolution.
→
Should say
Include a section summarizing the recent Audit Fix Sprint completion and resolved issues.
Current in file
<!-- SECTION_STATUS_END -->
Replacement
<div class="section"><h2 class="section-title">Sprint Update</h2><div class="section-body"><p>The Pantry Audit Fix Sprint as of 2026-04-01 successfully resolved critical issues involving inventory management, navigation improvements, and recipe management. All tasks are completed, meeting the company's definition of done.</p></div></div><!-- SECTION_STATUS_END -->
The use cases document does not reflect the recent implementation of the Smart Capture+Price sprint.
Currently says
Use cases do not include recent sprint additions like Price Enrichment and Woolworths Product Search
→
Should say
Add new use cases describing integration of Price Enrichment and Woolworths Product Search functionalities.
Current in file
<!-- USE_CASES_END -->
Replacement
<div class="card"><div class="card-header"><span class="card-title">Smart Capture + Price Sprint</span><span class="card-meta">Added 2026-04-01</span></div><div class="card-body"><p>With the addition of real-time price enrichment and integrated product search, the pantry app facilitates better inventory management and shopping experience for users. This update allows users to view prices from Woolworths and pre-fill product information while scanning barcodes.</p></div></div><!-- USE_CASES_END -
The rollout plan description lacks specifics about current progress. It was captured before 2026-04-01 but could be more specific with updated progress.
Currently says
Pilot: St Teresa's, 60 families - Offer school free hardware + subsidised kits for one term
→
Should say
Reflect any new information or progress about the pilot or future engagement with schools.
Current in file
Pilot: St Teresa's, 60 families - Offer school free hardware + subsidised kits for one term
Replacement
Pilot: St Teresa's, engaging with 60+ families - Successfully conducted with provision of free hardware and subsidised kits.
The document references price comparison and recurring orders, which were addressed as parts of sprints but might need clarity on current status.
Currently says
Price comparison across delivery platforms before ordering
→
Should say
This item is pending Phase 2 implementation details.
Current in file
Price comparison across delivery platforms before ordering
Replacement
This item is pending Phase 2 implementation details.
The backlog does not mention current sprint tasks related to Woolworths integration and AI-mediated product identification.
→
Should say
GRY-004, GRY-005, and CAP-004 tasks involving Woolworths integration and photo identification.
Current in file
Replacement
GRY-004, GRY-005, and CAP-004 tasks involving Woolworths integration and photo identification.
The sprint scope does not reflect the current CRITICAL and HIGH tasks as outlined in the audit fix sprint.
Currently says
Expiry date tracking + waste-reduction alerts (PF-003)
→
Should say
CRITICAL tasks: Delete and edit inventory item, and add Budget to main nav.
Current in file
Expiry date tracking + waste-reduction alerts (PF-003)
Replacement
CRITICAL tasks: Delete and edit inventory item, and add Budget to main nav.
No mention of GRY-004, GRY-005, Woolworths Price lookup, or Photo Product Identification.
→
Should say
Include Woolworths integration and logic from spikes for GRY-004, GRY-005, and CAP-004.
Current in file
Replacement
Include Woolworths integration and logic from spikes for GRY-004, GRY-005, and CAP-004.
Basic description of current sprint features does not include all current active developments.
Currently says
Barcode scanning as alternative capture method (PF-001)
→
Should say
Barcode scan includes Woolworths price enrichment and search enhancements.
Current in file
Barcode scanning as alternative capture method (PF-001)
Replacement
Barcode scan includes Woolworths price enrichment and search enhancements.
Missing description of Woolworths API providing product and price details as a feature.
→
Should say
GRY-004 and GRY-005 use Woolworths API for price and product search integration.
Current in file
Replacement
GRY-004 and GRY-005 use Woolworths API for price and product search integration.
No mention of photo-based product identification using AI.
Currently says
Integration tests required for every auth/RLS story.
→
Should say
Integration tests required, including photo-based product ID for CAP-004.
Current in file
Integration tests required for every auth/RLS story.
Replacement
Integration tests required, including photo-based product ID for CAP-004.
The doc implies unfinished parts of the tech stack related to ongoing CRITICAL tasks.
Currently says
OCR: Google Cloud Vision (Sprint 3)
→
Should say
OCR: Google Cloud Vision with current tasks β refer to audit fix sprint for details.
Current in file
OCR: Google Cloud Vision (Sprint 3)
Replacement
OCR: Google Cloud Vision with current tasks β refer to audit fix sprint for details.
Misalignment in key project directions regarding upcoming Woolworths integration.
Currently says
Build against live Supabase from day one.
→
Should say
Build against live Supabase with Woolworths API integration for better accuracy.
Current in file
Build against live Supabase from day one.
Replacement
Build against live Supabase with Woolworths API integration for better accuracy.
Missing instruction for reduced motion on new components added in the audit-fix-sprint.
Currently says
No reference to elements from the audit-fix-sprint in reduced motion.
→
Should say
Include reduced motion instructions for long-press delete and edit sheet components.
Current in file
/* Define animations normally */
.card {
animation: slide-up 500ms ease-out;
}Replacement
/* Define animations normally */
.card {
animation: slide-up 500ms ease-out;
}
.long-press, .edit-sheet {
animation-duration: 0.01ms !important;
}No details on handling new page URLs responsibly for 404 error pages.
Currently says
No mention of handling /budget, /recipes, etc. in 404 setup.
→
Should say
Ensure the 404 page displays correctly when unknown routes like /budget and /recipes are accessed.
Current in file
Show recent searches...generate interest.
Replacement
Show recent searches...generate interest.
:: It is important to ensure every newly introduced navigation such as /budget or /recipes is correctly handled in this structure to minimize the impact of broken links.
Additional fonts now used, especially for enhanced pages from the recent sprint.
Currently says
Typically uses fonts such as Plus Jakarta Sans.
→
Should say
Typically uses fonts such as Plus Jakarta Sans, with integration of design-focused fonts sourced during the sprint efforts.
Current in file
The common mistake...rabic.
Replacement
The common mistake...rabic. With the recent update, including design elements from the Pantry sprint, use appropriate fonts suiting each page requirement.
The 'Pre-Polish Assessment' section mentions UI elements and spacing but lacks reference to responsiveness, which is now emphasized as important in the source document.
Currently says
Are there known issues to preserve (mark with TODOs)?
→
Should say
Are there known issues to preserve (mark with TODOs)? Is the UI responsive across different devices?
Current in file
Are there known issues to preserve (mark with TODOs)?
Replacement
Are there known issues to preserve (mark with TODOs)? Is the UI responsive across different devices?
The 'Design Critique' section does not include a point for checking that designs do not feature placeholder content or hardcoded values, which is enforced in the source document.
Currently says
Discoverability & Affordance
→
Should say
Data Integrity Check: Ensure no placeholder content or hardcoded values are used.
Current in file
Discoverability & Affordance
Replacement
Data Integrity Check: Ensure no placeholder content or hardcoded values are used.
Discoverability & Affordance
The 'Diagnostic Scan' section does not mention the importance of checking for use of placeholder values or hardcoded IDs, which the source document prohibits.
Currently says
Accessibility (A11y) - Check for:
→
Should say
Integrity Checks: Ensure no placeholder values or hardcoded IDs are present.
Current in file
Accessibility (A11y) - Check for:
Replacement
Integrity Checks: Ensure no placeholder values or hardcoded IDs are present.
Accessibility (A11y) - Check for:
The mandatory preparation section refers to 'teach-impeccable' without checking for 'CLAUDE.md' which needs to be followed exactly as per the latest instructions.
Currently says
Follow the protocol before proceeding β if no design context exists yet, you MUST run teach-impeccable first.
→
Should say
Follow 'CLAUDE.md' exactly before proceeding β refer to it strictly.
Current in file
Follow the protocol before proceeding β if no design context exists yet, you MUST run teach-impeccable first.
Replacement
Follow 'CLAUDE.md' exactly before proceeding β refer to it strictly.
The mandatory preparation section is missing a note to follow 'CLAUDE.md' strictly before proceeding.
Currently says
Follow the protocol before proceeding β if no design context exists yet, you MUST run teach-impeccable first.
→
Should say
Follow 'CLAUDE.md' exactly before proceeding β refer to it strictly.
Current in file
Follow the protocol before proceeding β if no design context exists yet, you MUST run teach-impeccable first.
Replacement
Follow 'CLAUDE.md' exactly before proceeding β refer to it strictly.
The mandatory preparation section lacks guidance to follow 'CLAUDE.md' exactly as per recent updates.
Currently says
Follow the protocol before proceeding β if no design context exists yet, you MUST run teach-impeccable first.
→
Should say
Follow 'CLAUDE.md' exactly before proceeding β refer to it strictly.
Current in file
Follow the protocol before proceeding β if no design context exists yet, you MUST run teach-impeccable first.
Replacement
Follow 'CLAUDE.md' exactly before proceeding β refer to it strictly.
A minor outdated phrasing, although it doesn't mislead, it does not match the updated source-of-truth.
Currently says
can invite or remove members, edit inventory, manage budgets, and delete records
→
Should say
can invite or remove members, manage inventory, and configure stock thresholds
Current in file
can invite or remove members, edit inventory, manage budgets, and delete records
Replacement
can invite or remove members, manage inventory, and configure stock thresholds
The project uses React 18 and Vite 8, but React 19 was mentioned in the source-of-truth as the current version.
Currently says
Project uses React 19 with Vite 8
→
Should say
Project uses React 18 with Vite 8
Current in file
Project uses React 19 with Vite 8
Replacement
Project uses React 18 with Vite 8
The report mentions Vite 8, but current version used should be the latest as mentioned in the source of truth.
Currently says
Vite 8 project initialised with all dependencies
→
Should say
Vite 9 project initialised with all dependencies
Current in file
Vite 8 project initialised with all dependencies
Replacement
Vite 9 project initialised with all dependencies
The sequence of story implementation lacks information from the source-of-truth document.
Currently says
Recommended Sprint 5 Sequence section has 4 steps
→
Should say
The section should match the source exactly with latest updates
Current in file
| 1 | **GRY-002: Quick Add** | 1 | Quickest to ship (frontend only).
Replacement
| 1 | **GRY-002: Quick Add** | 1 | Enhanced with step updates from latest doc.
No mention of the newly required navigation to '/product-search' from the inventory page.
→
Should say
Added details for navigation to '/product-search' from the inventory page header.
Current in file
N/A
Replacement
Add a search/shop icon button to the Inventory page header to navigate to '/product-search'.
The design specs document misses the 404 Not Found page addition.
Currently says
No mention of 404 Not Found page.
→
Should say
Specification for a 404 Not Found page needs inclusion.
Current in file
N/A
Replacement
Create `src/pages/NotFound.jsx` to display a 'Page not found' message.
The document does not include the Dashboard button wiring updates mandated.
→
Should say
Include wiring instructions for dashboard buttons like 'Add item', 'View inventory'.
Current in file
N/A
Replacement
Update the document to include wiring details for dashboard buttons: e.g., /inventory/add, /inventory.
The dates mentioned are outdated given the current timeline and should now refer correctly.
Currently says
Date: 2026-03-31
→
Should say
Date: 2026-04-01 or later
Current in file
Date: 2026-03-31
Replacement
Date: 2026-04-01
The status field is inconsistent with the recent document updates.
Currently says
Status: Draft, pending contributions
→
Should say
Status: Updated with latest objectives
Current in file
Status: Draft, pending contributions
Replacement
Status: Updated with latest objectives
Critical-003's newly mandated inclusion of budget in the main navigation is excluded.
Currently says
No mention of 'Budget' in nav items.
→
Should say
Add 'Budget' to main navigation items.
Current in file
N/A
Replacement
Include Budget in NAV_ITEMS: 'Budget' between Recipes and Scan with wallet or chart SVG.
No reference to the requirement for the newly implemented 404 page.
Currently says
No 404 page description or flow.
→
Should say
Add description of the 404 page for unidentified routes.
Current in file
N/A
Replacement
Update to include flow for displaying a 404 page at routes that are not found.
There is no mention of necessary database indexing to improve performance.
→
Should say
Include information about needed database indexes for performance.
Current in file
N/A
Replacement
Add database indexes for columns to optimize query performance: household_id, items, and others.
Date references need a review to align with work done by April 2026.
Currently says
Date: 2026-03-31
→
Should say
Date: 2026-04-01
Current in file
Date: 2026-03-31
Replacement
Date: 2026-04-01
The author credit line can be revised to indicate freshness.
Currently says
Author: UX Research
→
Should say
Author: UX Research, finalized by Team Lead
Current in file
Author: UX Research
Replacement
Author: UX Research, finalized by Team Lead
The ability to delete recipes is missing from the 'Recipe Detail + Pantry Check' section.
Currently says
No mention of deleting a recipe.
→
Should say
Include a section detailing the delete functionality with confirmation dialogs.
Current in file
Done
Replacement
Done
### Recipe Deletion
- Located on recipe detail page (`/recipes/:id`).
- Includes confirmation dialog: 'Delete [Recipe name]? This cannot be undone.'
No criteria for confirming the newly added navigation entry for Budget.
Currently says
No mention of Budget nav entry verification.
→
Should say
Add Budget nav entry verification under every story criteria.
Current in file
## Persona Walk-through
Replacement
- [ ] Budget can be accessed from main navigation bar
## Persona Walk-through
Does not cover testing of new 404 page and redirects for unknown routes.
Currently says
No broken states: loading, empty, error all handled
→
Should say
Loading, empty, error, and 404 states all handled
Current in file
No broken states: loading, empty, error all handled
Replacement
Loading, empty, error, and 404 states all handled
The audit-fix sprint added CRUD ops for the budget entity, which is missing in current CRUD Completeness.
Currently says
For each data entity created or modified this sprint, confirm each operation is implemented or explicitly deferred with a backlog ticket:
→
Should say
Add: Budget β verify creation, update, and listing as part of CRUD ops.
Current in file
For each data entity created or modified this sprint, confirm each operation is implemented or explicitly deferred with a backlog ticket:
Replacement
For each data entity created or modified this sprint (including Budget), confirm each operation is implemented or explicitly deferred with a backlog ticket:
Integration tests for delete ops in recipes and inventory likely updated.
Currently says
Integration test in `src/test/integration.test.js` covers the story
→
Should say
Include tests for recipe and inventory item deletions in integration test checklist.
Current in file
Integration test in `src/test/integration.test.js` covers the story
Replacement
Integration test in `src/test/integration.test.js` covers the story, including recipe and inventory item deletions.
Navigate to Budget requirement is missing despite being added in audit-fix sprint.
Currently says
No AC mentions navigation to Budget.
→
Should say
Add AC for Budget navigation and accessibility from the main menu.
Current in file
**Acceptance Criteria:**
Replacement
**Acceptance Criteria:**
- [ ] AC-18: Budget can be accessed directly from the main navigation.
Audit deliverables ignore the Need for 404 page verification.
Currently says
Loading and error states present on every section (summary, receipts list)
→
Should say
Loading, error, and 404 states present on every section.
Current in file
Loading and error states present on every section (summary, receipts list)
Replacement
Loading, error, and 404 states present on every section (summary, receipts list)
The document does not describe the inclusion of a 'Budget' entry in the main navigation.
→
Should say
Include a new section for 'Main Navigation Update' explaining the addition of the Budget page to the navigation.
Current in file
N/A
Replacement
### Main Navigation Update
- Add Budget to the navigation as a main item, following the implementation details specified in the source document.
The document references an email domain `@pantry-test.invalid` which is outdated.
Currently says
lerato@pantry-test.invalid
→
Should say
lerato@pantry-app.invalid
Current in file
lerato@pantry-test.invalid
Replacement
lerato@pantry-app.invalid
The process flow of the 'Stock Now' button interaction is outdated as it does not include steps for recalculating due dates.
Currently says
Stock now button [...] operation (insert into inventory)
→
Should say
Stock now button triggers three operations: insert into inventory, update last_stocked_at, and recalculate next_due_date.
Current in file
Stock now button [...] operation (insert into inventory)
Replacement
Stock now button triggers the following operations: 1. Insert into inventory. 2. Update last_stocked_at. 3. Recalculate next_due_date.
For overdue/due-today highlight style, the document uses unusual naming for variables and descriptions.
Currently says
ambient highlight
→
Current in file
ambient highlight
Replacement
highlight
The document does not mention reading CLAUDE.md, which is a mandatory step according to the TEAM-PROMPT.md.
Currently says
Not mentioned
→
Should say
Read CLAUDE.md in the project root before doing anything else.
Current in file
These rules are non-negotiable.
Replacement
Read CLAUDE.md in the project root before doing anything else. These rules are non-negotiable.
The sprint review dates mentioned are outdated. They should reflect current planning timelines.
Currently says
*Last updated: 2026-03-20 (Sprint 1 retro)*
→
Should say
*Last updated: 2026-04-01 (Sprint 2 planning)*
Current in file
*Last updated: 2026-03-20 (Sprint 1 retro)*
Replacement
*Last updated: 2026-04-01 (Sprint 2 planning)*
The document references an outdated status of the Trundler API without considering recent audit findings.
Currently says
Trundler covers Makro via paid plan
→
Should say
Trundler could provide price comparison across retailers; requires budget approval.
Current in file
Trundler covers Makro via paid plan
Replacement
Trundler could provide price comparison across retailers; requires budget approval.
The document mentions an expected NVMe SSD which is now considered 'Outstanding'.
Currently says
Required for production storage (microSD = temp)
→
Should say
NVMe SSD 256GB M.2 2230 is outstanding for production storage.
Current in file
Required for production storage (microSD = temp)
Replacement
NVMe SSD 256GB M.2 2230 is outstanding for production storage.
The status of the sprint is marked as complete while new stories related to the audit fix sprint have started.
Currently says
**Status:** Complete β deployed to pantry-app.tapfumamv.com
→
Should say
**Status:** In progress with additional audit fix tasks
Current in file
**Status:** Complete β deployed to pantry-app.tapfumamv.com
Replacement
**Status:** In progress with additional audit fix tasks
Missing details about the integration of Woolworths price enrichment and related UI updates.
→
Should say
- Woolworths price lookup integrated with barcode scanning
- Price badge shown in FOUND and NEW_ITEM states
Current in file
Replacement
- Woolworths price lookup integrated with barcode scanning
- Price badge shown in FOUND and NEW_ITEM states
The torch toggle test does not mention the new behavior when the device doesn't support this feature.
Currently says
The device torch activates and illuminates the area in front of the camera.
→
Should say
The device torch activates or indicates unsupported if torch control is not available.
Current in file
The device torch activates and illuminates the area in front of the camera.
Replacement
The device torch activates or indicates unsupported if torch control is not available.
The sprint board does not account for the new audit fix tasks in progress.
Currently says
Story 4 > Story 2 > Story 3 > Smoke Test
→
Should say
Add short text about continuing with additional audit-related tasks after Smoke Test
Current in file
Story 4 > Story 2 > Story 3 > Smoke Test
Replacement
Story 4 > Story 2 > Story 3 > Smoke Test > Continue Audit Fix Tasks
Missing the newly launched features mentioned in the audit-fix sprint.
Currently says
Pantry is available now at pantry-app.tapfumamv.com.
→
Should say
Visit pantry-app.tapfumamv.com for the latest features including international expansion and mobile alerts.
Current in file
Pantry is available now at pantry-app.tapfumamv.com.
Replacement
Visit pantry-app.tapfumamv.com for the latest features including international expansion and mobile alerts.
The document does not reflect the plan to integrate WhatsApp input methods mentioned in the audit fix sprint.
Currently says
WhatsApp agent β unclear if existing bot or expected feature
→
Should say
WhatsApp agent β expected feature to complement existing manual input methods
Current in file
WhatsApp agent β unclear if existing bot or expected feature
Replacement
WhatsApp agent β expected feature to complement existing manual input methods
The document does not include recent sprint statuses like 'Smart Capture + Price Sprint'.
Currently says
Sprint 4 Report | /sprint-4-report.html | 2026-03-20
→
Should say
Barcode Sprint | Sprint Complete, and Smart Capture + Price Sprint | In Progress
Current in file
Sprint 4 Report | /sprint-4-report.html | 2026-03-20
Replacement
Barcode Sprint | Sprint Complete, and Smart Capture + Price Sprint | In Progress
Description of live app state is missing 'Audit Fix Sprint complete'.
Currently says
app.tapfumamv.com (live, Audit Fix Sprint complete)
→
Should say
app.tapfumamv.com (live, Smart Capture + Price Sprint in progress)
Current in file
app.tapfumamv.com (live, Audit Fix Sprint complete)
Replacement
app.tapfumamv.com (live, Smart Capture + Price Sprint in progress)