fix: set TRAVELERP_INIT_VERSION to 0 and rename Config.json for Linux compatibility

[devin-ai-integration]

Summary

Two fixes to get the TravelERP plugin working on Linux:

1. TRAVELERP_INIT_VERSION set to 0 instead of 20250101 — On first run, ProcessPatches() initializes the plugin version to TRAVELERP_INIT_VERSION and then checks if (version < 20250101). With the old value of 20250101, the condition was always false, so Patch20250101() (which creates all 7 TravelERP entities, the app, sitemap areas, and nodes) was silently skipped on every fresh database.

2. Renamed Config.json → config.json in WebVella.Erp.Site and WebVella.Erp.Site.TravelERP — The runtime code in ErpMvcExtensions.cs loads "config.json" (lowercase). On case-sensitive Linux filesystems, Config.json is not found. A previous workaround using symlinks (config.json → Config.json) caused NETSDK1022 duplicate content errors in .NET 10 SDK. Renaming the file is the clean fix.

Updates since last revision

• Rebased onto master after the TIMS → TravelERP rename (PR Rename TIMS to TravelERP across entire repository #3). The fix is identical in intent — the constant is now TRAVELERP_INIT_VERSION (was TIMS_INIT_VERSION) and the config rename applies to WebVella.Erp.Site.TravelERP (was WebVella.Erp.Site.TIMS).

Review & Testing Checklist for Human

• Existing deployments: If any production/staging database already has plugin_data for TravelERP with version 20250102, this fix alone won't re-run the skipped Patch20250101. Verify whether a DB reset or manual patch invocation is needed for those environments.
• Cross-platform impact of rename: The config.json rename affects WebVella.Erp.Site (the base site project), not just TravelERP. Confirm no other tooling, CI scripts, or .csproj content items reference Config.json with uppercase casing.
• Test fresh DB seeding end-to-end: Drop and recreate the database, run the TravelERP site, and verify all rec_tims_* entity tables are created and the app loads at http://127.0.0.1:5001.

Notes

• The .NET 10 SDK auto-includes content files, which is why the old symlink workaround broke — both Config.json and the config.json symlink were detected as separate content items.
• On Windows (case-insensitive), both the old and new filenames resolve identically, so this rename is a no-op there.

Link to Devin session: https://app.devin.ai/sessions/56e3c9458902432baa3dc3b189bf0279
Requested by: @patrickbradley-cog

---

[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: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 2 additional findings.

[devin-ai-integration]

End-to-End Test Results

Tested the TIMS Travel ERP system locally after fixing TIMS_INIT_VERSION and renaming Config.json.

TIMS App Testing (all passed)

• Login page — PASSED: Renders with IMF/PeopleSoft branding, email/password fields
• Authentication — PASSED: erp@webvella.com / erp logs in, redirects to dashboard
• TIMS dashboard — PASSED: All 6 modules visible (Missions, Travel Requests, Claims, Payments, Budgets, Approvals)
• Missions page — PASSED: Stats cards + empty list rendered
• Travel Requests page — PASSED: Stats cards + empty list rendered (via /Tims/TravelRequests)
• Claims page — PASSED: Stats cards + empty list rendered
• Payments page — PASSED: Stats cards + empty list rendered

Database Seeding Verification

All 7 TIMS entity tables confirmed created: rec_tims_mission, rec_tims_travel_request, rec_tims_claim, rec_tims_budget, rec_tims_payment, rec_tims_bank_account, rec_tims_approval. Plus 2 apps, 9 sitemap areas, 22 sitemap nodes.

Pre-existing Issue (not from this PR)

Nav bar links (e.g., /travel-requests, /claims) return "An unexpected system error occurred." The dashboard tile links (e.g., /Tims/TravelRequests) work correctly. This is a pre-existing routing mismatch unrelated to this PR.

Devin session