Skip to content

feat(specterqa): add SpecterQA iOS landing page and pricing (INIT-2026-525)#50

Open
SyncTekLLC wants to merge 35 commits into
developmentfrom
feat/specterqa-ios-landing-page
Open

feat(specterqa): add SpecterQA iOS landing page and pricing (INIT-2026-525)#50
SyncTekLLC wants to merge 35 commits into
developmentfrom
feat/specterqa-ios-landing-page

Conversation

@SyncTekLLC
Copy link
Copy Markdown
Contributor

Summary

  • src/pages/products/specterqa-ios/index.astro — Full product landing page: hero with install command, 6-feature grid, quickstart steps, BYOK cost transparency table, 5-tier pricing cards, honest tradeoffs section, and footer CTA
  • src/pages/products/specterqa-ios/pricing.astro — Dedicated pricing page: 5-tier cards (Trial/Indie/Pro/Team/Enterprise), 17-row feature comparison table, 8-item FAQ (BYOK, simulator support, licensing, runs, CI/CD, annual discount, Maestro migration), structured data (JSON-LD)
  • Both pages pull data from the existing src/data/products/specterqa-ios.ts source of truth — no data duplication
  • Follows the ForgeOS pricing page pattern exactly (BaseLayout, SectionDivider, inline SVG icons, dark theme)
  • Purple accent color #BC8CFF applied consistently throughout

Pricing tiers covered

Tier Price Simulators
Trial Free 1 (3 runs/session)
Indie $29/mo 1 (unlimited runs)
Pro $99/mo ($990/yr) 4 + parallel CI
Team $299/mo ($2,990/yr) 10 + parallel CI + priority support
Enterprise Custom ($1,000+/mo) Unlimited + SLA

