[08abhinav]

Which issue does this PR address?

Closes #4699

Rationale

The Rust, Node, Java and C# examples show the message envelope pattern, but the PHP examples only had getting-started and basic. This adds the missing example without any new PHP SDK calls (parity work is tracked in #3302).

What changed?

The PHP examples had no demonstration of sending several message kinds through one topic. This adds examples/php/message-envelope/producer.php and consumer.php, which wrap each order payload (OrderCreated, OrderConfirmed, OrderRejected, taken from the Node example) in a message_type + payload JSON envelope. The consumer dispatches on message_type with match, and logs and skips unknown or malformed messages. A "Message Envelopes" section is added to examples/php/README.md.

Local Execution

• Passed (built the extension with cargo build in foreign/php, started a fresh server, ran producer then consumer: 6 messages handled, 2 of each type)
• Also tested the unknown-type and malformed-message paths by temporarily adding a made-up message_type and a non-JSON payload; both were logged and skipped
• Pre-commit hooks ran (prek)

AI Usage

AI was used to assist with repository exploration, implementation, and documentation.

• Development assistance: Reviewed existing PHP and Rust examples while implementing the producer.
• I reviewed the changes and can explain the implementation and its design decisions.

[github-actions]

Thanks for the PR. It is labeled S-waiting-on-review and queued for review.

If AI was used to create this PR, you must run the team-review skill before opening it.

Slash commands (own line, regular comment) move it around the queue:

• /ready - back to S-waiting-on-review after addressing feedback
• /author - flip to S-waiting-on-author while you finish changes
• /request-review @user-or-team - request a reviewer
• /pin - exempt the PR from the stale bot, /unpin to undo

See CONTRIBUTING.md for details.

[justinmclean]

Thanks @08abhinav. The PR Title and Pre-merge checks never started on your first push, so they show as waiting. Could you push again, rebased on the latest master or as an empty commit (git commit --allow-empty -m "ci: rerun checks"), so they run?

[hubcio]

please address the issues below.

[hubcio]

no findings in the reviewed changes.