Files
ksif-manage-back/.agent-harness/references/kri-common/upgrade-and-verification.md

932 B

KriCommon Upgrade and Verification

  • Review KriCommon release notes, README changes, configuration defaults, auto-configuration conditions, and affected public APIs before upgrading.
  • Commit dependency-lock or resolved-version changes according to the consumer repository's policy.
  • Run the consumer's focused compile and tests after an upgrade, including application-context startup tests when auto-configuration or security behavior is affected.
  • Keep .agent/project.md near 2-3 KiB as a routing document. Do not delete material rules to meet the budget; move conditional schema, query, API, and migration details to routed .agent/references/ documents.
  • Do not modify KriCommon or another consumer repository unless it is explicitly included in the approved task scope.