name	bundle-maintenance
description	Safely update shipped bundles and generated artifacts with manifest, integrity, and smoke-test discipline.
compatibility	opencode

A repository ships an installable bundle, generated payload, or curated artifact directory that must stay reproducible.

Identify which directories are shipped artifacts versus normal source files.
Make the smallest reviewable change and preserve existing bundle structure.
Update manifest or inventory files if the shipped file set changed.
Regenerate integrity metadata such as checksums when bundled content changes.
Review whether version and changelog files should move with the shipped change.
Run the narrowest smoke tests that prove install, verify, or load behavior still works.

Treat shipped bundle content as a product surface, not just implementation detail.
Do not skip checksum or manifest updates when bundle contents change.
Call out cross-platform, installer, and verification impact explicitly.

Más de este repositorio

mismo repositorio

Run bounded iterative loops with explicit criteria, persisted state, compact summaries, and stop conditions.

Distill recurring prevention points from project patch history into learned project rules.

Capture bug-fix knowledge as reusable project patch artifacts after evidence-based fixes.

Answer only from verified evidence and refuse to guess when certainty is incomplete.

Interview the user, inspect the current repository, and bootstrap project-specific OpenCode intelligence safely.

Turn repository evidence and user answers into persistent project-specific rules, profile data, and workflow artifacts.

name	bundle-maintenance
description	Safely update shipped bundles and generated artifacts with manifest, integrity, and smoke-test discipline.
compatibility	opencode

A repository ships an installable bundle, generated payload, or curated artifact directory that must stay reproducible.

Identify which directories are shipped artifacts versus normal source files.
Make the smallest reviewable change and preserve existing bundle structure.
Update manifest or inventory files if the shipped file set changed.
Regenerate integrity metadata such as checksums when bundled content changes.
Review whether version and changelog files should move with the shipped change.
Run the narrowest smoke tests that prove install, verify, or load behavior still works.

Treat shipped bundle content as a product surface, not just implementation detail.
Do not skip checksum or manifest updates when bundle contents change.
Call out cross-platform, installer, and verification impact explicitly.