Future Improvements for AI Tasks

[nsaulnier-ti]

Collect feedback here to improve the docs_ai/task_* documents going forward.

[nsaulnier-ti]

collected after re-validating the import process for #132 - AI selected "port_project" instead of "create_project"

Feedback on task_create_project.md:

1. "From Scratch" in the title excludes the case of importing a PRU project from outside of OpenPRU repo into OpenPRU repo. The title reads as "writing new firmware," so an agent seeing existing
   firmware files from an external source (PSSP, PSDK, another repo) is unlikely to select this runbook. Rename to Create or Import a
   New OpenPRU Project or just drop "from Scratch."

2. feedback was invalid

3. D2 has no compatibility assessment for imports. When importing, the firmware already exists and may use device-specific features.
   For new-from-scratch projects this is a non-issue, but for imports it is the same compatibility question as D3 in
   task_port_project.md. The import case would benefit from a note in D2: "If importing existing firmware, also check Npru/N-hw/N-sw
   compatibility (see task_port_project.md §D3) before committing to the target device list."

4. feedback was invalid

---

Root cause of the routing error: neither document has a header that says "use me when X, not when Y." The runbooks are
well-structured individually but have no mutual disambiguation. A two-line routing note in each would prevent an agent from picking
the wrong one.

● Feedback on task_port_project.md:

1. No scope boundary statement. The document has no sentence distinguishing its scope from task_create_project.md. The first line
   says "Port an Existing Project to a New Device or Board" but "existing project" is ambiguous — it could mean "any existing firmware"
   or specifically "an already-in-OpenPRU project." A one-line disambiguator at the top would close this:

▎ "This task covers porting a project already in this OpenPRU repository to a new device or board. If you are adding a new project
▎ (including importing from an external source), use task_create_project.md instead."

2. The decision tree works well for validation. D1-D3, Section A/B routing, and V1-V6 map cleanly onto validating an import. The
   runbook is usable for validation even though it was written for execution. No changes needed there.