docs(memory): clarify self-upstream release manifest semantics - #10
Merged
Conversation
Adds a dedicated 'compose refresh <pack>' subcommand that updates an installed pack's .github/ projection from its current authoritative source in one all-or-restored transaction. Editing a pack source previously made that pack unrefreshable: 'remove' refuses on the Feature 028 recorded-source digest guard, and 'add --force' early-returns as already installed. The documented remove-then-add path was unusable in exactly the case it documented. Refresh proves installed-side authority (exact profile bytes, whole-profile currency, files-to-inventory congruence, per-artifact recorded hashes), stages the current source through the canonical add pipeline, applies the destination-set difference, and updates the profile in the same transaction. It does not apply the uninstall digest guard, because it expects the source to have changed. That guard and 'add --force' semantics are unchanged.
…ing, not a release version file
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Records the source-vs-release manifest contract in the existing project context instead of adding a duplicate lesson.
This repository is its own upstream. Its source/dogfood manifest intentionally remains:
source_ref: main— live development and catalog/upgrade channelinstalled_ref: main— branch-tracking install pin, not a release versionFor a tagged release,
scripts/build-release.mjs --tag <tag>reads but does not modify that committed manifest and writes only the stageddist/manifest assource_ref: latest/installed_ref: <tag>. The repo has no package manifests and no version write-back step.Hand-bumping the committed fields would either pin upgrade/catalog resolution away from live
mainor create false upgrade status.The claim was independently audited against all production readers/writers and reproduced from the exact
origin/maintree withv0.4.8: source stayedmain/main, dist becamelatest/v0.4.8, and the source manifest hash did not change.The branch was synchronized with the squash-merged
mainbefore this PR was finalized. Net diff: one existing context entry; no new memory entry. Lint: 0 warnings, 0 failures.