Public Access
feat: metadata CLI tools and MCP extraction #256
Reference in New Issue
Block a user
Delete Branch "feature/metadata-cli"
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\n\n- Rename
manifest_*CLI tools →metadata_*with backward-compatible wrappers\n- Add--set field=valuesupport tometadata_read.phpfor updating metadata XML fields\n- Auto-migratemanifest.xml→metadata.xmlon first read (copy + delete old)\n- Addmanifest_integrity.php→metadata_integrity.phpfor org-wide validation\n- Extract all MCP servers from monorepo to standaloneA:/MCP/directories\n- Publish all 9 MCP servers to npm and Gitea package registry\n- Update changelog for MCP extraction and npm publishing\n\n## Changes\n\n| File | Change |\n|------|--------|\n|cli/metadata_read.php| Read + set metadata fields, auto-migrate manifest→metadata |\n|cli/metadata_detect.php| Detect display_name, target_version, php_minimum |\n|cli/metadata_integrity.php| New — org-wide metadata validation (564 lines) |\n|cli/metadata_element.php| Renamed from manifest_element |\n|cli/metadata_licensing.php| Renamed from manifest_licensing |\n|cli/manifest_*.php| Now backward-compat wrappers to metadata_* |\n|.mokogitea/metadata.xml| New canonical name (replaces manifest.xml) |\n|templates/repos/joomla/*| MokoSuite references in Makefile and composer.json |\n|CHANGELOG.md| MCP extraction, npm publishing, manifest→metadata rename |\n\n## Test Plan\n\n- [ ]php cli/metadata_read.php --path . --allreads fields correctly\n- [ ]php cli/metadata_read.php --path . --set platform=phpupdates XML\n- [ ]php cli/manifest_read.php --path . --allstill works via wrapper\n- [ ] Auto-migration: repo with manifest.xml gets migrated to metadata.xml on read\n- [ ]--setrejects unknown field namesPull request closed