Test plan

  • astro build succeeds with no type errors
  • /products/specterqa-ios/ renders hero, features, pricing cards, tradeoffs
  • /products/specterqa-ios/pricing/ renders all 5 tier cards, comparison table, FAQ
  • All CTA links are correct (GitHub, mailto:sales, #pricing anchor)
  • Breadcrumb navigation works in both directions
  • "Most popular" badge displays on Pro card
  • Feature comparison table Pro column has purple highlight
  • FAQ accordions open/close correctly
  • Install command copy button functions

🤖 Generated with Claude Code

SyncTekLLC and others added 30 commits March 8, 2026 21:48
Update fallback values, fetch logic, sample JSON, and text references
to match the current ForgeOS FTI API which returns 6 dimensions
(removed governance and operational which are not yet scored).

Co-authored-by: Claude Opus 4.6 <[email protected]>
…3) (#13)

FTI API now returns all 8 dimensions (including governance and operational)
thanks to the new signal feeder pipeline. Update fallback values, sample JSON,
and text references to reflect the full 8-dimension scoring.

Co-authored-by: Claude Opus 4.6 <[email protected]>
fix: update FTI fallbacks to match signal pipeline scores
Product page showed stale 72.7 scores because Astro fetches at build time.
Added static fallback scores to forgeos.ts and composite score fallback
logic to [slug].astro so scores display correctly even when API is
unreachable during build.

Co-Authored-By: Claude Opus 4.6 <[email protected]>
fix: add FTI score fallbacks to product page
fix: update FTI fallbacks to 76.55 (INIT-2026-345)
fix: update FTI fallbacks to 78.71 (INIT-2026-345)
- Update forgeos.ts fallback scores to match live API values
- Update fti.astro fallback score from 79 to 81, operational from 70 to 86
- Update sample JSON response to show current composite (81.10)
- Replace all em dashes with regular dashes per copy style rules
- Replace decorative em dash bullets with bullet characters

Co-Authored-By: Claude Opus 4.6 <[email protected]>
fix: sync FTI scores with API (81.1) and remove em dashes
- compositeScore: 81.1 -> 82.0
- operational: 86.0 -> 92.0 (production incident filter fixed)
- documentation: 91.5 -> 91.4
- governance: 87.1 -> 87.0

Co-Authored-By: Claude Opus 4.6 <[email protected]>
fix: update FTI fallbacks to match live API (82.0)
Astro static site fetches FTI scores at build time. Without scheduled
rebuilds, scores go stale between code pushes. Adds daily 07:00 UTC
cron rebuild and manual workflow_dispatch trigger.

Co-Authored-By: Claude Opus 4.6 <[email protected]>
feat: add scheduled rebuild and manual trigger to deploy workflow
Remove hardcoded composite/dimensional score fallbacks from forgeos.ts.
Add client-side fetch script to [slug].astro that hydrates FTI card with
live API data on page load, eliminating badge/card score mismatch.
Replace em dashes with regular dashes per copy style directive.

Co-Authored-By: QualityAtlas <[email protected]>
QualityAtlas: Build clean (77 pages, 0 errors). All 5 CI checks pass. Client-side live score fetch eliminates badge/card mismatch. Stale fallbacks removed. INIT-2026-359.
update: ForgeOS logo + FTI score sync fix
style: larger ForgeOS logo on product page
From development branch (14 commits, March 6-16):
- Add CLAUDE.md governance file
- Add FTI cross-tool scoring comparison blog post
- Remove self-scoring blog post
- Disable agentic-approval GitHub Actions workflow
- FTI score updates and scheduled rebuild workflow

Conflicts resolved (all in favor of main):
- deploy.yml: retained schedule/PR triggers and development branch builds
- forgeos.ts: retained live-fetch-only FTI (no hardcoded fallback scores)
- fti.astro: retained score 82 fallbacks and client-only fetch
- [slug].astro: retained client-only FTI fetch and 120px logo size
- forge-anvil-icon.png: retained main's newer binary

Closes #39
Merge development: FTI blog post, CLAUDE.md, workflow cleanup
Merge development to main: SupportAtlas chat widget
Widget belongs in product dashboards (SiteAtlas/PolicyAtlas), not synctek.io.
INIT-2026-484 handles the proper in-app integration.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
SyncTekLLC and others added 5 commits March 27, 2026 13:30
Add HSTS, CSP, X-Frame-Options, Permissions-Policy, and COOP headers
to _headers file. Remove Astro generator meta tag.

MRP SiteAtlas INIT-2026-484 — Pillar 4 remediation.
- Fix MIT license claim on about page (ForgeOS is commercial, not MIT)
- Add registered address to privacy policy
- Remove broken ForgeOS GitHub links (repo is private)
- Update API endpoint count from 135+ to 239
- Remove specterqa-mcp from open-source page (repo doesn't exist)
- Fix blog pagination (remove non-functional pagination)
- Add /pricing redirect to ForgeOS pricing page

MRP SiteAtlas INIT-2026-484 — Pillar 1/2/5 remediation.
…tics

- Regenerate fti.json from updated fti.yaml (8 dimensions, correct pricing)
- Fix hardcoded pricing on FTI page if present
- Correct ForgeOS pricing tier features (Team/Free)
- Add Plausible analytics script
- Fix Get Started CTA to point to registration

MRP SiteAtlas INIT-2026-484 — Pillar 1/3 remediation.
… and llms.txt

Introduces specterqa-ios as a first-class product on synctek.io:
- src/data/products/specterqa-ios.ts — full product data (features, pricing, quickstart, tradeoffs)
- [slug].astro — registers specterqa-ios route and imports new data module
- llms.txt.ts — extends LLM discovery file with SpecterQA iOS section alongside ForgeOS

Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
…6-525)

- src/pages/products/specterqa-ios/index.astro: full landing page with hero,
  feature grid, quickstart steps, BYOK cost table, pricing cards (5 tiers),
  honest tradeoffs, and footer CTA
- src/pages/products/specterqa-ios/pricing.astro: detailed pricing page with
  5-tier cards, 17-row feature comparison table, and 8-item FAQ (BYOK,
  simulators, licensing, runs, CI/CD, annual discount, Maestro migration)

Both pages follow the ForgeOS pricing/layout pattern and pull data from the
existing src/data/products/specterqa-ios.ts source of truth. Purple accent
color (#BC8CFF) applied consistently. JSON-LD structured data included on
both pages for SEO.

Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
@SyncTekLLC
Copy link
Copy Markdown
Contributor Author

Thank you for your contribution, @SyncTekLLC! We appreciate you taking the time to open this (substantial change) PR.

Our team will review it shortly. In the meantime, please make sure:

  • All CI checks are passing
  • The description clearly explains the motivation and approach
  • Any related issues are linked

We aim to provide a first review within 48 hours. Thank you again for contributing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant