Clarify repository scope and rule semantics

[KuGouGo]

Summary

• describe branch URLs as mutable publication references
• distinguish repository code licensing from third-party rule content
• describe rule names as upstream or configured classifications rather than accuracy claims
• align local command and publication descriptions with the implemented workflow

Source review

• reviewed build scope selection, artifact transactions, restoration identity, manifest verification, capability mapping and atomic publication
• no additional blocking source-logic defects found

Validation

• PATH=/opt/homebrew/bin:$PATH REQUIRE_SHELLCHECK=1 make preflight
• 23/23 test suites passed