Align release publication policy and runbook

docs/development.md

@@ -78,8 +78,9 @@ go test ./internal/config -run '^TestExamplesLoadAndValidate$'
 
 The documentation check verifies local Markdown links and the dependency graph
 of the Woodpecker workflows. The configuration check loads every maintained
-pipeline and session example. Tag CI reuses this validation path before its
-asynchronous asset publication; the maintainer release boundary is documented
+pipeline and session example. Tag CI independently revalidates the tagged source
+before asynchronous asset delivery; it is not a second synchronous release
+prerequisite. The normal maintainer entry point is the single publication command
 in the [Release Procedure](release.md).
 
 Woodpecker also runs `go test -race -shuffle=on -count=3 ./...` on its scheduled