Add Koinara record provenance tracking

[Shinichi-Toue]

Summary

Add public-safe provenance tracking for Koinara records so agents and readers can distinguish records distilled from the founding internal set from future external or mixed-origin records.

What changed

• Add required origin and sources frontmatter to the public record schema.
• Backfill all five existing records as origin: internal with public-safe Aigora source references.
• Render provenance in record HTML and generated Markdown endpoints.
• Include provenance in generated public metadata and /llms.txt record summaries.
• Add docs/record-provenance.md covering public frontmatter and the private internal registry boundary.
• Extend npm run lint:public so provenance is required and obvious private identifiers/source-kind mismatches fail CI.

Source references

The public repo stores only public-safe references such as:

• aigora-record:<record-id>
• aigora-path:<repo-relative-path>

Private workflow/database pointers stay in the internal registry, not in public Markdown or rendered pages.

Verification

• npm run lint:public — passed, 5/5 records included
• npm run check — passed, Astro diagnostics 0 errors / 0 warnings / 0 hints
• npm run build — passed, 9 static pages built and Pagefind indexed
• npm run ci — passed

[cloudflare-workers-and-pages]

Deploying koinara-site with    Cloudflare Pages

Latest commit:	567124f
Status:	✅  Deploy successful!
Preview URL:	https://2d338cf9.koinara-site.pages.dev
Branch Preview URL:	https://q1453-koinara-provenance-tra.koinara-site.pages.dev

View logs