D2: re-run capped taxonomy + content enrichment after owner reset (#167)

[xenodeve]

Parent

Part of #167
Blocked by: owner-reset child (must land first)

EN

What to do

After owners are auto on empty fields, dry-run then capped apply:true on Nest prod:

1. POST /github/generate-taxonomy (cap 1+)
2. POST /github/generate-case-studies (empty content path)
3. Continue POST /github/refresh/missing-readme as needed (27 missing)
4. gh workflow run screenshot-projects.yml when live_urls exist

Record HTTP bodies on this issue. Revalidate /projects after applies.

Acceptance

• Taxonomy candidates > 0 after owner reset
• At least one project gains category/tech/tags
• At least one gains deep content (or documented skip: no README)
• Hype-Macro_Store improves vs audit 2/8 when README present

Audit excerpt

Parent #167 — only MangaDock has taxonomy/content today.

---

TH

งาน

dry-run → apply แบบ capped หลัง reset owner

เกณฑ์รับ

taxonomy candidates > 0 · มีอย่างน้อย 1 โปรเจกต์ได้หมวด/tech/content

[xenodeve]

EN — D2 first capped wave APPLIED

After #168 owner reset:

Dry-run: taxonomy candidates:46 (was 0); case-study candidates:46.

Apply ×5 each (cap 1/run):

• taxonomy: candidates 46→42 (5 projects categorized)
• case-study: 5 applies returned generated:1 each

DB after wave (published with category+content):

slug	techs	tags	content
mangadock	7	5	yes
hype-macro-store	17	6	yes
facedetection	3	6	yes
home-iot-system	9	7	yes
resume-web	7	6	yes
xeno-skills	6	9	yes

Hype-Macro_Store (audit 2/8) now has category + tech + tags + deep content. Remaining empties converge via hourly cron (generate-taxonomy / generate-case-studies / missing-readme). Leaving this issue open until scoreboard improves further or agent closes with a second wave.

TH — D2 รอบแรกทำแล้ว

Hype-Macro_Store ได้หมวด/tech/tags/content แล้ว · อีก ~40 แถวให้ cron ไล่ต่อ