chore: rename rest-owl plugin to poc-rest-owl-loop

Rename plugin directory, files, and all internal references.
The docs/rest-owl artifacts directory path is preserved as a
config default since it's a user-facing path.

https://claude.ai/code/session_0191H4s9PX5VxKfmKnrq3aYF

Author: claude

…yosmani-agentic-engineering-deep-dive.md …yosmani-agentic-engineering-deep-dive.mddocs/research/rest-owl/addyosmani-agentic-engineering-deep-dive.md renamed to docs/research/poc-rest-owl-loop/addyosmani-agentic-engineering-deep-dive.md docs/research/rest-owl/addyosmani-agentic-engineering-deep-dive.md renamed to docs/research/poc-rest-owl-loop/addyosmani-agentic-engineering-deep-dive.md

@@ -41,7 +41,7 @@
 - Agentic engineering **disproportionately benefits senior engineers**
 - Junior developers risk building code they cannot debug — "dangerous skill atrophy"
 
-## Relevance to rest-owl Plugin
+## Relevance to poc-rest-owl-loop Plugin
 
 This validates our entire architecture and highlights one gap:
 

…st-owl/biggo-missing-middle-tutorials.md …l-loop/biggo-missing-middle-tutorials.mddocs/research/rest-owl/biggo-missing-middle-tutorials.md renamed to docs/research/poc-rest-owl-loop/biggo-missing-middle-tutorials.md docs/research/rest-owl/biggo-missing-middle-tutorials.md renamed to docs/research/poc-rest-owl-loop/biggo-missing-middle-tutorials.md

@@ -11,7 +11,7 @@
 - Criticizes broad questions ("How do I build X?") in favor of discrete challenges ("What's the right data model for this entity?")
 - The owl emerges through your own effort and targeted feedback
 
-## Relevance to rest-owl Plugin
+## Relevance to poc-rest-owl-loop Plugin
 
 This is actually the **opposite** of our plugin's philosophy. Zarick argues you should struggle through it yourself. Our plugin argues the AI _can_ lay out all the steps — because it has access to the entire internet's worth of knowledge about what "all the steps" look like.
 

…/danielzarick-draw-the-owl-philosophy.md …/danielzarick-draw-the-owl-philosophy.mddocs/research/rest-owl/danielzarick-draw-the-owl-philosophy.md renamed to docs/research/poc-rest-owl-loop/danielzarick-draw-the-owl-philosophy.md docs/research/rest-owl/danielzarick-draw-the-owl-philosophy.md renamed to docs/research/poc-rest-owl-loop/danielzarick-draw-the-owl-philosophy.md

@@ -18,7 +18,7 @@
 - "SpecOps Discipline" — specs receive version control, peer review, and operational rigor equivalent to source code
 - Breaking changes require explicit human approval
 
-## Relevance to rest-owl Plugin
+## Relevance to poc-rest-owl-loop Plugin
 
 This is the most architecturally rigorous SDD model. Key insights for our plugin:
 

…st-owl/github-spec-driven-development.md …l-loop/github-spec-driven-development.mddocs/research/rest-owl/github-spec-driven-development.md renamed to docs/research/poc-rest-owl-loop/github-spec-driven-development.md docs/research/rest-owl/github-spec-driven-development.md renamed to docs/research/poc-rest-owl-loop/github-spec-driven-development.md

@@ -12,7 +12,7 @@
 - **Execute in phases, not all at once**: "Don't ask the agent to do everything in tasks.md in one go"
 - Human oversight at every transition point
 
-## Relevance to rest-owl Plugin
+## Relevance to poc-rest-owl-loop Plugin
 
 Our plugin follows this same pattern but goes broader:
 

…rest-owl/github-spec-kit-architecture.md …owl-loop/github-spec-kit-architecture.mddocs/research/rest-owl/github-spec-kit-architecture.md renamed to docs/research/poc-rest-owl-loop/github-spec-kit-architecture.md docs/research/rest-owl/github-spec-kit-architecture.md renamed to docs/research/poc-rest-owl-loop/github-spec-kit-architecture.md

@@ -11,7 +11,7 @@
 - "Other people often have to do much more to get the same results"
 - Advocates **acknowledging complexity** rather than hiding it behind elegant simplicity
 
-## Relevance to rest-owl Plugin
+## Relevance to poc-rest-owl-loop Plugin
 
 This is directly relevant to our design philosophy:
 

…infoq-spec-as-executable-architecture.md …infoq-spec-as-executable-architecture.mddocs/research/rest-owl/infoq-spec-as-executable-architecture.md renamed to docs/research/poc-rest-owl-loop/infoq-spec-as-executable-architecture.md docs/research/rest-owl/infoq-spec-as-executable-architecture.md renamed to docs/research/poc-rest-owl-loop/infoq-spec-as-executable-architecture.md

@@ -25,7 +25,7 @@
 - $4.7B market projected to $12.3B by 2027
 - Gartner: 40% of enterprise apps will have AI agents by end of 2026
 
-## Relevance to rest-owl Plugin
+## Relevance to poc-rest-owl-loop Plugin
 
 **Our plugin IS agentic engineering applied to project creation.** Key alignment: