Organize changelogs: create separate TypeScript package changelog

- Create dedicated packages/typescript/CHANGELOG.md with complete TypeScript package history (v1.4.0-v1.10.0)
- Update main CHANGELOG.md to reference package-specific changelog instead of duplicating TypeScript implementation details
- Maintain protocol-focused structure in main changelog while providing detailed package documentation separately
- Ensure all TypeScript package releases and features remain accessible through dedicated changelog

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: pelle

CHANGELOG.md

@@ -17,13 +17,8 @@ This changelog focuses on:
 ## [2025-08-21]
 
 ### Added
-- **TypeScript Package - Zod v4 Validation**: Added comprehensive runtime validation for TAP messages
-  - New `validator` module available at `@taprsvp/types/validator` 
-  - Zod v4 schemas for all TAP message types (Transfer, Payment, Authorize, etc.)
-  - Validation functions: `validateTAPMessage()`, `parseTAPMessage()`, `isTAPMessage()`
-  - Message-specific validators for each TAP message type
-  - Full CAIP-10, CAIP-19, PayTo URI, and DID validation
-  - Separate module path keeps validators optional for bundle size optimization
+- **TypeScript Package v1.10.0**: Enhanced Zod v4 validation with strict ISO standards validation
+  - See [packages/typescript/CHANGELOG.md](packages/typescript/CHANGELOG.md) for complete details
 
 ### Changed
 - **BREAKING: TAIP-15 Agent Connection Protocol**: Major restructure to support multi-party connections
@@ -33,7 +28,7 @@ This changelog focuses on:
   - Added "Parties and Agent Roles" section clarifying two-party connection model
   - Added support for AddAgents messages to dynamically add agents during connection flow
   - Updated all examples and diagrams to use Merchant/Customer/PSP Agent terminology
-  - Updated TypeScript interfaces, JSON schemas, and test vectors to match new structure
+  - Updated JSON schemas, and test vectors to match new structure
   - Removed `type` attributes from all agent examples across codebase for consistency with TAIP-5 specification
 
 ### Fixed
@@ -43,69 +38,18 @@ This changelog focuses on:
   - Updated TAIP-14 example to include merchant agent and proper `for` attributes
   - Ensures consistency with TAIP-15 and TAIP-17 agent array requirements
 
-### Added
 - **TypeScript Package v1.9.0**: Released with TAIP-15 agent restructuring support
-  - **Updated Connect Interface**: Restructured to support new requester/principal/agents pattern
-    - Added `requester` and `principal` Party fields to Connect interface
-    - Replaced single `agent` field with required `agents` array
-    - Agents array must include at least one agent with `@id` matching DIDComm `from` field and `for` attribute set to requester DID
-    - Updated JSDoc documentation to reflect TAIP-15 specification changes
-    - Maintained backward compatibility for existing message types
-  - **Enhanced Agent Interface**: Updated agent structure to support multi-party connections
-    - Clarified `for` attribute usage in agent definitions
-    - Updated documentation to reference TAIP-5 specification for agent details
-    - Consistent agent array patterns across Transfer, Payment, and Connect messages
+  - See [packages/typescript/CHANGELOG.md](packages/typescript/CHANGELOG.md) for complete details
 
 - **TypeScript Package v1.8.0**: Released with enhanced DIDComm v2.1 support and new message types
-  - **DIDComm Attachments Support**: Added full DIDComm v2.1 attachments support
-    - Added `Attachment` interface following DIDComm v2.1 specification
-    - Added optional `attachments` array to `DIDCommMessage` interface
-    - Supports inline data (base64, JSON), external links, and cryptographic integrity verification (JWS, hash)
-    - Includes comprehensive documentation with usage examples for different attachment types
-    - Enables inclusion of supplementary documents like KYC verification, receipts, and compliance documentation
-  - **DIDComm Out-of-Band Messages**: Added support for out-of-band invitation messages
-    - Added `OutOfBandInvitation` interface extending `DIDCommMessage<OutOfBandGoal>`
-    - Added `OutOfBandGoal` interface for invitation body fields
-    - Supports QR codes, URLs, emails for sharing invitations
-    - Enables bundling initial protocol messages (like Connect requests) with invitations
-    - Compatible with TAIP-15 Agent Connection Protocol for TAP-specific connections
-  - **Presentation Message**: Added support for verifiable credential presentations per TAIP-8
-    - Added `PresentationMessage` interface implementing DIDCommReply with empty body
-    - Requires attachments containing verifiable presentations
-    - Follows WACI Present Proof protocol v3.0 specification
-    - Enables selective disclosure for privacy-preserving identity verification
-  - **Enhanced Message Type Support**: Expanded TAPMessage union type to include 19 message types
-    - Added PresentationMessage to support TAIP-8 selective disclosure
-    - Improved cross-reference documentation for all TAIP specifications
+  - See [packages/typescript/CHANGELOG.md](packages/typescript/CHANGELOG.md) for complete details
 
 ## [2025-08-18]
 
 ### Added
 - **TypeScript Package v1.7.0**: Released enhanced TypeScript library with comprehensive documentation and fixes
