Loom import creates a placeholder article and never fetches the transcript

POST /api/docs/import-loom validates the URL and then creates a placeholder article. Its own docstring says so:

 * Accepts a Loom URL and generates a knowledge base article from the video transcript.
 * Currently stubbed — creates a placeholder article after validation.
 * In production this would fetch the Loom transcript via their API and pass it to AI.

The UI at apps/web/src/components/docs/loom-import.tsx gives no indication the article is empty.

Why it matters

An admin imports a Loom, sees a new article appear, and reasonably concludes it worked. That placeholder then becomes a knowledge-base document the AI can retrieve and cite — a hollow article is worse for groundedness than no article.

Fix

Fetch the transcript via the Loom API and pass it through the article generator, or make the stub visible: return 501 and remove the import affordance until the transcript path exists.

Start with the POST /api/docs/import-loom handler and its docstring, then inspect apps/web/src/components/docs/loom-import.tsx. Verify the current placeholder behavior and determine which stated path fits the project; done means imports no longer create hollow articles and the UI accurately reflects support.