vibespot 1.1.1 → 1.2.0

package/LICENSE

@@ -1,33 +1,103 @@
-vibeSpot - Personal Use License
-
-Copyright (c) 2024-2026 Boris Michel. All rights reserved.
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to use,
-copy, and modify the Software for personal, non-commercial purposes only,
-subject to the following conditions:
-
-1. NON-COMMERCIAL USE ONLY. The Software may not be used, in whole or in part,
-   for any commercial purpose. Commercial purpose includes, but is not limited
-   to: selling, licensing, sublicensing, or distributing the Software or any
-   derivative work for a fee; using the Software to provide paid services;
-   incorporating the Software into a product or service that is sold or
-   offered commercially.
-
-2. NO REDISTRIBUTION FOR SALE. You may not sell, sublicense, or otherwise
-   transfer the Software or any derivative work to any third party for
-   commercial gain.
-
-3. ATTRIBUTION. Any permitted use of the Software must retain this license
-   notice, the above copyright notice, and the following attribution:
-   "Built with vibeSpot by Boris Michel."
-
-4. NO WARRANTY. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY
-   KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-   MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
-   IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
-   DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
-   OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE
-   USE OR OTHER DEALINGS IN THE SOFTWARE.
-
-For commercial licensing inquiries, contact Boris Michel.
+Functional Source License, Version 1.1, Apache 2.0 Future License
+
+Abbreviation
+
+FSL-1.1-Apache-2.0
+
+Notice
+
+Copyright 2024-2026 Boris Michel
+
+Licensed Work
+
+vibeSpot — AI-powered HubSpot CMS landing page builder
+
+Change Date
+
+2031-04-26
+
+Change License
+
+Apache License, Version 2.0
+
+Terms and Conditions
+
+Licensor:             Boris Michel
+Licensed Work:        vibeSpot
+                      The Licensed Work is copyright 2024-2026 Boris Michel.
+Change Date:          2031-04-26
+Change License:       Apache License, Version 2.0
+
+For information about alternative licensing arrangements for the Licensed Work,
+please contact Boris Michel.
+
+Notice
+
+This license is not an Open Source license. However, the Licensed Work will
+eventually be made available under an Open Source license, as stated in this
+license.
+
+License text copyright 2023 MariaDB plc, All Rights Reserved.
+"Functional Source License" is a trademark of MariaDB plc.
+
+License Grant
+
+Subject to the terms and conditions of this license, Licensor hereby grants
+you a non-exclusive, worldwide, royalty-free, non-sublicensable, non-transferable
+license to use, copy, modify, create derivative works, publicly perform, publicly
+display, and redistribute the Licensed Work and any modified versions of the
+Licensed Work, subject to the conditions in the section below titled
+"Limitations."
+
+Limitations
+
+You may not make the Licensed Work available to third parties as a hosted or
+managed service, where the service provides users with access to any substantial
+set of the features or functionality of the Licensed Work.
+
+You may not move, change, disable, or circumvent the license key functionality
+in the Licensed Work, and you may not remove or obscure any functionality in the
+Licensed Work that is protected by the license key.
+
+You may not alter, remove, or obscure any licensing, copyright, or other notices
+of Licensor in the Licensed Work. Any use of Licensor's trademarks is subject
+to applicable law.
+
+Patents
+
+Licensor grants you a license, under any patent claims Licensor can license,
+or becomes able to license, to make, have made, use, sell, offer for sale,
+import and have imported the Licensed Work, in each case subject to the
+limitations and conditions in this license. This license does not cover any
+patent claims that you cause to be infringed by modifications or additions to
+the Licensed Work. If you or your company make any written claim that the
+Licensed Work (including any additions or modifications by anyone) infringes
+or contributes to infringement of any patent, your patent license for the
+Licensed Work granted under these terms ends immediately. If your company
+makes such a claim, your patent license ends immediately for work on behalf
+of your company.
+
+Change Date and Change License
+
+On the Change Date, or the fourth anniversary of the first publicly available
+distribution of a specific version of the Licensed Work under this license,
+whichever comes first, the Licensor hereby grants you rights under the terms
+of the Change License, and the rights granted in the sections above titled
+"License Grant" and "Patents" terminate.
+
+If there is no specified Change Date and the above condition regarding the
+fourth anniversary is not met, the Change License shall be deemed to be
+the Elastic License 2.0.
+
+Disclaimer
+
+THE LICENSED WORK IS PROVIDED "AS IS". LICENSOR HEREBY DISCLAIMS ALL
+WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
+OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT.
+
+Limitation of Liability
+
+IN NO EVENT SHALL LICENSOR BE LIABLE FOR ANY CLAIM, DAMAGES, OR OTHER LIABILITY,
+WHETHER IN AN ACTION OF CONTRACT, TORT, OR OTHERWISE, ARISING FROM, OUT OF, OR
+IN CONNECTION WITH THE LICENSED WORK OR THE USE OR OTHER DEALINGS IN THE
+LICENSED WORK.

