📚 Add release preparation skill and refresh Almanac

[Vivekyy]

Adds a centralized release-preparation skill that synchronizes version-bearing manifests, ingests the complete range since the previous release, Gardens the wiki, and validates package and documentation state. Refreshes the Almanac across runtime batching and reports, telemetry, prompt history, test-generation intent, package/build behavior, changed-line coverage, CI, and release automation. Validated with CodeAlmanac health and validation, agent-layout and Markdown checks, TypeScript typechecking, all 43 tests, and the production build.

---

Greptile Summary

Adds a centralized package-release preparation skill and refreshes the Almanac to document current release, runtime telemetry, test-generation, packaging, coverage, CI, and contributor workflows.

• Introduces shared release-skill metadata and operational instructions.
• Documents synchronized version manifests and tag-to-HEAD Almanac ingestion.
• Updates runtime, telemetry, prompt-history, test-generation, package, build, and automation references.
• Extends the Almanac topic catalog for the new release guide.

Confidence Score: 4/5

The release skill should be fixed before merging because its mandatory npm-version step cannot safely review a branch that already contains the intended bump.

The skill explicitly targets already-bumped branches but always applies npm version, which either advances the version again or rejects an unchanged explicit version; its reduced local validation can also defer coverage and package-shape failures until CI or publishing.

Files Needing Attention: .agents/skills/prepare-package-release/SKILL.md

Important Files Changed

Filename	Overview
.agents/skills/prepare-package-release/SKILL.md	Adds the release workflow, but mishandles already-bumped branches and omits two publication checks from local validation.
.agents/skills/prepare-package-release/agents/openai.yaml	Adds consistent agent-facing metadata for invoking the release skill.
almanac/guides/release/prepare-package-release.md	Adds contributor guidance mirroring the centralized release process.
almanac/architecture/runtime/telemetry.md	Refreshes telemetry documentation for pseudonymized run events and best-effort dispatch.
almanac/architecture/runtime/rudder-skill-runtime.md	Documents bounded rewrite batches, run telemetry, and per-prompt reports.
almanac/topics.yaml	Registers the new release-preparation guide in the Almanac topic hierarchy.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[Confirm intended release version] --> B[Synchronize package and plugin manifests]
  B --> C[Resolve previous rudder-plugin tag]
  C --> D[Ingest tag-to-HEAD range and worktree diff]
  D --> E[Garden Almanac]
  E --> F[Validate wiki and package]
  F --> G[Merge]
  G --> H[Publish workflow creates missing artifacts]

Loading

_{Reviews (1): Last reviewed commit: "📚 Add release preparation skill and ref..." | Re-trigger Greptile}

Greptile also left 2 inline comments on this PR.

[github-actions]

🔌 Merging this PR will release the Rudder plugin

Publish @ruddercode/rudder-plugin@0.1.4 through npm Trusted Publishing.
Create the plugin tag rudder-plugin-v0.1.4.
Create the GitHub Release for rudder-plugin-v0.1.4.

The release runs through .github/workflows/publish.yml after merge.

[ghost]

Ready to review this PR? Stage has broken it down into 7 individual chapters for you:

	Title
1	Refresh Almanac topics and getting started
2	Document telemetry and local state changes
3	Refine skill runtime and prompt history
4	Update intent-driven test generation standards
5	Enforce changed-line coverage in CI
6	Update plugin package and build reference
7	Add release preparation skill

_{Chapters generated by Stage for commit c4469bc on Jul 30, 2026 6:54pm UTC.}

[greptile-apps]

Already-bumped versions advance again

When this skill reviews a branch that already contains the intended version bump, step 3 still runs npm version; a bump-level argument advances the version again, while the unchanged explicit version is rejected by npm, preventing the documented review workflow from completing with the confirmed release version.

[greptile-apps]

Release validation omits publish gates

The new workflow reports package validation without running the changed-line coverage check or package dry run required by the publishing workflow, so contributors can receive a successful preparation report only for CI or post-merge publishing to reject the same revision.