Move release manifest into lib/ to fix dependency direction
Architecture review (hai-architecture / APoSD) of the shipped redesign found one structural smell: the shared lib/ layer imported the release manifest from components/ — data in the presentation layer, dependency pointing the wrong way. - move components/release-links.generated.ts -> lib/; update the four importers and the README. lib/ no longer imports from components/. - downloads.ts: reuse PlatformDownload["id"] instead of re-declaring the union. No behavior change (download counter + tracked hrefs identical); build + e2e 12/12.
This commit is contained in:
1 parent
74e2d3fed6
commit
d833ff4776
6 files changed
+6
-6
No files matched your search
+1
-1
@@ -6,7 +6,7 @@ Next.js landing page for the AgentCompany desktop release lane.
|
||||
|
||||
| Surface | Source |
|
||||
|---|---|
|
||||
| Download cards | `landing/components/release-links.generated.ts` |
|
||||
| Download cards | `landing/lib/release-links.generated.ts` |
|
||||
| Platform FAQ | `landing/lib/platform-support.ts` |
|
||||
| Hero, How It Works, software JSON-LD features | `landing/lib/product-narrative.ts` |
|
||||
| Runtime download URLs | generated from `scripts/generate-landing-release-links.mjs` |
|
||||
|
||||
Reference in new issue
Block a user