Story: Rename the package and PHP namespace to spatial-encoder #26

Goal

Rename the library identity in the codebase from spatial-writer / LongitudeOne\SpatialWriter to spatial-encoder / LongitudeOne\SpatialEncoder, consistently with the architecture defined by #19.

This Story covers the package and source-code rename. The GitHub repository itself is renamed separately.

Scope

• Rename the Composer package to longitude-one/spatial-encoder.
• Rename the production namespace to LongitudeOne\SpatialEncoder.
• Update PSR-4 autoloading.
• Update production namespaces and imports.
• Update test namespaces and imports.
• Update source and test paths where required by the project structure.
• Update internal configuration, development scripts, and quality-tool configuration affected by the rename.
• Remove internal references to SpatialWriter and longitude-one/spatial-writer where they refer to the package/code identity.

Acceptance criteria

• composer.json declares the package as longitude-one/spatial-encoder.
• Production code uses the LongitudeOne\SpatialEncoder namespace.
• Tests use the corresponding LongitudeOne\SpatialEncoder\Tests namespace structure.
• Composer PSR-4 autoloading resolves the new namespace correctly.
• No production class remains under LongitudeOne\SpatialWriter.
• No compatibility namespace, class alias, or deprecated Writer namespace is retained.
• Internal scripts and quality configuration reference the new package/namespace where applicable.
• The complete test suite succeeds using the new namespace.
• All configured quality checks succeed.

Validation gate

A repository-wide search must confirm that remaining occurrences of SpatialWriter or longitude-one/spatial-writer, if any, are intentional and relate only to repository-level migration work handled by the final integration Story.

Out of scope

• Renaming the GitHub repository.
• Backward-compatibility aliases.
• Changes to encoding semantics.
• New encoding formats or spatial representation support.

Parent Epic

#19

Dependencies

Depends on completion of the generic Encoder API Story.

Estimate

3 Story Points