type-c-interface-mocks: Create initial port mock structure

[RobertZ2011]

Create the initial structure for a type-C port mock that is intended to run in a no_std environment to mock hardware that isn't physically present. This will mostly be used for demonstration purposes.

[Copilot]

Pull request overview

Summary of changes

This PR introduces a new type-c-interface-mocks crate intended to provide a no_std-friendly mock implementation of per-port Type-C (Pd) and power-policy (Psu) traits. It adds a PortMock with control helpers (connect / disconnect) that broadcast Type-C and power-policy events, plus integration tests validating the emitted events and internal state updates. The crate is wired into the workspace so it can be used by other components and demos.

Changes:

• Added a new type-c-interface-mocks crate (no_std) with an initial PortMock implementation for Type-C + PSU traits.
• Added integration tests for PortMock::connect() / PortMock::disconnect() event broadcasting.
• Registered the crate in the workspace (Cargo.toml) and lockfile (Cargo.lock).

Step-by-step review guide

1. Mock port structure & public surface

   • PortMock is generic over NonBlockingSender implementations for Type-C and power-policy event streams, keeping it no_std compatible and avoiding heap use.
   • Control helpers (connect / disconnect) directly mutate stored PortStatus + PSU State, then emit a StatusChanged event and PSU attach/detach events.

2. Event semantics & state-machine alignment

   • The Type-C status event bitfields (new_power_contract_as_provider vs ..._as_consumer, sink_ready) have specific meaning and are used by the Type-C service’s power-policy integration.
   • Power-policy State has distinct transitions for attach/detach vs connect/disconnect; mocks should mirror those transitions so services under test behave realistically.

3. Workspace integration

   • The new crate is added to the workspace members and [workspace.dependencies], enabling reuse and consistent dependency resolution.

Potential issues

#	Severity	File	Description	Code
1	High	type-c-interface-mocks/src/port/mod.rs:119-130	connect() sets consumer-side status bits and updates consumer capability when PowerRole::Source; this inverts provider/consumer semantics.	set_new_power_contract_as_consumer(true)
2	High	type-c-interface-mocks/tests/connect_disconnect.rs:76-80	Source-role test asserts consumer-side status bits; it should assert provider contract bit(s).	new_power_contract_as_consumer()
3	High	type-c-interface-mocks/tests/connect_disconnect.rs:82-88	Source-role test checks consumer_capability, but source/provider flow should track requested provider capability in PSU state.	consumer_capability.map(...)
4	Medium	type-c-interface-mocks/src/port/mod.rs:281-285	Psu::disconnect() uses detach() (physical unplug) rather than disconnect(...) (commanded power disconnect), diverging from power-policy state machine behavior.	self.psu_state.detach();
5	Medium	type-c-interface-mocks/src/port/mod.rs:287-289	Psu::connect_provider() is a stub and never transitions the PSU state to ConnectedProvider.	async fn connect_provider ... { Ok(()) }
6	Low	type-c-interface-mocks/Cargo.toml:26	log feature doesn’t enable power-policy-interface/log, risking inconsistent logging backend propagation vs the defmt feature.	log = ["dep:log", ...]

Reviewed changes

Copilot reviewed 5 out of 6 changed files in this pull request and generated 6 comments.

Show a summary per file

File	Description
type-c-interface-mocks/src/lib.rs	Adds new no_std crate entry point exposing the port module.
type-c-interface-mocks/src/port/mod.rs	Introduces PortMock implementing Type-C Pd + power-policy Psu, plus connect/disconnect helpers and event emission.
type-c-interface-mocks/tests/connect_disconnect.rs	Adds integration tests validating connect/disconnect broadcasts and internal state.
type-c-interface-mocks/Cargo.toml	Defines crate deps/features (defmt/log) and dev-deps for tokio-based tests.
Cargo.toml	Registers the new crate as a workspace member and workspace dependency.
Cargo.lock	Adds the new crate entry to the lockfile.

[Copilot]

Pull request overview

Copilot reviewed 5 out of 6 changed files in this pull request and generated 2 comments.

[jerrysxie]

@RobertZ2011 Will this mock be used for testing or just demoing? which issue is tracking this effort?

[RobertZ2011]

@RobertZ2011 Will this mock be used for testing or just demoing? which issue is tracking this effort?

At the moment the intent is to use this for demoing. I also created and linked an issue for this.