fix(landing): fill the Codex Plugin mega-menu column and adopt the dsh one-line installer

[joeylee12629-star]

Why

Live content defects on open-design.ai, plus an owner-reviewed nav/content redesign that landed during review:

1. The product mega menu's first column rendered as a blank panel (head link only).
2. The DeepSeek Harness agent guide taught the manual npm install -g path requiring a preinstalled Node.js toolchain, while the published one-line installers (open-design.ai/install-dsh.{sh,ps1,cmd} — verified live) replace that flow.
3. The guide led with a "does DeepSeek Harness have a GUI" angle that is off the page's actual message (designing with DeepSeek Harness through OpenDesign).

What users will see

• Product mega menu (final design, owner-reviewed): the first column is the localized Feature category (new header i18n key across all 18 locales) with Codex Plugin as its entry. The interim link-list variant from the first commit was superseded by the reviewed design mock. In the Agent column, DeepSeek Harness moves to the top with a red new-dot.
• DeepSeek Harness guide, all 11 active locales: Step 1 teaches the three per-OS one-line install commands (no preinstalled Node.js/pnpm/dsh, no sudo, isolated user-directory toolchain pinned to the verified release), the installer-behavior list, updated Web UI step and credential note, reworked install FAQ plus two new installer FAQs.
• Guide refocus: design-first title/description in all active locales; the GUI section, its TOC entry and FAQ removed. A #gui compatibility anchor stays aliased to the setup section so saved/search-indexed deep links keep landing on content.
• SEO: HowTo structured data generated from the real five-step walkthrough joins the existing Breadcrumb/WebPage/ItemList/FAQPage blocks.

Surface area

• Web UI (landing header + agent guide + structured data)
• i18n content (header feature key in 18 locales; guide copy in 11 active locales; retired locales untouched)
• Tests (content guard now requires the three installer URLs and rejects the manual npm path; title anchor tracks the new intent)

How to verify

• pnpm --filter @open-design/landing-page test — 147/147 pass; typecheck clean.
• Preview: https://pr-7139.open-design-landing-staging.pages.dev/zh/ (hover 产品) and /zh/agents/deepseek-harness-design/.

Bug fix verification

