harmonyos-evolution

Document HarmonyOS build issues by recording critical failures and resolutions into an Evolution.md knowledge base. This process consolidates development challenges into a reference file to prevent repeated debugging mistakes.

Retrieve known solutions for HarmonyOS build failures by first checking the Evolution.md knowledge base. This prioritization queries recorded resolutions before resorting to deeper searches, reducing overall debugging time.

New build errors are recorded only after a successful build verification. This ensures that documented solutions in the knowledge base are proven effective before being saved for future reference.

Track undeclared identifier errors during HarmonyOS app development by logging the failure into the knowledge base. The system checks Evolution.md for a recorded solution before attempting deeper troubleshooting.

Use a knowledge base for troubleshooting HarmonyOS build problems to automate the documentation of resolutions. This prevents repeated mistakes and builds a valuable reference for future development challenges.

Check Evolution.md for build errors whenever a HarmonyOS build fails. Querying this knowledge base first ensures efficient problem-solving by retrieving known solutions before performing deeper searches.