-  - Added comprehensive README.md with installation guide, quick start examples, and complete API reference
-  - Enhanced examples with current type definitions (Person, Organization, Agent, Party)
-  - Added nameHash examples for travel rule compliance with privacy-preserving name matching
-  - Updated participant type documentation to reflect current schema.org-based interfaces
-  - Added complete participant interfaces documentation (Person, Organization, Agent, Party)
-  - Enhanced travel rule compliance examples with IVMS101 data structures
-  - Improved developer experience with detailed usage examples and standards compliance information
+  - See [packages/typescript/CHANGELOG.md](packages/typescript/CHANGELOG.md) for complete details
 
-### Fixed
-- **Payment Message Type**: Removed erroneous `defaultAddress` field from Payment interface
-  - Fixed Payment interface to comply with TAIP-14 specification
-  - Settlement addresses should be provided by agents with SettlementAddress role, not as direct fields
-  - Maintained `fallbackSettlementAddresses` field as specified in TAIP-14
-  - Updated JSDoc examples to remove invalid `defaultAddress` references
-
-- **TAIP-12 Name Hashing Implementation**: Added production-ready TypeScript implementation for privacy-preserving name matching
-  - Added `generateNameHash()` function with SHA-256 hashing using Web Crypto API and Node.js crypto fallback
-  - Added `normalizeForHashing()` function for TAIP-12 compliant name normalization (uppercase, whitespace removal)
-  - Cross-platform compatibility supporting browsers and Node.js environments without additional dependencies
-  - Comprehensive test suite with 19 test cases including TAIP-12 specification test vectors
-  - Support for non-Western names (Arabic, Chinese, Korean, Japanese scripts)
-  - Compatible with VerifyVASP and GTR networks per TAIP-12 specification
-  - Added Vitest testing framework for comprehensive validation
-  - Enhanced TypeScript package (@taprsvp/types) with new nameHash utilities
 
 ## [2025-08-16]
 
@@ -141,12 +85,7 @@ This changelog focuses on:
   - Added privacy recommendations for selective disclosure of natural person information
   - Clarified that this capability was always supported by the JSON-LD extensibility but was not explicitly documented
 - **TypeScript Package v1.6.0**: Released enhanced TypeScript library with comprehensive documentation
-  - Added comprehensive JSDoc documentation to all TAP message types
-  - File-level overview with protocol explanation, features, and usage examples
-  - Organized code into logical sections with clear headers
-  - Practical usage examples for Transfer, Payment, DIDCommMessage, and Agent interfaces
-  - Complete TAIP specification cross-reference mapping
-  - Enhanced IntelliSense and documentation tooltips for better developer experience
+  - See [packages/typescript/CHANGELOG.md](packages/typescript/CHANGELOG.md) for complete details
 
 ### Changed
 - **TAIP-6 (Transaction Parties)**: Enhanced documentation to explicitly describe IVMS101 data inclusion
@@ -170,7 +109,7 @@ This changelog focuses on:
   - AuthorizationRequired is now part of the core transaction authorization protocol (TAIP-4)
   - Added optional `from` field to specify party type (customer, principal, originator) required to open URL
   - TAIP-15 now references TAIP-4 for complete AuthorizationRequired specification
-  - Updated TypeScript interface with enhanced documentation for both transaction and connection authorization
+  - Updated interface with enhanced documentation for both transaction and connection authorization
   - Added comprehensive test case example to TAIP-4
   - Updated messages.md to document AuthorizationRequired as part of authorization flow
 
@@ -184,9 +123,10 @@ This changelog focuses on:
 - **Fallback Settlement Addresses**: New optional field in Payment messages for redundancy
   - Supports array of mixed CAIP-10 and RFC 8905 addresses
   - Enables failover mechanisms for fiat payments and crypto transfers
-- **Purpose Code Types**: Added ISO 20022 External Purpose Code union types to TypeScript package
-  - ExternalPurposeCode: 331 standardized purpose codes
+- **Purpose Code Types**: Added ISO 20022 External Purpose Code union types
+  - ExternalPurposeCode: 331 standardized purpose codes  
   - ExternalCategoryPurposeCode: 48 category purpose codes
+  - See [packages/typescript/CHANGELOG.md](packages/typescript/CHANGELOG.md) for TypeScript implementation details
 - **schema.org/Organization Attributes**: Added optional organization metadata fields to Agents and Parties
   - Based on schema.org/Organization standard
   - Added fields: `name`, `url`, `logo`, `description`, `email`, `telephone`