package/README.md

@@ -161,6 +161,8 @@ vibespot wizard       # Classic CLI wizard
 vibespot init         # Check and install required tools
 vibespot convert      # Convert a React project (no upload)
 vibespot upload       # Upload theme to HubSpot
+vibespot marketplace check [--fix] [--json]   # Audit theme for HubSpot Marketplace submission
+vibespot marketplace edit                     # Edit Marketplace listing metadata (marketplace.json)
 vibespot doctor       # Diagnose environment issues
 ```
 
@@ -180,6 +182,14 @@ Settings are managed in the **Settings** panel (tabbed: AI, HubSpot, Figma, GitH
 
 ## What's New
 
+### v1.1.3
+- **Model selection persists for Codex CLI, Gemini CLI, and Gemini API** — picking a non-default model used to revert because the `/api/settings/engine` route had no cases for those engines, no config fields existed, and `getCurrentModel` returned `null` (so the dropdown reset to the first option). Added the config fields, route persistence, UI lookup, and runtime `--model`/`-m` flag plumbing into the CLI subprocess invocation.
+
+### v1.1.2
+- **Honest model dropdowns** — replaced generic `opus`/`sonnet`/`haiku` aliases in the Claude Code dropdown with specific version IDs (Opus 4.7, Sonnet 4.6, Haiku 4.5, etc.) so picking a version actually pins it. Codex CLI dropdown now lists GPT-5.5, GPT-5.5 Pro, GPT-5.3 Codex, GPT-5.2 Codex, GPT-5.1 Codex Max/Mini, GPT-5.4 Mini/Nano, Codex Mini — no more outdated `o4-mini` / `o3` / `gpt-4o` only.
+- **Live model catalog covers Codex CLI** — when an OpenAI API key is configured, both OpenAI API and Codex CLI dropdowns get populated from `/v1/models` (cached 10 min). New OpenAI releases show up automatically.
+- **Settings dialog opens to AI tab** — fixed a click-handler bug that left the dialog blank on open.
+
 ### v1.1.0
 - **Plan mode** — deliberation phase before generation. Prominent toggle above chat input; AI asks elicitation questions, builds a markdown plan in a dedicated tab, only generates after Approve. Plan persists to `.vibespot/plan.md` across sessions.
 - **Streamlined Figma import** — replaces the old agentic-pipeline path with a translation pipeline that preserves Figma's exact design tokens, copy, and section order. Image assets copy into the theme automatically.
@@ -223,4 +233,4 @@ See [CHANGELOG.md](CHANGELOG.md) for the full history.
 
 ## License
 
-Personal use only — see [LICENSE](LICENSE) for details. Commercial licensing available on request.
+FSL-1.1-Apache-2.0 — see [LICENSE](LICENSE) for details.

package/assets/plan-templates/agency-services.md

@@ -0,0 +1,42 @@
+---
+id: agency-services
+label: Agency / Services
+description: Service business — drive consultation requests
+icon: users
+order: 60
+---
+
+# Agency / Services
+
+## Goal
+Convert visitors into qualified leads (consultation calls, RFPs, project inquiries).
+
+## Audience
+TBD — what kind of company / role is the buyer?
+
+## Primary CTA
+TBD — typically "Book a consultation", "Request a proposal", "Start a project".
+
+## Sections / Modules
+1. **hero** — positioning statement, who you serve, primary CTA
+2. **services** — 3–6 service offerings with short descriptions
+3. **process** — how engagements work (3–5 phases)
+4. **case-studies** — 2–4 client outcomes with metrics where possible
+5. **client-logos** — recognizable brands you've worked with
+6. **team-or-leadership** — founders or key people (skip if larger agency)
+7. **testimonials** — 2–3 detailed quotes from named clients
+8. **cta-banner** — final CTA with form or scheduling link
+9. **footer** — services, locations, legal
+
+## Brand & Tone
+TBD — confident/strategic, scrappy/founder-led, premium/boutique
+
+## Open questions
+- [ ] What is the agency / firm name, and what's the one-line positioning?
+- [ ] What kinds of clients do you serve (industry, size, stage)?
+- [ ] What are your 3–6 core service offerings?
+- [ ] What is the typical engagement model — retainer, project, hourly?
+- [ ] Do you have case studies with measurable outcomes (lift %, $ saved, etc.)?
+- [ ] Recognizable client logos — which ones to feature?
+- [ ] Primary conversion — calendar link (Calendly), form, or email-only?
+- [ ] Should the team/leadership section be prominent or low-key?

package/assets/plan-templates/blog-content-hub.md

@@ -0,0 +1,41 @@
+---
+id: blog-content-hub
+label: Blog / Content Hub
+description: Editorial home — feature posts, drive subscriptions
+icon: book-open
+order: 40
+---
+
+# Blog / Content Hub
+
+## Goal
+Surface the best content, build readership, and capture email subscriptions.
+
+## Audience
+TBD — who reads this content and what do they come for?
+
+## Primary CTA
+TBD — typically "Subscribe" or "Read latest". Secondary: "Browse by topic".
+
+## Sections / Modules
+1. **hub-hero** — featured post (large image, title, excerpt, CTA)
+2. **topic-nav** — pills or chips for browsing by category
+3. **latest-posts** — 6–9 card grid of recent posts
+4. **author-spotlight** — 1–3 contributors with bios (skip if single-author)
+5. **newsletter-signup** — email capture with value-prop copy
+6. **most-popular** — evergreen / most-read posts
+7. **categories-grid** — links into top topic landing pages
+8. **footer** — site nav, social, legal
+
+## Brand & Tone
+TBD — magazine/editorial, technical/research, conversational/personal
+
+## Open questions
+- [ ] What is the publication / blog called and what is its niche?
+- [ ] How many posts per week/month does it publish?
+- [ ] What are the top 3–5 content categories or topics?
+- [ ] Single author, small editorial team, or many contributors?
+- [ ] Is the primary conversion newsletter signup, ad views, or product upsell?
+- [ ] Do you want a featured post slot (editor pick) on the hub?
+- [ ] Any reference publications you admire (The Verge, Stratechery, Substack-style)?
+- [ ] Should categories be discoverable in the hero, secondary nav, or footer?

package/assets/plan-templates/ecommerce-product.md

@@ -0,0 +1,42 @@
+---
+id: ecommerce-product
+label: E-commerce Product Page
+description: Single product — drive add-to-cart and purchase
+icon: shopping-bag
+order: 20
+---
+
+# E-commerce Product Page
+
+## Goal
+Convert visitors into buyers for a single product (or a tightly focused product family).
+
+## Audience
+TBD — who is this product for? (lifestyle, occasion, problem solved)
+
+## Primary CTA
+TBD — typically "Add to cart" or "Buy now". Secondary: "Add to wishlist", "See size guide".
+
+## Sections / Modules
+1. **product-hero** — gallery, name, price, variants (size/color), primary CTA
+2. **product-highlights** — 3–5 benefit bullets with icons or imagery
+3. **product-details** — long-form description, materials, specs
+4. **social-proof** — average rating, review count, featured reviews
+5. **lifestyle-imagery** — large editorial shots showing product in use
+6. **size-or-fit-guide** — table or imagery (skip for non-apparel)
+7. **shipping-and-returns** — short trust block
+8. **related-products** — 3–4 cross-sell cards
+9. **footer** — store nav, support, legal
+
+## Brand & Tone
+TBD — premium/luxury, playful/colorful, minimalist/clean, etc.
+
+## Open questions
+- [ ] What is the product (name, category, one-line pitch)?
+- [ ] Does it have variants (size, color, flavor) and what are they?
+- [ ] What is the price point (or range)?
+- [ ] What are the top 3 reasons someone should buy it (vs. alternatives)?
+- [ ] Do you have product photography ready, or should we use placeholders?
+- [ ] Any social proof — rating, review count, press mentions?
+- [ ] Shipping / returns policy worth surfacing on the page?
+- [ ] Reference sites — Glossier, Allbirds, Apple, something else?

package/assets/plan-templates/event-registration.md

@@ -0,0 +1,42 @@
+---
+id: event-registration
+label: Event Registration
+description: Conference, webinar, or workshop — drive registrations
+icon: calendar
+order: 30
+---
+
+# Event Registration
+
+## Goal
+Drive ticket purchases or free registrations for a specific event.
+
+## Audience
+TBD — who is the event for? (industry, role, experience level)
+
+## Primary CTA
+TBD — typically "Register now", "Get tickets", "Save my seat".
+
+## Sections / Modules
+1. **event-hero** — countdown, event name, date, location, primary CTA
+2. **event-summary** — 2–3 sentence pitch + the value of attending
+3. **speakers** — grid with photos, names, titles, short bios
+4. **agenda** — timed schedule (single or multi-day)
+5. **sponsors** — tiered logo grid (or single block if no tiers)
+6. **venue-or-format** — location map / online platform details
+7. **ticketing** — tier comparison with "Register" CTA per tier
+8. **faq** — practical questions: refunds, accessibility, dress code, recordings
+9. **footer** — contact, legal, social
+
+## Brand & Tone
+TBD — energetic/anticipation, professional/industry-credible, intimate/community
+
+## Open questions
+- [ ] What is the event called and what's the one-line pitch?
+- [ ] When is it (date, time, time zone) and where (city/venue or online platform)?
+- [ ] Is it free or paid? If paid, what tiers and price points?
+- [ ] Who are the headline speakers (names + companies, even just 1–3 to start)?
+- [ ] What's the agenda format — single track, multi-track, multi-day?
+- [ ] Is there a registration deadline or capacity limit worth surfacing?
+- [ ] Does the event have sponsors, and how should they be tiered?
+- [ ] Any specific accessibility, refund, or COVID-style policies to call out?

package/assets/plan-templates/portfolio.md

@@ -0,0 +1,41 @@
+---
+id: portfolio
+label: Portfolio
+description: Personal or studio site — showcase work, drive contact
+icon: briefcase
+order: 50
+---
+
+# Portfolio
+
+## Goal
+Showcase work and convert visitors into project inquiries, hires, or collaborators.
+
+## Audience
+TBD — recruiters, agency clients, prospective collaborators?
+
+## Primary CTA
+TBD — typically "Get in touch", "Hire me", "Book a call".
+
+## Sections / Modules
+1. **hero** — name, role, one-line pitch, primary CTA
+2. **selected-work** — 4–8 case studies in a grid (image + title + tags)
+3. **about** — bio, photo, story / approach
+4. **services-or-skills** — what you do, listed concretely
+5. **clients-or-recognition** — logos, awards, press
+6. **testimonials** — 1–3 quotes from clients or collaborators
+7. **contact** — email + form, social links
+8. **footer** — minimal: copyright, social, return-to-top
+
+## Brand & Tone
+TBD — minimal/editorial, bold/expressive, technical/clean
+
+## Open questions
+- [ ] What's your name, role, and the one-line pitch you want at the top?
+- [ ] Solo portfolio, studio, or collective? If a studio, what's the team size?
+- [ ] Which 4–8 projects should be featured, and do you have imagery / case studies?
+- [ ] What primary action should a visitor take — email, form, calendar link?
+- [ ] Are you actively looking for work, freelance projects, or both?
+- [ ] Any awards, press mentions, or recognizable client logos to feature?
+- [ ] Reference portfolios you admire — Bruno Simon, Locomotive, plain Substack-bio style?
+- [ ] Should case studies open inline (modals) or link to dedicated detail pages?

package/assets/plan-templates/restaurant.md

@@ -0,0 +1,42 @@
+---
+id: restaurant
+label: Restaurant
+description: Single-location restaurant — drive reservations and visits
+icon: utensils
+order: 70
+---
+
+# Restaurant
+
+## Goal
+Drive reservations, takeaway orders, and walk-in visits.
+
+## Audience
+TBD — locals, tourists, special-occasion diners, lunch crowd?
+
+## Primary CTA
+TBD — "Book a table", "Order online", "View menu".
+
+## Sections / Modules
+1. **hero** — atmospheric photography, name, tagline, primary CTA
+2. **about** — story of the restaurant, chef, or concept
+3. **menu** — categories with featured dishes (skip full menu — link out)
+4. **gallery** — interior, dishes, ambience
+5. **reservations** — booking widget or instructions
+6. **reviews** — quotes from press or diners
+7. **location-and-hours** — address, map, opening hours, contact
+8. **events-or-private-dining** — optional, skip if not offered
+9. **footer** — social, newsletter, legal
+
+## Brand & Tone
+TBD — fine-dining/elegant, cozy/neighborhood, bold/trendy, casual/family
+
+## Open questions
+- [ ] What is the restaurant called, where is it, and what's the cuisine?
+- [ ] What's the one-line story or concept (chef-driven, family-run, fast-casual, etc.)?
+- [ ] Do you take reservations — and if so, via which platform (OpenTable, Resy, Tock, in-house)?
+- [ ] Is there online ordering or delivery, and via which platform?
+- [ ] Do you want a featured-dishes section or just a link to the full menu (PDF / external)?
+- [ ] Any press mentions, awards, or stars to call out?
+- [ ] Do you host private events or have a separate private-dining offering?
+- [ ] Reference vibes — Eleven Madison, Sweetgreen, In-N-Out, neighborhood bistro?

package/assets/plan-templates/saas-landing.md

@@ -0,0 +1,42 @@
+---
+id: saas-landing
+label: SaaS Landing Page
+description: Cloud product — sign-ups, demo bookings, or trial conversions
+icon: rocket
+order: 10
+---
+
+# SaaS Landing Page
+
+## Goal
+Drive sign-ups, demo bookings, or free-trial conversions for a cloud product.
+
+## Audience
+TBD — describe the target persona (industry, role, company size, key pain).
+
+## Primary CTA
+TBD — common patterns: "Start free trial", "Book a demo", "Get started free".
+
+## Sections / Modules
+1. **hero** — headline, sub-headline, primary CTA, optional product screenshot
+2. **trust-bar** — customer / partner logos
+3. **features-grid** — 3–6 product benefits with icons and short copy
+4. **how-it-works** — 3-step explainer (sign up → connect → see results)
+5. **testimonials** — 1–3 customer quotes with name, role, company
+6. **pricing-table** — 2–4 tiers with feature comparison
+7. **faq** — 4–8 Q&A covering common objections
+8. **cta-banner** — final conversion-focused CTA
+9. **footer** — links, legal, copyright
+
+## Brand & Tone
+TBD — confident/professional, playful/casual, technical/approachable?
+
+## Open questions
+- [ ] What is the product name and one-line description (pitch)?
+- [ ] Who is the primary buyer / user persona?
+- [ ] What is the single most important action a visitor should take?
+- [ ] What are the top 3 product benefits or differentiators?
+- [ ] Do you have customer logos, testimonials, or case studies ready?
+- [ ] Pricing — free + paid + enterprise, single price, or contact-sales only?
+- [ ] Are there integrations or platforms worth highlighting?
+- [ ] Any reference sites or competitors whose vibe you want to match (or avoid)?