Taste.md adds lot of redundant info which leads to low quality code

Summary

If projects is being built using AI, it evolves rapidly within a week. Taste fails to update obsolete info and leads to conflicting statements. This causes lower quality code and token burn.

Expected Behavior

Taste should update dynamically- not even add new info but also replace older, outdated info.

Actual Behavior

1. Attached taste.md from a Wordpress project I started working on. It has obsolete info about initial scaffolding struggles. Also refer the QA video from Github Copilot. The project has moved to building custom plugins and themes within days, the taste.md has become obsolete.
2. Attached another file it created under commandcode/workflow/taste.md.

taste (1).md
taste.md
https://github.com/user-attachments/assets/a3e2f726-d2c7-4990-9093-97f5d25bbe2c

Note in initial scaffolding I setup puppeteer, then moved to playwright mcp and removed puppeteer. But taste.md still asks to use puppeteer >> more confusion >> lower quality code.

Steps to reproduce the issue

Move a project rapidly from one stage to another and watch whether taste is able to replace obsolete info.

Command Code Version

0.26.8

Operating System

Linux

Terminal/IDE

vscode

Shell

bash

Additional context

My env is WSL-Ubuntu

Start by comparing the attached taste.md files, especially the stale Puppeteer guidance versus the later Playwright MCP setup, and trace where commandcode/workflow/taste.md is generated or updated. Done should include a reproducible project transition where obsolete guidance is replaced rather than retained, with the resulting taste.md no longer giving conflicting instructions.