refactor: rename databind-metaschema module to databind-modules (#617)

* refactor: rename databind-metaschema module to databind-modules (#588)

Rename the Maven module directory from databind-metaschema to
databind-modules for better clarity. The module contains Metaschema
binding modules, not a metaschema for databind.

- Rename directory databind-metaschema/ to databind-modules/
- Update parent pom.xml module reference
- Update .gitmodules submodule path
- Update module pom.xml SCM URL
- Update all documentation references (CLAUDE.md, .claude rules/skills)
- Update PRD path references
- Update test resource schema path

Note: Maven artifact coordinates (metaschema-databind-modules) and
Java module name (gov.nist.secauto.metaschema.databind.modules)
remain unchanged - only the directory name changes.

Fixes #588

* chore: ignore transient 404 for databind-modules during rename PR

Author: david-waltermire

.claude/rules/metaschema-authoring.md

@@ -23,7 +23,7 @@ This rule defines repository-specific conventions for authoring Metaschema modul
 For YAML Metaschema modules, configure IDE validation using the generated JSON schema:
 
 ```text
-databind-metaschema/target/generated-resources/schema/json/metaschema-model_schema.json
+databind-modules/target/generated-resources/schema/json/metaschema-model_schema.json
 ```
 
 Build with `mvn install` first to generate the schema.

.claude/skills/metaschema-java-library.md

@@ -19,7 +19,7 @@ metaschema-framework (parent)
 ├── core                    - Core API, Metapath engine, model interfaces
 ├── databind                - Data binding, serialization, code generation
 ├── schemagen               - XML/JSON schema generation
-├── databind-metaschema     - Metaschema binding modules
+├── databind-modules        - Metaschema binding modules
 ├── metaschema-maven-plugin - Maven plugin for code/schema generation
 ├── metaschema-testing      - Testing utilities
 ├── cli-processor           - CLI framework

.gitmodules

@@ -5,7 +5,7 @@
 [submodule "core/qt3tests"]
 	path = core/qt3tests
 	url = https://github.com/w3c/qt3tests.git
-[submodule "databind-metaschema/modules"]
-	path = databind-metaschema/modules
+[submodule "databind-modules/modules"]
+	path = databind-modules/modules
 	url = https://github.com/metaschema-framework/metaschema-modules.git
 	branch = develop

.lycheeignore

@@ -69,3 +69,5 @@ https://projects.eclipse.org/projects/eclipse.jdt
 http://www.gnu.org/software/classpath/license.html
 # fix later
 https://github.com/metaschema-framework/liboscal-java/
+# transient 404 during module rename PR - remove after merge
+https://github.com/metaschema-framework/metaschema-java/tree/develop/databind-modules/.*

CLAUDE.md

@@ -72,7 +72,7 @@ metaschema-framework (parent)
 ├── core (metaschema-core) - Core API, Metapath expression language
 ├── databind (metaschema-databind) - Data binding and code generation
 ├── schemagen (metaschema-schema-generator) - XML/JSON schema generation
-├── databind-metaschema - Metaschema binding modules
+├── databind-modules - Metaschema binding modules
 ├── metaschema-maven-plugin - Maven plugin for code/schema generation
 ├── metaschema-testing - Testing utilities
 ├── cli-processor - CLI framework
@@ -139,7 +139,7 @@ See the README.md files in each module for detailed instructions.
 
 **YAML-first approach**: When creating new Metaschema modules, prefer YAML format over XML.
 - YAML modules use `.yaml` extension and are stored in `src/main/metaschema/`
-- Use the JSON schema at `databind-metaschema/target/generated-resources/schema/json/metaschema-model_schema.json` for IDE validation
+- Use the JSON schema at `databind-modules/target/generated-resources/schema/json/metaschema-model_schema.json` for IDE validation
 - Reference existing YAML modules (e.g., `databind/src/main/metaschema/metaschema-bindings.yaml`) for structure examples
 
 ### Key Interfaces

PRDs/20251221-xmlbeans-removal/implementation-plan.md

@@ -14,7 +14,7 @@ This document details each PR for removing XMLBeans and replacing it with Metasc
 
 **Metaschema Module JSON Schema** (for YAML module authoring):
 ```text
-databind-metaschema/target/generated-resources/schema/json/metaschema-model_schema.json
+databind-modules/target/generated-resources/schema/json/metaschema-model_schema.json
 ```
 
 Use this schema for IDE validation when authoring the YAML Metaschema modules.

PRDs/20251224-codegen-quality/implementation-plan.md

@@ -116,7 +116,7 @@ This PR extends the binding configuration to support overriding default collecti
 | `databind/src/main/java/gov/nist/secauto/metaschema/databind/codegen/config/DefaultBindingConfiguration.java` | Parse `<collection-class>` element |
 | `databind/src/main/java/gov/nist/secauto/metaschema/databind/codegen/typeinfo/IPropertyTypeInfo.java` | Update `getCollectionImplementationClass()` to accept override |
 | `databind/src/main/java/gov/nist/secauto/metaschema/databind/codegen/typeinfo/AbstractModelInstanceTypeInfo.java` | Apply collection class override from binding config |
-| `databind-metaschema/src/main/metaschema/metaschema-bindings.yaml` | Add `collection-class` field definition to binding schema |
+| `databind-modules/src/main/metaschema-bindings/metaschema-bindings.yaml` | Add `collection-class` field definition to binding schema |
 
 ### Implementation Approach