feat(standards): serve service version-wiring rule + bundle wiki pages in MCP
Versioning standard now states services must read their VERSION (e.g. a build arg) rather than hardcoding it; the compliance prompt repeats it. build_bundle also bundles src/wiki/** as wiki_-prefixed modules (e.g. docs://modules/wiki_development_releasing), so the release runbook is reachable from the MCP. Bundle grows to 22 modules.
This commit is contained in:
@@ -107,7 +107,8 @@ _COMPLIANCE_TEXT = (
|
||||
" from `get_drone_template(\"drone-pypi\")` (`python-lib.yaml`, tag-triggered).\n"
|
||||
"- **service / site** — root `VERSION`; root `CHANGELOG.md`; Drone file from\n"
|
||||
" `get_drone_template(\"drone-service\")` (`service-docker.yaml`; tag-triggered\n"
|
||||
" service variant, push-triggered site variant).\n\n"
|
||||
" service variant, push-triggered site variant). The service must read its\n"
|
||||
" version from `VERSION` (e.g. a build arg) — never hardcode it.\n\n"
|
||||
"Steps:\n"
|
||||
"1. Inspect each repo (`git -C <path> tag`, version file, `CHANGELOG.md`,\n"
|
||||
" `.drone.yml`) and list the gaps — never assume.\n"
|
||||
|
||||
Reference in New Issue
Block a user