• Installer content: the reworked guard in tests/deepseek-harness-cta.test.ts is the red spec — its new assertions (all three open-design.ai/install-dsh.* commands present, manual npm install -g @deepseek-ai/dsh rejected, design-first title anchor) fail on main's guide content and pass on this branch (147/147 locally; Validate landing page green on this head).
• Blank Feature column: no rendered-header harness exists in this suite, so verification is visual — the PR preview (https://pr-7139.open-design-landing-staging.pages.dev/zh/) shows the populated Feature column and the DeepSeek Harness red-dot entry; before/after covered in the review discussion. A rendered-header regression harness is noted as a follow-up.
• #gui deep links: on this head the built guide page carries the span#gui alias inside the setup section (checked in the built HTML); on main the id only exists on the removed GUI section.

[lefarcen]

Thanks for tightening the landing-page copy and the installer path here.

One PR-body follow-up before pool review: please add the new template info for Surface area and Bug fix verification. The current How to verify section already covers Validation, so this is just about checking the relevant surface boxes and briefly stating how you confirmed the two regressions were fixed (the blank mega-menu column and the old manual dsh install flow).

[nettee]

@joeylee12629-star The landing-page typecheck is clean, but this head has two blocking regressions: the final Product menu no longer contains the three destinations promised in the PR description, and the existing landing-page test suite fails against the new DeepSeek setup copy. I’ve left concrete fixes inline below.

_{🔁 Powered by Looper · runner=reviewer · agent=codex · An autonomous AI dev team for your GitHub repos.}

[lefarcen]

@joeylee12629-star The current blockers are already covered clearly in @nettee's review: restore the three Product-menu destinations promised in the PR body, and update the landing-page tests so they match the new DeepSeek installer flow and copy. Once those two items are fixed — plus the PR-body Surface area / Bug fix verification fields from my earlier note — the next pass should be straightforward.

💡 To drive this PR to merge hands-free, paste this to your AI coding agent (Claude Code / Codex / opencode / Cursor …):
Take over nexu-io/open-design#7139 until it merges — read https://raw.githubusercontent.com/nexu-io/looper/main/skills/pr-takeover/SKILL.md and follow it.

[nettee]

@joeylee12629-star I verified the current head with all 147 landing-page tests passing, Astro typecheck reporting zero errors, and the full static build completing successfully. The installer guide rollout is covered across the active locales, but one blocking Product-menu regression remains in the changed header range; the inline comment below identifies the missing destinations and fix.

_{🔁 Powered by Looper · runner=reviewer · agent=codex · An autonomous AI dev team for your GitHub repos.}

[github-actions]

🚀 Landing page preview

This PR is deployed to a Cloudflare Pages preview — not staging or production:

• Stable alias: https://pr-7139.open-design-landing-staging.pages.dev
• This build: https://8e6869c6.open-design-landing-staging.pages.dev
  Updated for commit a0cc776.

[lefarcen]

@joeylee12629-star Quick status update: the test/build regressions from the earlier pass look resolved now, so the remaining blocker is the single Product → Feature menu gap called out in @nettee's latest review — restoring the three missing destinations plus a regression assertion for that href set. After that, please also fill in the PR-body Surface area and Bug fix verification fields from my earlier note so the template is complete.

[nettee]

@joeylee12629-star I reviewed all 15 changed landing-page files and rendered the current static output. The installer rollout is localized across the active locales, and the landing tests, Astro typecheck, and a clean static build pass. I found one blocking menu regression plus one public-anchor compatibility regression in the changed ranges; the concrete fixes are inline. Thanks for the thorough installer documentation work — once these entry-point regressions are addressed, the rest of the rollout looks cohesive.

_{🔁 Powered by Looper · runner=reviewer · agent=codex · An autonomous AI dev team for your GitHub repos.}

[lefarcen]

@joeylee12629-star Quick update: the current blockers have shifted again in @nettee's latest review. The test/build side looks good now, but there are still two remaining entry-point regressions to address on this head: restoring the missing Product → Feature destinations, and keeping a compatibility anchor for the old #gui deep link so existing links still land correctly. After those are fixed, please also fill in the PR-body Surface area and Bug fix verification fields from my earlier note so the template is complete.

[lefarcen]

@joeylee12629-star Thanks for the clarification on the owner-reviewed Feature-column design, and for adding the #gui compatibility anchor on the current head. I’ve re-requested @nettee for a fresh pass on 6a9ee3751fd781fc5ae0fd5699f5b98a1219bb09 since those were the two blockers from the prior review state. From my earlier template note, the remaining PR-body follow-up is just Bug fix verification — the new Surface area section is in place now.

[nettee]

I found one blocking issue in the new HowTo structured data: the five emitted steps contain only headings and anchors, not the instructional content the markup is meant to describe. The exact omission and a concrete fix are anchored inline below.

_{🔁 Powered by Looper · runner=reviewer · agent=codex · An autonomous AI dev team for your GitHub repos.}

[lefarcen]

@joeylee12629-star Thanks for the quick follow-up on the latest structured-data blocker. The current head now includes the HowToStep.text field that @nettee called out, and @nettee is still requested for the fresh pass on a0cc776c8f2268bb204dffa02ac3cd926d6c2e51. From my earlier template note, the remaining PR-body follow-up is now just Surface area — the Bug fix verification section is in place.

[nettee]

@joeylee12629-star I reviewed the complete changed range for the landing header and DeepSeek Harness guide, including all 11 active locale outputs, the compatibility anchor, and the generated HowTo JSON-LD. The landing-page test suite (147/147), Astro typecheck (0 errors), static build, and current landing-page CI validation pass on a0cc776. The Feature/Codex Plugin menu entry and DeepSeek Harness red-dot highlight render as intended. Thanks for the careful follow-up work across the localized content and verification paths—this is a thoughtful, cohesive fix.

_{🔁 Powered by Looper · runner=reviewer · agent=codex · An autonomous AI dev team for your GitHub repos.}