feat(publisher): persist compile manifest as manifest.json blob

[patoperpetua]

Summary

• Upload manifest.json as a third blob under each template prefix (tenants/{tenant}/{env}/templates/{key}/manifest.json) with application/json; charset=utf-8, containing contentHash, compiledAt, sourceCommit, and related compile manifest fields.
• Keep the existing per-template stdout JSON line unchanged so log-scraping continues to work; BlobTemplateStore still reads only template.html and metadata.json.
• Update docs/guides/template-publishing.md to document the new blob and its operational (non-send-path) role.

Closes #69

Test plan

• pnpm --filter @singleton-sd/post-kit-publisher test — asserts manifest blob path, content type, payload fields, and unchanged stdout shape
• pnpm --filter @singleton-sd/post-kit-compiler test
• pnpm -r --if-present run test

Made with Cursor

Summary by CodeRabbit

• New Features

  • Published templates now include a manifest.json file alongside the HTML and metadata.
  • The manifest includes compilation provenance and change-detection details.
  • Manifest files use the standard application/json content type.

• Bug Fixes

  • Existing templates remain compatible when manifest files are present.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 57dd5a97-fde8-457e-b16c-a39ccccd520a

📥 Commits

Reviewing files that changed from the base of the PR and between 1e667ae and 92d368d.

📒 Files selected for processing (3)

• docs/guides/template-publishing.md
• packages/post-kit-publisher/src/publish.spec.ts
• packages/post-kit-publisher/src/publish.ts

Included review availability: Your plan provides up to 10 included reviews per hour; 3 remain after this review.

---

📝 Walkthrough

Walkthrough

Template publishing now stores manifest.json with compile metadata alongside template.html and metadata.json. Tests verify the payload, content type, paths, hashing, timestamps, source commit, and structured logging. Documentation records compatibility with older templates.

Changes

Template manifest publishing

Layer / File(s)	Summary
Upload and validate compile manifests packages/post-kit-publisher/src/publish.ts, packages/post-kit-publisher/src/publish.spec.ts	The publisher uploads formatted manifest.json content with an application/json content type. Tests verify manifest fields, content hashing, artifact paths, content types, and the unchanged single-line structured log.
Document stored artifacts and compatibility docs/guides/template-publishing.md	The guide documents the three uploaded blobs, manifest metadata, preserved stdout output, and compatibility with templates that lack a manifest.

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk: ⚪ Minimal · up to 92d36

This change adds a non-send-path manifest.json blob while preserving the existing template blobs and stdout format; no actionable merge-blocking risk remains after normal checks and review.

Sequence Diagram(s)

sequenceDiagram
  participant Publisher
  participant BlobStorage
  participant TemplateAPI
  Publisher->>BlobStorage: Upload template.html and metadata.json
  Publisher->>BlobStorage: Upload manifest.json as application/json
  Publisher-->>Publisher: Emit one structured summary line
  TemplateAPI->>BlobStorage: Read template.html and metadata.json
  BlobStorage-->>TemplateAPI: Return template content and metadata

Loading

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 2 functions across 2 files. (1 skipped: 1 …	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the primary change: persisting the compiler manifest as a manifest.json blob.
Description check	✅ Passed	The description includes the linked issue, change summary, test commands, compatibility impact, and documentation impact. It omits the template's detailed setup, step-by-step expected results, feedbac…
Linked Issues check	✅ Passed	The changes satisfy issue #69: they upload manifest.json for each template, use the required content type and template prefix, preserve stdout output, keep BlobTemplateStore compatibility, add tests, …
Out of Scope Changes check	✅ Passed	The code, tests, and documentation changes directly support issue #69. No unrelated changes are identified.

Full details: Description check

Explanation

The description includes the linked issue, change summary, test commands, compatibility impact, and documentation impact. It omits the template's detailed setup, step-by-step expected results, feedback focus, and Automated checks heading, but the core information is complete.

Full details: Linked Issues check

Explanation

The changes satisfy issue #69: they upload manifest.json for each template, use the required content type and template prefix, preserve stdout output, keep BlobTemplateStore compatibility, add tests, and update the documentation.

Full details: Docstring Coverage

Explanation

Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 2 functions across 2 files. (1 skipped: 1 unsupported.)

• Fix all pre-merge checks with AI

✨ Finishing Touches 💡 1

📝 Generate docstrings 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/69-persist-compile-manifest

---

_{Comment @coderabbitai help to get the list of available commands.}