Add FedEx WebHarbor mirror

[Lxr-max]

Summary

• Site name: FedEx
• Site slug: fedex
• Upstream URLs:
  • https://www.fedex.com/en-us/home.html
  • https://www.fedex.com/en-us/tracking.html
  • https://www.fedex.com/en-us/online/rating.html
  • https://www.fedex.com/en-us/shipping/schedule-manage-pickups.html
• Contribution type: New Website
• Contributor: XuanRui LI / Lxr-max
• Contact email: mingduanmu845@gmail.com
• Safety note: deterministic demo logistics data only; no real shipment creation, no real pickup scheduling, no real payment, no live FedEx API calls.

Implementation summary

This PR adds a self-contained FedEx-style logistics mirror under sites/fedex/ with Flask, SQLAlchemy, SQLite, Jinja templates, local CSS/JS, deterministic SVG visuals, seeded tracking timelines, rate estimates, shipment creation, pickup scheduling, invoices, claims, support content, and account flows.

Selected WebSyn port: 40015

Seed row counts

• users: 4
• service_levels: 5
• locations: 15
• pickup_slots: 45
• shipments: 60
• tracking_records: 72
• tracking_events: 360
• invoices: 60
• claims: 12
• support_articles: 18
• pickup_requests: 8
• search_logs: 3+

Benchmark users

• alice.j@test.com
• bob.c@test.com
• carol.d@test.com
• david.k@test.com
• Password: TestPass123!

Task count and categories

• 18 tasks in sites/fedex/tasks.jsonl
• Categories: single-package tracking, multi-package tracking, support/help lookup, rate estimate comparison, location search, mock shipment creation, pickup scheduling, account shipments, invoices, claims, and global search.

Key routes

• /, /home
• /track, /track/results, /tracking/<tracking_number>
• /rate-estimate
• /ship, /ship/service, /ship/review, /ship/confirmation
• /pickup
• /locations, /locations/<location_slug>
• /support, /support/<article_slug>
• /search
• /login, /register, /logout
• /account, /account/edit, /account/shipments, /invoices, /claims

Verification commands and results

• py -3 -m py_compile sites/fedex/app.py sites/fedex/seed_data.py sites/fedex/_health.py -> passed
• py -3 sites/fedex/seed_data.py -> generated deterministic instance_seed/fedex.db and local SVG assets
• local Flask test-client smoke for homepage, search, login, ship flow, pickup, invoices, and claims -> passed

Docker result

• docker build -t webharbor:fedex-pr . -> passed
• Test container: webharbor-fedex-submit
• Host ports used for verification: 8301 -> 8101, 43000-43015 -> 40000-40015
• Control plane health -> passed, all 16 registered sites alive

Smoke test result

• HTTP 200 on /, /home, /track, /track/results, /rate-estimate, /locations, /support, /search?q=delay, /login
• HTTP flows passed for login/logout, multi-number tracking, shipment creation, shipment confirmation, pickup scheduling, shipment history, invoices, claims, support search, and location search
• Example generated confirmation values after reset: shipment SH-260061, tracking FDX260000061, pickup PU-2609

Reset + MD5 result

• POST http://localhost:8301/reset/fedex -> ready: true
• docker exec webharbor-fedex-submit md5sum /opt/WebSyn/fedex/instance/fedex.db /opt/WebSyn/fedex/instance_seed/fedex.db -> both hashes matched
• MD5: ea65ea7d0ec6f17af8229806ed8c4317
• Container restart check also passed; control plane and FedEx homepage still returned healthy / 200

Screenshot paths

Local review-only screenshots were captured at:

• sites/fedex/scraped_data/submission_review/home.png
• sites/fedex/scraped_data/submission_review/track.png
• sites/fedex/scraped_data/submission_review/track_results.png
• sites/fedex/scraped_data/submission_review/tracking_detail.png
• sites/fedex/scraped_data/submission_review/rate_estimate.png
• sites/fedex/scraped_data/submission_review/locations.png
• sites/fedex/scraped_data/submission_review/support.png
• sites/fedex/scraped_data/submission_review/login.png
• sites/fedex/scraped_data/submission_review/mobile_home.png

HF asset status

• Fork asset upload succeeded:
  • https://huggingface.co/datasets/lxr-max/WebHarbor/commit/6ec4bf8fc860fb598b7bb6e450feb255aebccf73
• Upstream asset reference from hf upload --create-pr:
  • https://huggingface.co/datasets/ChilleD/WebHarbor/commit/c6d0c54e4989a8fc44208ff51573338ee35c6f66
• .assets-revision was not modified in this PR and should stay unchanged until the HF asset change is merged/pinned.

Known limitations

• Visual assets are deterministic local SVGs, not official FedEx artwork.
• No real shipment booking, pickup scheduling, claims filing, address validation, or carrier API integration.
• scripts/check_assets.sh / scripts/fetch_assets.sh use CRLF-sensitive bash entrypoints in this Windows checkout, so I followed the documented asset workflow with equivalent manual hf/tar commands in PowerShell when needed.
• Logged-in account screenshots were not captured with full browser automation; those routes were verified via real HTTP smoke instead.

Manual review notes

• The branch also updates repo-level site counts, exposed port range, and internal skill docs from 15 sites to 16 sites.
• Runtime artifacts, screenshots, local caches, and HF-managed heavy assets were intentionally left out of the git commit.
• This is a new website contribution, not a tooling-only PR.

[Susan571]

Review — Add FedEx WebHarbor mirror (#50)

Verdict: Request changes (one blocker), then Approve. The code is correct and the full
runtime suite passes once assets exist; the only blocker is the missing HF asset upload.

Mechanical

• Registration synced in all 3 places (websyn_start.sh, control_server.py,
  Dockerfile EXPOSE 40000-40015). Nice extras: CRLF-strip on entrypoint and SITE_COUNT
  parametrized readiness loop. py_compile OK.
• ❌ Blocker: ./scripts/build.sh fails at check_assets.sh —
  MISSING (required): sites/fedex/instance_seed. No fedex.tar.gz exists on
  ChilleD/WebHarbor@main and .assets-revision isn't bumped. Please generate
  instance_seed/fedex.db, pack fedex.tar.gz, upload to HF, and bump .assets-revision.
• ✅ After I generated the seed locally and built the 16-site image: all 16 sites → 200,
  /reset/fedex is byte-identical (md5 matches instance_seed), /reset-all parallel
  in ~1.1s. Seed is idempotent.

Visual fidelity: PASS

Correct FedEx purple branding, nav, and a full tracking timeline (screenshot:
fedex_track.png). Text/logo site — no product photography needed. (Live FedEx is
bot-walled, so a literal side-by-side isn't possible; IA matches the upstream tracking flow.)

Functional depth: PASS

Tracking shows the delay reason; support search resolves the exception article; /account/*
correctly 302-gate when logged out; login as alice.j@test.com works and account
shipments/invoices/claims load.

Task quality: 18/18 PASS

All entities verified present (5 tracking numbers, 4 seeded users, named locations/articles).
Tasks are genuinely multi-step (auth → account drill-down; create-shipment and
schedule-pickup are ≥5 steps) with good near-miss distractors. Task web URL :40015
matches the registered port. No answer leaks observed.

Required before approval: upload the FedEx asset tarball to HF + bump .assets-revision.