fix: Resolve marketing landing page defects after PR #505 - #514
Merged
Conversation
cursorBot
pushed a commit
that referenced
this pull request
Sep 5, 2026
Add comprehensive release readiness and business plan interface document for founder/CEO decision-making on v0.x public release vs design-partner private. Covers: - Runtime release bar (Ashlar): P0 trust holes (#513), CI redundancy (#511), cert-loop honesty (#512, #505, #506, #514), known limitations - Product release bar (Forge): scaffold status, Verify phased plan, Cursor-safe claims gate (P3 pending) - Business plan mapping: funnel stages (Aware/Eval/Embed/Design partner/Paid) with readiness per stage - Go/no-go checklist: binary decision framework for public v0.x vs design-partner private - CEO-only actions: branch protection, Pages deployment, social preview, contact channel, PAT for Forge Grounded in certification-evidence.md, SELF-EXTEND-AUDIT.md, and issue tracker. Tone: precise, founder-useful, no hype. Current recommendation: design-partner private first (runtime ready, Forge hold-mode), then CEO actions (branch protection, Pages), then public v0.x. References: #513, #512, #511, #506, #505, #514 Co-authored-by: IanFrelinger <IanFrelinger@users.noreply.github.com>
8 tasks
cursorBot
pushed a commit
that referenced
this pull request
Sep 5, 2026
Accuracy fix per user feedback: PRs #513, #512, #511, #514 are OPEN/draft, NOT merged. Updated document to reflect accurate statuses: - #513 P0 trust holes: OPEN (draft), not merged - #512 cert-loop integration: OPEN (draft), not merged - #511 CI redundancy: OPEN (ready), not merged - #514 landing honesty: OPEN (draft), not merged - Only #505, #506 confirmed merged Updated recommendations: - Changed from "GO design-partner private" to "HOLD for P0 PR merges" - Added active blockers to go/no-go checklist - Updated "What to tell prospects" to reflect P0 PRs must merge first - Path forward now: merge P0 PRs FIRST, then design-partner private This ensures document accuracy matches GitHub PR state as of 2026-09-05 23:34 UTC. Co-authored-by: IanFrelinger <IanFrelinger@users.noreply.github.com>
Problems fixed: 1. GitHub Pages asset paths - vendored brand SVGs under site/assets/ and updated all references to relative paths that work when site/ is the web root 2. SDK options accuracy - replaced invented AddAshlar options (LocalFirst, AuditTrail, CertificationRequired) with real AddAshlarClient examples 3. Audit API sample honesty - updated to match actual POST /api/copilot/task and GET /api/trust/dashboard shapes from TesterQuickstart.md 4. Brand compliance - removed gold class from Cloud pricing 'Coming soon' (gold is certification-only per BRAND.md) 5. Contact CTA - replaced dead mailto:hello@ashlar.dev with working GitHub Discussions link 6. Docs drift - updated site/README.md OG card reference to ashlar-og-flat-1200x630.png All changes keep the landing static (no build step) and working for both: - Local testing: cd site && python3 -m http.server - GitHub Pages: when /site folder is published as root Co-authored-by: IanFrelinger <IanFrelinger@users.noreply.github.com>
cursorBotforce-pushed
the
cursor/fix-landing-page-defects-b2b4
branch
from
September 5, 2026 23:59
23c4d2b to
614a7d3ComparecursorBot
pushed a commit
that referenced
this pull request
Sep 5, 2026
Add comprehensive release readiness and business plan interface document for founder/CEO decision-making on v0.x public release vs design-partner private. Covers: - Runtime release bar (Ashlar): P0 trust holes (#513), CI redundancy (#511), cert-loop honesty (#512, #505, #506, #514), known limitations - Product release bar (Forge): scaffold status, Verify phased plan, Cursor-safe claims gate (P3 pending) - Business plan mapping: funnel stages (Aware/Eval/Embed/Design partner/Paid) with readiness per stage - Go/no-go checklist: binary decision framework for public v0.x vs design-partner private - CEO-only actions: branch protection, Pages deployment, social preview, contact channel, PAT for Forge Grounded in certification-evidence.md, SELF-EXTEND-AUDIT.md, and issue tracker. Tone: precise, founder-useful, no hype. Current recommendation: design-partner private first (runtime ready, Forge hold-mode), then CEO actions (branch protection, Pages), then public v0.x. References: #513, #512, #511, #506, #505, #514 Co-authored-by: IanFrelinger <IanFrelinger@users.noreply.github.com>
cursorBot
pushed a commit
that referenced
this pull request
Sep 5, 2026
Accuracy fix per user feedback: PRs #513, #512, #511, #514 are OPEN/draft, NOT merged. Updated document to reflect accurate statuses: - #513 P0 trust holes: OPEN (draft), not merged - #512 cert-loop integration: OPEN (draft), not merged - #511 CI redundancy: OPEN (ready), not merged - #514 landing honesty: OPEN (draft), not merged - Only #505, #506 confirmed merged Updated recommendations: - Changed from "GO design-partner private" to "HOLD for P0 PR merges" - Added active blockers to go/no-go checklist - Updated "What to tell prospects" to reflect P0 PRs must merge first - Path forward now: merge P0 PRs FIRST, then design-partner private This ensures document accuracy matches GitHub PR state as of 2026-09-05 23:34 UTC. Co-authored-by: IanFrelinger <IanFrelinger@users.noreply.github.com>
Co-authored-by: IanFrelinger <IanFrelinger@users.noreply.github.com>
Uh oh!
There was an error while loading. Please reload this page.
9 tasks
cursorBot
pushed a commit
that referenced
this pull request
Sep 6, 2026
* docs: Add CEO-facing release readiness + business plan interface Add comprehensive release readiness and business plan interface document for founder/CEO decision-making on v0.x public release vs design-partner private. Covers: - Runtime release bar (Ashlar): P0 trust holes (#513), CI redundancy (#511), cert-loop honesty (#512, #505, #506, #514), known limitations - Product release bar (Forge): scaffold status, Verify phased plan, Cursor-safe claims gate (P3 pending) - Business plan mapping: funnel stages (Aware/Eval/Embed/Design partner/Paid) with readiness per stage - Go/no-go checklist: binary decision framework for public v0.x vs design-partner private - CEO-only actions: branch protection, Pages deployment, social preview, contact channel, PAT for Forge Grounded in certification-evidence.md, SELF-EXTEND-AUDIT.md, and issue tracker. Tone: precise, founder-useful, no hype. Current recommendation: design-partner private first (runtime ready, Forge hold-mode), then CEO actions (branch protection, Pages), then public v0.x. References: #513, #512, #511, #506, #505, #514 Co-authored-by: IanFrelinger <IanFrelinger@users.noreply.github.com> * fix: Correct PR statuses in release readiness doc Accuracy fix per user feedback: PRs #513, #512, #511, #514 are OPEN/draft, NOT merged. Updated document to reflect accurate statuses: - #513 P0 trust holes: OPEN (draft), not merged - #512 cert-loop integration: OPEN (draft), not merged - #511 CI redundancy: OPEN (ready), not merged - #514 landing honesty: OPEN (draft), not merged - Only #505, #506 confirmed merged Updated recommendations: - Changed from "GO design-partner private" to "HOLD for P0 PR merges" - Added active blockers to go/no-go checklist - Updated "What to tell prospects" to reflect P0 PRs must merge first - Path forward now: merge P0 PRs FIRST, then design-partner private This ensures document accuracy matches GitHub PR state as of 2026-09-05 23:34 UTC. Co-authored-by: IanFrelinger <IanFrelinger@users.noreply.github.com> * Retrigger CI checks Co-authored-by: IanFrelinger <IanFrelinger@users.noreply.github.com> --------- Co-authored-by: Cursor Agent <cursoragent@cursor.com> Co-authored-by: IanFrelinger <IanFrelinger@users.noreply.github.com>
10 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes user-facing defects in the marketing landing page at
site/index.htmlthat were introduced or present after PR #505 merged. All fixes maintain static HTML/CSS-only approach (no build step) and ensure the page works correctly when served from/siteas GitHub Pages root and for local testing.Changes
ashlar-logo-chaos.svg,ashlar-terminal-preview.svg) undersite/assets/brand/and updated all HTML references from../assets/brand/toassets/brand/so assets resolve whensite/is served as web rootAddAshlar(options => { options.LocalFirst = true; options.AuditTrail = AuditLevel.Full; options.CertificationRequired = true; })with realAddAshlarClient(baseUrl: "http://localhost:5000")examples grounded in actualAshlarHostingOptionsandServiceCollectionExtensionsauditTrailJSON to match realPOST /api/copilot/taskandGET /api/trust/dashboardshapes perdocs/TesterQuickstart.md(taskId, sourceId on trust log, not falsely precise nested structure)goldclass from Cloud pricing "Coming soon" tier (gold is certification-only perassets/brand/BRAND.md)mailto:hello@ashlar.devwith workinghttps://github.com/IanFrelinger/Ashlar/discussionslink (ashlar.dev has no DNS)site/README.mdto referenceashlar-og-flat-1200x630.pnginstead of olderashlar-social-card-1280x640.pngTesting
Static HTML verification
site/is served as rootassets/brand/ashlar-logo-chaos.svg) loads in header and faviconassets/brand/ashlar-terminal-preview.svg) loads in bento gridAsset path verification
All referenced assets exist under
site/assets/brand/.Code sample accuracy
AddAshlarClient(baseUrl)persrc/Ashlar.Client/ServiceCollectionExtensions.csCopilotTaskRequest/Responseshapes fromapplication/src/Ashlar.API/Endpoints/LocalFirst,AuditTrail,CertificationRequiredremoved)Testing strategy (blast radius)
Static documentation/marketing content only. No runtime code changes.
make kernel-coverage-gate— Not applicable (no kernel code changes)make kernel-gate— Not applicable (no kernel code changes)make test-prod-style— Not applicable (no production code changes)Checklist
make testpasses locally — N/A (static content only)site/README.mdOG card reference corrected)TODOorNotImplementedExceptionleft unresolved — N/A (no code)Release
Notes
GitHub Pages deployment readiness
After merge, the landing page will work correctly when GitHub Pages is enabled:
master→ Folder:/sitehttps://ianfrelinger.github.io/Ashlar/All asset paths are now relative to
site/as root, so images and SVGs will load correctly.Verification commands