Add Oracle Forms modernization workshop (modules, event, unified track)

[devin-ai-integration]

Summary

Adds a complete Oracle Forms modernization track to the workshop-metadata repo, paralleling the existing COBOL track. Changes span four areas:

New files:

• events/oracle-forms-modernization-workshop/README.md — standalone 4-lab event guide for Oracle Forms audiences
• modules/migration-modernization/oracle-forms-system-understanding.md — Lab 1 module
• modules/migration-modernization/oracle-forms-migration-planning.md — Lab 2 module
• modules/migration-modernization/oracle-forms-to-java.md — Lab 4 module

Updated files:

• workshops/legacy-modernization/README.md — restructured from COBOL-only to dual-track (Track A: COBOL, Track B: Oracle Forms) with a track selection table and updated duration variants
• catalog/repos.md — added entries for ts-plsql-oracle-forms-legacy-codebase (ts- section), uc-legacy-modernization-oracle-forms-to-java (uc- section), and cluster C12
• modules/migration-modernization/README.md — added 3 Oracle Forms modules to the module table and 2 repos to the repository cross-reference table; added event/workshop links

The two underlying repos (ts-plsql-oracle-forms-legacy-codebase and uc-legacy-modernization-oracle-forms-to-java) were pushed to the org separately.

Review & Testing Checklist for Human

• Verify both repos exist and match descriptions — Open ts-plsql-oracle-forms-legacy-codebase and uc-legacy-modernization-oracle-forms-to-java. Confirm they contain the artifacts referenced in the modules (PL/SQL packages like PKG_EMPLOYEE, Forms XML exports, test-harness directory, java-target directory, etc.)
• Check all relative links resolve — The new files reference each other extensively (../../modules/..., ../../events/...). Spot-check that links in the catalog entries, event README, and module files all point to files that exist on main (or will exist once this merges)
• Review COBOL track for regressions — The unified workshop README was restructured: labs renamed from "Lab 1–4" to "Lab A1–A4", and per-lab Repository: / Duration: lines were removed (repo info moved to track header). Confirm nothing important was lost and existing references to the COBOL workshop still work
• Domain review of Oracle Forms technical content — The module prompts, "What to Try" sections, and Key Takeaways reference specific Oracle Forms constructs (PLL libraries, LOVs, tab canvases, Forms triggers, CONNECT BY queries). Verify these are accurate and realistic for a workshop audience
• Walk through the Lab B1→B4 arc — Read the Oracle Forms event README end-to-end and confirm the progressive narrative (Understand → Plan → Safeguard → Execute) is coherent and each lab's outputs feed the next

Notes

• Oracle Forms modules reuse the migration-test-harness.md module for Lab B3 (same as COBOL Lab A3) rather than creating a separate Oracle-specific test harness module. This is intentional — the test harness methodology is platform-agnostic.
• No CI exists in this repo to validate markdown links or formatting, so link integrity must be verified manually.
• The COBOL track content is functionally unchanged — restructuring is limited to renaming and reorganization, not content edits.

Link to Devin session: https://partner-workshops.devinenterprise.com/sessions/6abcc66c28ee405c86876cb33da2f3a9
Requested by: @bsmitches

---

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[devin-ai-integration]

Devin Review found 1 potential issue.

View 5 additional findings in Devin Review.

[devin-ai-integration]

🔴 Cluster ID C12 collision: Oracle Forms reuses ID already assigned to .NET/Angular Containerized Decomposition

The PR assigns cluster C12 to the new Oracle Forms HRMS repos (ts-plsql-oracle-forms-legacy-codebase, uc-legacy-modernization-oracle-forms-to-java), but C12 is already defined in catalog/upstream-map.yaml:178 as ".NET/Angular Containerized Decomposition" and used by four existing repos in catalog/repos.md:361-394 (app_dotnet_angular_containerized_decomposition_*). This means two completely different repo clusters share the same identifier, breaking the uniqueness invariant of the cluster system. Anyone looking up "C12" will get ambiguous results. The new Oracle Forms cluster should use C13.

Prompt for agents

The new Oracle Forms cluster was assigned C12, but C12 is already taken by .NET/Angular Containerized Decomposition (defined in catalog/upstream-map.yaml:178 and used by repos at catalog/repos.md:361-394). This needs to be changed to C13 in three places:

1. catalog/repos.md line 37: Change C12 to C13 in the cluster table row for Oracle Forms HRMS Modernization
2. catalog/repos.md line 62: Change C12 to C13 in the uc-legacy-modernization-oracle-forms-to-java entry
3. catalog/repos.md line 215: Change C12 to C13 in the ts-plsql-oracle-forms-legacy-codebase entry

Also add the new C13 cluster definition and the two new repo entries to catalog/upstream-map.yaml (see the WHEN TO UPDATE THIS FILE section in that file).

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[devin-ai-integration]

The cluster ID collision flagged by Devin Review (C12 already taken by .NET/Angular Containerized Decomposition) has been fixed in #39 — renamed the Oracle Forms cluster to C13 across all references in repos.md and added the C13 definition + per-repo entries to upstream-map.yaml.