@@ -197,14 +137,8 @@ This changelog focuses on:
   - Enhances invoice line items in TAIP-16 with richer product information
 
 ### Changed
-- **TypeScript Package (@taprsvp/types)**:
-  - Added `PayToURI` type for RFC 8905 support
-  - Created `SettlementAddress` union type (CAIP-10 | PayToURI)
-  - Updated all settlement address fields to use new union type
-  - Converted `IsoCurrency` from enum to union type for better tree-shaking
-  - Converted purpose codes from enums to union types
-  - Extended `Participant` interface with schema.org/Organization attributes
-  - Enhanced `LineItem` interface with schema.org/Product attributes
+- **TypeScript Package (@taprsvp/types)**: Updated with RFC 8905 PayTo URI support, purpose code types, and schema.org attributes
+  - See [packages/typescript/CHANGELOG.md](packages/typescript/CHANGELOG.md) for complete details
 - **JSON Schemas**:
   - Created `payto-uri.json` and `settlement-address.json` common schemas
   - Updated all message schemas to support new settlement address formats
@@ -248,7 +182,8 @@ This changelog focuses on:
   - New `Capture` message type for releasing escrowed funds
   - Supports both cryptocurrency assets and fiat currency denominations
   - Enables payment guarantees and asset swap use cases
-- TypeScript fixes: Added `by` field to Cancel interface
+- TypeScript Package: Added `by` field to Cancel interface
+  - See [packages/typescript/CHANGELOG.md](packages/typescript/CHANGELOG.md) for complete details
 
 ### Removed
 - Complete message type (replaced by extended Authorize message)

packages/typescript/CHANGELOG.md

