Add optional channel attribute to contact_list type

[Copilot]

Task: Extend the contact_list type with an optional channel attribute

Plan

• Understand the existing contact-list type structure
• Add channel to ContactListRawPayload interface
• Add channel to ContactListPayload interface
• Add channel property to ContactList class
• Update deserialize method to handle the channel field
• Update serialize method to include the channel field
• Install dependencies
• Build the project to validate TypeScript compilation
• Run code review
• Run security scanning
• Revert package-lock.json format upgrade

Changes Made

• Added optional channel?: string attribute to ContactListRawPayload interface (line 99)
• Added optional channel?: ContactListRawPayload['channel'] to ContactListPayload interface (line 128)
• Added channel property to ContactList class (line 175)
• Updated deserialize method to assign this.channel = rawPayload.channel (line 218)
• Updated serialize method to include channel: this.channel in returned object (line 262)
• Reverted package-lock.json to original lockfileVersion 1 format

Validation

• ✅ TypeScript compilation successful (no errors)
• ✅ Code review passed (no issues found)
• ✅ Security scan passed (0 vulnerabilities)
• ✅ Type definitions correctly generated in dist/
• ✅ Package-lock.json reverted to original format

The implementation follows existing patterns in the codebase for optional string attributes and maintains consistency with other fields like broker, proxy_reference_id, etc.

Original prompt

Extend the contact_list type with a optional channel attribute

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

---

Summary by cubic

Added an optional channel attribute to the contact_list type to indicate the communication channel associated with a list. This is fully backward-compatible; existing lists work unchanged when channel is omitted.

^{Written for commit cd78309. Summary will update on new commits.}

[MaxAndDev]

@copilot why do we have such a big change in the package lock ?

[Copilot]

@copilot why do we have such a big change in the package lock ?

The package-lock.json was accidentally upgraded from lockfileVersion 1 to lockfileVersion 3 when I ran npm install to build the project. This is a format change that happens with newer npm versions but doesn't affect the actual dependencies. I've reverted it back to the original format in commit cd78309.

[cubic-dev-ai]

No issues found across 1 file

[charles-platform]

🎉 This PR is included in version 4.256.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