chore: Align the Stock Indicators for Python project with the org template

[DaveSkender]

Context

Stock Indicators for Python (org Project #16) is this repository's work board. It was not created from the org-level project template, so its fields diverge from every other board.

Standard template: https://github.com/orgs/facioquo/projects/3

Current vs. expected

Field	Current	Expected (template)
Status	🧊 Icebox / 🔖 Do next / 🏗 In progress / 👀 In review / ✅ Done	🧊 Icebox / 📦 Backlog / 🔖 Do next / 🏗 In progress / 👀 In review / ✅ Done
Priority	—	🌋 Urgent / 🏔 High / 🏕 Medium / 🏝 Low
Size	—	🐋 X-Large / 🦑 Large / 🐂 Medium / 🐇 Small / 🦔 Tiny

Gap: Status is missing 📦 Backlog; no Priority; no Size

Acceptance criteria

• Status single-select matches the template's six options, including colors (Icebox GRAY, Backlog GREEN, Do next GREEN, In progress YELLOW, In review ORANGE, Done PURPLE)
• Priority single-select exists with the four template options
• Size single-select exists with the five template options
• Any item whose Status value is dropped by the change is re-set to the closest template stage (replacing a single-select's options orphans existing values — re-set them explicitly)

Notes

• Reference implementations: Memory (org Project refactor: Rename package name #31) and Identity and Access Management (IAM) (refactor: Refactor Quote class #39) are correct; diff against either.
• The template's Priority and Size currently have no options. The deprecated Priority (old) / Size (old) fields were removed from Project Add dll for _cslib #3 on 2026-07-27, and the surviving Priority / Size fields are still empty — so copying the template today yields unusable single-selects. Populate them from the table above, or diff against a reference implementation rather than against Add dll for _cslib #3.
• Project Add dll for _cslib #3 also carries an empty Roadmap field that neither reference implementation has; treat it as out of scope here.
• Projects refactor: Update import statements #40–43 (Management & Governance, porg, Design system, Agentics) still carry the Priority (old) / Size (old) fields and need the same trim — tracked separately.
• Fields can be updated via the GraphQL API (updateProjectV2Field for Status, createProjectV2Field for Priority/Size) or by hand in the Projects UI.

Work mode

🤖 AGENT READY