@@ -0,0 +1,129 @@
+# @taprsvp/types Changelog
+
+All notable changes to the TypeScript package are documented in this file.
+
+## [1.10.0] - 2025-08-21
+
+### Added
+- **Enhanced Zod v4 Validation**: Comprehensive runtime validation for TAP messages
+  - New `validator` module available at `@taprsvp/types/validator` 
+  - Zod v4 schemas for all TAP message types (Transfer, Payment, Authorize, etc.)
+  - **Strict ISO Standards Validation**: Proper validation using actual ISO code sets
+    - ISO 4217 currency code validation (156 valid codes: USD, EUR, GBP, etc.)
+    - ISO 20022 purpose code validation (367 valid codes: SALA, TRAD, RENT, etc.)
+    - ISO 20022 category purpose code validation (38 valid codes)
+  - Validation functions: `validateTAPMessage()`, `parseTAPMessage()`, `isTAPMessage()`
+  - Message-specific validators for each TAP message type
+  - Full CAIP-10, CAIP-19, PayTo URI, and DID validation
+  - Comprehensive test suite with 74 test cases covering all validation scenarios
+  - Separate module path keeps validators optional for bundle size optimization
+
+## [1.9.0] - 2025-08-21
+
+### Changed
+- **Updated Connect Interface**: Restructured to support new TAIP-15 requester/principal/agents pattern
+  - Added `requester` and `principal` Party fields to Connect interface
+  - Replaced single `agent` field with required `agents` array
+  - Agents array must include at least one agent with `@id` matching DIDComm `from` field and `for` attribute set to requester DID
+  - Updated JSDoc documentation to reflect TAIP-15 specification changes
+  - Maintained backward compatibility for existing message types
+
+### Enhanced
+- **Enhanced Agent Interface**: Updated agent structure to support multi-party connections
+  - Clarified `for` attribute usage in agent definitions
+  - Updated documentation to reference TAIP-5 specification for agent details
+  - Consistent agent array patterns across Transfer, Payment, and Connect messages
+  - Updated TypeScript interfaces, JSON schemas, and test vectors to match new structure
+  - Removed `type` attributes from all agent examples across codebase for consistency with TAIP-5 specification
+
+## [1.8.0] - 2025-08-21
+
+### Added
+- **DIDComm Attachments Support**: Added full DIDComm v2.1 attachments support
+  - Added `Attachment` interface following DIDComm v2.1 specification
+  - Added optional `attachments` array to `DIDCommMessage` interface
+  - Supports inline data (base64, JSON), external links, and cryptographic integrity verification (JWS, hash)
+  - Includes comprehensive documentation with usage examples for different attachment types
+  - Enables inclusion of supplementary documents like KYC verification, receipts, and compliance documentation
+
+- **DIDComm Out-of-Band Messages**: Added support for out-of-band invitation messages
+  - Added `OutOfBandInvitation` interface extending `DIDCommMessage<OutOfBandGoal>`
+  - Added `OutOfBandGoal` interface for invitation body fields
+  - Supports QR codes, URLs, emails for sharing invitations
+  - Enables bundling initial protocol messages (like Connect requests) with invitations
+  - Compatible with TAIP-15 Agent Connection Protocol for TAP-specific connections
+
+- **Presentation Message**: Added support for verifiable credential presentations per TAIP-8
+  - Added `PresentationMessage` interface implementing DIDCommReply with empty body
+  - Requires attachments containing verifiable presentations
+  - Follows WACI Present Proof protocol v3.0 specification
+  - Enables selective disclosure for privacy-preserving identity verification
+
+- **Enhanced Message Type Support**: Expanded TAPMessage union type to include 19 message types
+  - Added PresentationMessage to support TAIP-8 selective disclosure
+  - Improved cross-reference documentation for all TAIP specifications
+
+## [1.7.0] - 2025-08-18
+
+### Added
+- **Comprehensive Documentation**: Enhanced TypeScript library with complete documentation and guides
+  - Added comprehensive README.md with installation guide, quick start examples, and complete API reference
+  - Enhanced examples with current type definitions (Person, Organization, Agent, Party)
+  - Added nameHash examples for travel rule compliance with privacy-preserving name matching
+  - Updated participant type documentation to reflect current schema.org-based interfaces
+  - Added complete participant interfaces documentation (Person, Organization, Agent, Party)
+  - Enhanced travel rule compliance examples with IVMS101 data structures
+  - Improved developer experience with detailed usage examples and standards compliance information
+
+### Fixed
+- **Payment Message Type**: Removed erroneous `defaultAddress` field from Payment interface
+  - Fixed Payment interface to comply with TAIP-14 specification
+  - Settlement addresses should be provided by agents with SettlementAddress role, not as direct fields
+  - Maintained `fallbackSettlementAddresses` field as specified in TAIP-14
+  - Updated JSDoc examples to remove invalid `defaultAddress` references
+
+## [1.6.0] - 2025-08-04
+
+### Added
+- **Comprehensive JSDoc Documentation**: Enhanced TypeScript library with comprehensive documentation
+  - Added comprehensive JSDoc documentation to all TAP message types
+  - File-level overview with protocol explanation, features, and usage examples
+  - Organized code into logical sections with clear headers
+  - Practical usage examples for Transfer, Payment, DIDCommMessage, and Agent interfaces
+  - Complete TAIP specification cross-reference mapping
+  - Enhanced IntelliSense and documentation tooltips for better developer experience
+
+### Enhanced
+- **TAIP-12 Name Hashing Implementation**: Added production-ready TypeScript implementation for privacy-preserving name matching
+  - Added `generateNameHash()` function with SHA-256 hashing using Web Crypto API and Node.js crypto fallback
+  - Added `normalizeForHashing()` function for TAIP-12 compliant name normalization (uppercase, whitespace removal)
+  - Cross-platform compatibility supporting browsers and Node.js environments without additional dependencies
+  - Comprehensive test suite with 19 test cases including TAIP-12 specification test vectors
+  - Support for non-Western names (Arabic, Chinese, Korean, Japanese scripts)
+  - Compatible with VerifyVASP and GTR networks per TAIP-12 specification
+  - Added Vitest testing framework for comprehensive validation
+
+## [1.5.0] - 2025-08-03
+
+### Changed
+- **AuthorizationRequired Message**: Enhanced interface for both transaction and connection authorization
+  - Updated TypeScript interface with enhanced documentation for both transaction and connection authorization
+  - AuthorizationRequired moved from TAIP-15 to TAIP-4 as standard authorization message
+  - Added optional `from` field to specify party type (customer, principal, originator) required to open URL
+
+## [1.4.0] - 2025-07-28
+
+### Added
+- **RFC 8905 PayTo URI Support**: Settlement addresses now support both blockchain (CAIP-10) and traditional payment systems (RFC 8905)
+  - Settlement addresses in Transfer, Authorize, Settle, Revert, and Capture messages now accept PayTo URIs
+  - Payment messages support `fallbackSettlementAddresses` field with mixed CAIP-10 and RFC 8905 addresses
+  - Enables failover mechanisms for fiat payments and crypto transfers
+
+- **Purpose Code Types**: Added ISO 20022 External Purpose Code union types
+  - ExternalPurposeCode: 331 standardized purpose codes
+  - ExternalCategoryPurposeCode: 48 category purpose codes
+
+- **schema.org Organization Attributes**: Added optional organization metadata fields to Agents and Parties
+  - Based on schema.org/Organization standard
+  - Added fields: `name`, `url`, `logo`, `description`, `email`, `telephone`
+  - Available for both Agent (TAIP-5) and Party (TAIP-6) entities