Extract reusable implementation patterns from external OSS references

[enricopiovesan]

Summary

Extract concrete implementation patterns from the checked-out external reference repos under references/open-source/ and document which patterns should be adopted, adapted, or rejected for Traverse.

Why

We now have local checkouts of Spin, Dapr, Flogo Core, and a polyglot microservices reference repo. That investigation work should be tracked explicitly so implementation decisions stay visible and reusable.

Depends on

None.

Blocked by

None.

Definition of done

• Review the checked-out reference repos in references/open-source/.
• Produce one Traverse-facing note or doc capturing reusable patterns, non-goals, and direct follow-up recommendations.
• Cover at least:
  • Spin runtime/packaging patterns
  • Dapr component and sidecar patterns
  • Flogo trigger/action composition patterns
  • any useful polyglot microservice boundary/deployment patterns
• Create follow-up tickets for concrete adoption work if needed.
• Keep the reference repos ignored and out of Traverse history.

Validation

• verify the reference repos exist under references/open-source/
• verify the extraction note is present and linked from the ticket or PR
• PR checks pass

[enricopiovesan]

Implemented locally on branch codex/issue-108-oss-patterns.

Artifacts:

• note: docs/oss-pattern-extraction.md
• follow-up tickets: Standardize local Traverse runtime home for generated binaries and adapter config #110, Template executable capability package manifests and deterministic build commands #111, Document adapter responsibilities versus core runtime responsibilities #112

Validation:

• verified the reference repos under references/open-source/
• bash scripts/ci/repository_checks.sh