core: placeholder regex and EXPECT_MATCHERS duplicate their Zod definitions

[Dione-b]

Summary

Two validations duplicate their canonical Zod definitions:

1. Placeholder pattern — the ${contracts.<name>.contractId} regex is defined in both contracts/placeholder-engine.ts:10 and config/validate-contract-graph.ts:5.
2. Expect matchers — EXPECT_MATCHERS (contracts/verify-expect.ts:17-27, a Set) duplicates ExpectMatcherSchema (config/config.schema.ts:32-42, a z.enum).

Why it matters

The allowed placeholder grammar and matcher list can drift between validation-time and resolve-time, and adding a matcher requires editing two files.

Suggested fix

Export the placeholder pattern from placeholder-engine.ts and import it in validate-contract-graph.ts; derive EXPECT_MATCHERS from ExpectMatcherSchema.options (or drop the set).

Priority: Low | Release impact: Patch | Breaking: No

[Juliet283]

@Juliet283 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello Maintainer, I’m a full-stack developer with the skills to take on this issue and deliver a solid solution. I’d be glad to contribute- please consider assigning it to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Juliet283 to this issue.

[pwsaragossy]

@pwsaragossy has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

The repo already has a canonical definition for both of these — a Zod schema — and then restates them by hand, so the accepted placeholder grammar can drift between validation time and resolve time, and adding a matcher means remembering to edit two files. I would export the placeholder pattern from placeholder-engine.ts and import it in validate-contract-graph.ts, and derive EXPECT_MATCHERS from ExpectMatcherSchema.options so the enum stays the single source of truth.

Relevant experience: I use Zod as the canonical contract in my own projects specifically so that runtime validation, types and derived constants cannot disagree, and deriving sets from z.enum options is a pattern I apply routinely. The change is small, but I would add a test asserting the derived matcher list matches the schema so the two can never separate again.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @pwsaragossy to this issue.

[larryjay007]

@larryjay007 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi buddy, please i would like to handle this issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @larryjay007 to this issue.

[Okorie2000-code]

@Okorie2000-code has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi Maintainer, I’ve reviewed the issue and I’m confident I can deliver a solid solution. Kindly assign it to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Okorie2000-code to this issue.

[TechBroAfrica]

@TechBroAfrica has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Focused on building trust through consistent, meaningful contributions. I approach every issue with curiosity, attention to detail, and a commitment to delivering clean, maintainable, and well-tested solutions. Driven by impact, not just commits, I value clear communication, effective collaboration with maintainers, continuous learning, and delivering meaningful value to every project I contribute to.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @TechBroAfrica to this issue.

[ThomazPassarelli]

@ThomazPassarelli has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hey! I can quickly unify placeholder regex and EXPECT_MATCHERS with their existing Zod definitions to cut down on code duplication. Ready to get this done!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @ThomazPassarelli to this issue.

[Galmanus]

@Galmanus has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

PR #189. The placeholder pattern was defined in two files and the expect matcher list duplicated the schema definition, so the two copies could drift apart and adding a matcher meant editing two places. The fix makes each one come from a single source. Covered by tests; full core suite passes.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Galmanus to this issue.

[drips-wave]

Congratulations, @ThomazPassarelli! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @ThomazPassarelli: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