Public Access
chore: rename all mokoplatform → mokocli references (repo renamed)
#336
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
The repo
mokoplatformwas renamed tomokoclion Gitea, but stalemokoplatformreferences remain scattered across this repo and the template repos. This is the umbrella tracking issue for a full rewrite.Decided scope: rewrite everything (all token categories)
.../MokoConsulting/mokoplatform→.../mokocli/opt/mokoplatform/cli,/tmp/mokoplatform-api→/opt/mokocli/...auto-bump.ymletc.mokoplatform.git→mokocli.gitEXCLUDE="… mokoplatform …"→… mokocli …MokoPlatform.*/INGROUP: MokoPlatform→MokoCLI.*xmlns="https://standards.mokoconsulting.tech/mokoplatform/1.0"→.../mokocli/1.0<mokoplatform>→<mokocli>moko-platform-schema.xsd→moko-cli-schema.xsd⚠ Namespace caveat
Renaming the XML namespace URI (
.../mokoplatform/1.0) and the XSDtargetNamespacekeeps local manifest-vs-XSD validation consistent (both change together). However the externalstandards.mokoconsulting.techserver still publishes the old namespace — that endpoint must be updated to match, or any validator that fetches the live schema will fail. Track that as a follow-up on the standards server.Affected repos (checklist)
mokocli— 430 occurrences across ~202 files (this repo)Template-Client-WaaS—/opt/mokoplatform, clone URLs,manifest.xmlnamespace,branch-protection.ymlEXCLUDE,CLAUDE.md,ISSUE_TEMPLATE/config.ymlTemplate-MCP— same set as Template-Client-WaaSMokoSuiteBackup— 1 ref (.mokogitea/CLAUDE.mdMokoStandards wiki URL) — handled inlineReplacement rules (case-sensitive)
Delivery: branch + PR per repo.