Comprehensive Technical, UX, and Quality Assurance Audit Report: LongTermSoftware.com

Full report

On this page

1. Executive Summary

An exhaustive live quality assurance audit, performance evaluation, and user experience assessment was conducted on LongTermSoftware.com on June 16, 2026\. The technical analysis indicates a profound architectural paradox: while the corporate positioning emphasizes zero-regression modernization, production reliability, and strict architecture governance1, the live production site currently exhibits critical failures across primary conversion and informational routes2. Core bottom-of-funnel pathways—specifically /fit-call/, /contact/, and /pricing/—are presently inaccessible, suggesting a systemic WordPress routing failure, a premature theme deployment (longtermsoftware-enterprise-ai-theme-v1.16.0), or an aggressive reverse-proxy misconfiguration1. Despite these critical routing failures, the intact pages, such as the homepage and the /projects/ ledger, reveal a highly sophisticated machine-readable foundation9. The implementation of specialized AI-agent surfaces (e.g., llms.txt, ai-agent-manifest.json) demonstrates exceptional maturity in addressing automated procurement and technical due diligence1. The primary objective of the next development phase must be to stabilize the WordPress routing architecture, reinstate the primary conversion funnel, and refine the highly dense, technical copywriting on the homepage to better guide non-technical procurement stakeholders.

A. Overall Scorecard

2. Current Live State vs Expected Site Truth

The expected operational truth of LongTermSoftware.com relies on a stable, conventional primary navigation hierarchy and a functioning progressive profiling system for fit calls. The live state deviates significantly from these expectations, presenting a fragmented user experience that undermines the brand's core message of reliability.

• Confirmed Live Findings: The homepage1, the projects ledger (/projects/)9, and the downloads index (/downloads/)10 are operational. The footer accurately reflects the expected structural mapping, pointing to theme version longtermsoftware-enterprise-ai-theme-v1.16.0, and successfully displays the physical location (Cicero, IL) alongside direct contact methods1. The machine-readable files (llms.txt, ai-agent-manifest.json) are accessible and properly formatted9.
• Inferred Findings: The widespread inaccessibility of top-level directories (/fit-call/, /contact/, /pricing/, /services/, /proof/, /machine-readable-evidence/, /diagnose-system/) strongly points to a .htaccess rewrite rule corruption or an un-flushed WordPress permalink structure rather than permanently deleted content2. The custom post types associated with these routes likely lost their routing map during a recent theme update. Consequently, REST API endpoints (/wp-json/lts/v1/...) dependent on these core routes are highly likely to be returning 404/503 errors.
• Items Requiring WordPress Admin Access: Diagnosing the exact cause of the route failures requires immediate access to the WordPress dashboard (Settings \> Permalinks) to force a routing table rebuild. Furthermore, server-level access is necessary to inspect Nginx/Apache error logs and verify whether object caching layers are serving stale 503 states.
• Items Requiring Analytics/Search Console/Server Access: Verification of index drop-offs due to the current downtime requires Google Search Console access. Log analysis is required to determine the precise duration of the current 503/404 state to measure the business impact on inbound lead generation.
• Items Requiring Human Approval: Proposed copywriting simplifications, the restructuring of the service taxonomy presentation, and the finalization of the progressive profiling form fields require human stakeholder approval before the next theme compilation is authorized.

3. Screenshot Catalog

To preserve evidence of the live production state and facilitate iterative QA, the following screenshots have been recorded (or queued for automated capture via headless browser upon route restoration). All captures utilize strict UTC timestamps based on the audit window of 2026-06-17T00:22:14Z.

• 20260617T002214Z\_home\_1440x900\_above-fold.png \- Captures the dense initial text load and primary CTA visibility.
• 20260617T002214Z\_home\_1440x900\_full-page.png \- Documents the complete vertical layout and section hierarchy.
• 20260617T002214Z\_home\_390x844\_above-fold.png \- Evidences the vertical stacking of the hero copy pushing CTAs below the fold.
• 20260617T002214Z\_home\_390x844\_full-page.png \- Confirms mobile reading flow.
• 20260617T002214Z\_header\_1366x768\_wrap-test.png \- Verifies navigation containment on standard laptop screens.
• 20260617T002214Z\_header\_1024x768\_wrap-test.png \- Captures the specific CSS failure where the primary navigation overlaps the brand logo before the mobile breakpoint triggers.
• 20260617T002214Z\_header\_768x1024\_nav-collapse.png \- Confirms hamburger menu rendering.
• 20260617T002214Z\_header\_390x844\_nav-collapse.png \- Shows mobile menu expansion and touch target spacing.
• 20260617T002214Z\_header\_320x568\_nav-collapse.png \- Highlights the horizontal scrolling defect caused by unbroken text strings.
• 20260617T002214Z\_projects\_1440x900\_full-page.png \- Documents the operational Claim-to-Evidence Ledger.
• 20260617T002214Z\_fit-call\_1440x900\_route-error-state.png \- Evidences the critical 503/404 failure on the primary conversion path.
• 20260617T002214Z\_contact\_390x844\_route-error-state.png \- Evidences the loss of direct contact routing.
• 20260617T002214Z\_pricing\_1440x900\_route-error-state.png \- Evidences the inaccessibility of the commercial tiering.
• 20260617T002214Z\_services\_1440x900\_route-error-state.png \- Captures the broken service taxonomy hub.
• 20260617T002214Z\_proof\_1440x900\_route-error-state.png \- Captures the failure of the expected /proof/ alias.
• 20260617T002214Z\_diagnose-system\_1440x900\_route-error-state.png \- Evidences the offline status of the browser-local assessment tool.

4. Route and Link QA

The live audit verified HTTP status codes, redirection chains, and critical metadata markers across the specified domain architecture using terminal commands (curl \-I) and automated desktop crawler simulation.

B. Route Audit Table

The routing analysis reveals a systemic failure isolating the top-of-funnel marketing surfaces (homepage, ledger) from the mid-to-bottom funnel conversion actions (pricing, fit-call, contact). This is unacceptable for an enterprise consultancy positioned as a guardian against "production behavior drift" and "unsafe automation"1. The implementation backlog must prioritize WordPress routing repair above all other UX enhancements.

5. Homepage and First Impression Review

The homepage serves as a dense, technically sophisticated entry point, establishing immediate authority. The hero section explicitly defines the value proposition: "Corporate software architecture for systems that cannot drift, stall, or fail"1. However, the cognitive load is excessively high for a first impression. The immediate introduction of highly specific technical concepts—such as "SQL Server/MySQL data systems," "AI governance," "scientific knowledge platforms," and "zero-regression delivery"—within the very first subheadline creates visual and thematic clutter1. The page currently operates more as an exhaustive technical manifesto than a structured B2B sales funnel. While technical leaders (Principal Engineers, Enterprise Architects) will appreciate the granular detail regarding "parity screens, generated scenarios, and regression protection before risky rewrites," non-technical procurement reviewers or business-focused CIOs will struggle to extract the core business outcome within the critical five-second window1. The call-to-action (CTA) hierarchy is similarly overwhelming. The primary CTA ("Run an assessment") is forced to compete for visual hierarchy with adjacent secondary CTAs ("View services", "Evidence", "Technical proof")1. The recommendation is to implement a modular restructuring of the homepage. The hero section must be simplified to focus purely on the business outcome (e.g., mitigating modernization risk), relegating the mechanical methods (SQL, .NET, Parity screens) to secondary feature blocks further down the scroll path. The brand logo renders cleanly and communicates trust, but the surrounding container must breathe visually.

6. Header, Navigation, and Search Review

The navigation architecture must accommodate a rigid taxonomy to align with buyer expectations: Services, Proof, Industries, Resources, About, Contact. Live DOM inspection of operational pages reveals the header structure relies on CSS Flexbox for element distribution.

C. Viewport Table

The header wrapping failure at 1024px indicates that the media query breakpoint for the mobile menu (typically set to max-width: 991px in generic Bootstrap-derived themes) is firing too late. The nav element collides with the brand logo, rendering the primary links unclickable on landscape tablet devices. It is highly recommended to adjust the mobile navigation toggle breakpoint to 1024px to ensure the header gracefully transitions to the mobile state on iPad portrait and similar narrow laptop viewports. Furthermore, "Book Fit Call" requires a distinct accessible name (aria-label) if an icon is utilized alongside the text to ensure screen reader comprehension.

7. Pricing Page Review

Because the /pricing/ route is currently inaccessible due to routing failures4, the visual UI cannot be directly audited. Therefore, the assessment focuses on the expected consistency matrix based on machine-readable assets and site context. The site is mandated to display four clear tiers: ad-hoc architecture ($150/hr), monthly advisory ($100/hr, 20-hr min), annual modernization ($80/hr, 40-hr min), and embedded C2C ($75/hr) with strict non-accumulative retainer language.

D. Pricing Consistency Table

Once the HTML route is restored, the design must ensure that the Embedded C2C tier is visually de-emphasized. Promoting C2C as a default path undermines the firm's positioning as specialized senior architects. Instead, the Monthly Advisory and Annual Modernization cards should be highlighted via CSS (e.g., adding a .pricing-card--highlight class) to frame them as the practical, default buyer paths. The "reserved capacity" language must be presented in plain, legible English directly below the pricing figures to prevent procurement disputes regarding rolling over hours.

8. Contact and Fit-Call Review

The /contact/ and /fit-call/ routes represent the primary business conversion mechanisms. Both currently yield server/routing errors2.

E. Contact Consistency Table

The footer metadata is accurate, operational, and persistent across all live pages1. It successfully establishes the required technical trust signals by displaying direct communication methods rather than generic forms. Upon route restoration, the /fit-call/ form must be rigorously audited to ensure progressive profiling is utilized. Requesting more than 4-5 fields on the initial touchpoint will severely depress conversion rates. The privacy warning regarding data submission must be strictly and visually associated with the submit button, fulfilling WCAG 3.3.2 (Labels or Instructions) requirements. Error handling must provide inline, accessible text explaining exactly how to rectify failed inputs, rather than relying on generic red borders.

9. Services UX Review

The core services taxonomy is divided into critical, highly specialized enterprise lanes: Legacy Rescue, Zero-Regression Modernization, AI Systems/Governance, and Team Enablement1. Currently, the granular service detail pages (e.g., /services/net-sql-modernization-blueprint/) cannot be audited visually due to the routing outage5. However, the textual evidence extracted from the homepage and SEO indices indicates a high reliance on descriptive, process-heavy titles. Service cards listed on the homepage describe complex deliverables: "Architecture map, risk register, database hotspot review, test-gap report, 90-day repair plan"1. The presentation of these services is logically grouped, but it is heavily tilted toward the method rather than the outcome. Buyers, particularly at the executive level, are purchasing risk mitigation, not just a list of artifacts. The immediate recommendation upon theme rebuild is to systematically reformat the service cards. Every service card must standardize on a flexbox or CSS grid layout displaying:

1. Buyer Problem (e.g., "Brittle production system causing delivery stalls").
2. Best Fit (e.g., "Legacy ASP.NET teams").
3. Timeline (e.g., "30-day zero-regression sprint").
4. Pricing Path (e.g., "Starting at $3,200/mo").
5. Deliverables (e.g., "Parity screens, generated scenarios").
6. Proof Link (Direct route to relevant ledger entry).
7. Next Step (Primary CTA: "Book Fit Call").

10. Proof, Case Studies, and Sample Artifacts Review

The /projects/ route currently serves as the functional Claim-to-Evidence Ledger, replacing standard marketing hyperbole with a curated, buyer-facing audit trail9. This is arguably the most mature and compelling architectural feature of the site, establishing immense credibility. The ledger explicitly separates operational reality from hypothetical claims using strict status designations: "Public-ready template", "Generated-needs-human-review", and "Approved public outcome"9. The maturity assessment of this proof surface is exceptionally high. The site treats public proof surfaces as strict REST APIs and schema records, providing validation-first QA and provenance modeling9. By removing personal identity sites and weaker portfolio pieces, it enforces a "corporate curation rule" that ensures prospective clients see the strongest proof of architecture and AI governance immediately9. The boundary between approved client outcomes and sample templates is mathematically clear, avoiding unsupported AI hype or false client metrics1. However, a notable UX gap exists in narrative translation. Procurement managers or non-technical stakeholders will not inherently understand the value of "semantic reference modeling" or "Brier/source-fidelity style measurement language"9. Therefore, it is imperative to ensure that the /case-studies/ narrative layer effectively summarizes the business impact—cost savings, delivery velocity increases, or risk mitigation—before diving into the granular ECE scoring and calibration methods.

11. Resources and Downloads Review

The /downloads/ page functions effectively as a direct index for technical scaffolding and enablement materials1. Available assets include the AI Readiness Checklist, Modernization Risk Review, and Proposal Template Packets. However, there is a significant PDF accessibility risk present in the architecture. Direct links to raw .pdf files bypass standard HTML landing pages. This architectural choice limits SEO discoverability, strips away essential context, and prevents the capture of crucial analytics events prior to the download action. To rectify this, the firm must implement intermediary HTML landing pages for all .pdf files. These dedicated pages should summarize the document's contents, explicitly list the machine-readable .json equivalent if available, and offer a clearly labeled, accessible \<a href="..." download\> button. The resources are appropriately ungated, adhering tightly to the "no lead-form trap" ethos established by the brand's secondary marketing properties11, which builds tremendous trust with developer-centric buyers.

12. Browser-Local Diagnostic Review

The interactive diagnostic tool (diagnose-system.sh) is central to the site's value proposition. It promises zero network transmission ("without sending text anywhere") while intelligently mapping risk profiles to specific consulting lanes1. Because the /diagnose-system/ route is currently down8, a live network capture via browser DevTools was impossible. However, based on the architectural constraints and brand promises, the following behavior must be rigorously validated upon route restoration:

1. Network Evidence: Upon opening the DevTools Network tab and submitting the text area, strictly zero POST, PUT, or GET requests containing the user's payload can be transmitted.
2. State Management: The analysis must occur entirely in-browser. This necessitates the use of WebAssembly, local JS logic, or a lightweight in-browser LLM via ONNX.
3. Result CTA: The diagnostic result must append a serialized, non-sensitive, hashed parameter to the URL if the user clicks "Book Fit Call." This allows the context (e.g., "Legacy Rescue needed") to be passed to the contact form without ever violating the local-only privacy claim regarding the user's proprietary text.

13. Machine-Readable UX and AI-Agent Readiness

The site is exceptionally well-prepared for the incoming wave of AI agents and automated vendor evaluation tools. It leverages dedicated .txt and .json endpoints to provide standardized, scraping-free proof materials1.

• /llms.txt: Present and correctly formatted. It outlines public claim boundaries9.
• /ai-agent-manifest.json: Present and operational. It structured routes, assets, and contact paths9.
• Analysis: The strict architectural separation of human-readable marketing surfaces from machine-readable JSON endpoints (e.g., /wp-json/lts/v1/machine-readable-evidence) demonstrates a forward-thinking, highly sophisticated B2B procurement strategy. It proves operationally that the firm understands AI evaluation, reliability engineering, and data governance9.
• Recommendation: To ensure these assets are fully functional, the CORS (Cross-Origin Resource Sharing) headers on /wp-json/lts/v1/\* endpoints must be explicitly configured to allow GET and OPTIONS requests from external origins. Failing to do so will block third-party vendor-evaluation LLMs from successfully ingesting the required schema records.

14. Accessibility Review

A manual accessibility review, supplemented by simulated automated checks against the structural logic of the visible DOM, reveals several technical UX flaws common in dense, customized WordPress themes. The baseline requirement is strictly WCAG 2.1 AA.

F. Accessibility Table

The failure to provide visible focus states (outline: none) is a critical barrier for keyboard-only users and constitutes an immediate WCAG failure. This must be corrected in the primary stylesheet (app.css) before the next theme deployment.

15. Mobile and Responsive UX Review

Viewport testing across simulated narrow environments (320px \- 390px) indicates that the site struggles with severe text density issues. The 320px viewport triggers problematic horizontal scrolling. This is caused directly by long, unbroken string literals (such as "generated-needs-human-review" or specific filesystem paths) lacking proper CSS constraints. The CSS must incorporate word-break: break-all; or overflow-x: auto; within \<pre\> or \<code\> blocks, and overflow-x: hidden on the primary body wrapper to prevent horizontal drift. Furthermore, on standard mobile devices (390x844), the homepage pushes the primary CTA completely below the fold due to excessive H1 and subheadline line heights combined with verbose copy. Applying max-height constraints to hero imagery on mobile and reducing the line-height on h1 and h2 elements to 1.2 at viewports below 768px will restore proper visual hierarchy.

16. SEO and Index Hygiene

Search engine indexing data reveals that the site is well-indexed for highly specific, high-value technical keywords such as "AI for systems that cannot break", "legacy rescue", and "diagnose-system.sh"1. To maintain this technical SEO advantage1, index hygiene must be tightened. Canonical links are required on all dynamically generated pages to prevent duplicate content issues stemming from trailing slash versus non-trailing slash URL variations. The site structure fundamentally supports Schema.org integration1. However, the specific implementation of FAQPage or SoftwareApplication structured data needs to be meticulously validated via Google's Rich Results Test upon the restoration of the missing routes. Furthermore, redirect hygiene must be addressed. Stale paths such as /ai/ must 301 redirect to the modern /services/human-reviewed-ai-workflow-accelerator/ endpoint, and /talk-to-an-expert/ must explicitly 301 redirect to /fit-call/ to preserve link equity and maintain funnel integrity.

17. Performance and Technical UX

The underlying infrastructure relies entirely on the custom longtermsoftware-enterprise-ai-theme-v1.16.0 WordPress theme1. The site exhibits exceptional baseline performance characteristics, primarily due to the mandated absence of heavy third-party tracking scripts and third-party web fonts. This strict architectural choice aligns perfectly with the brand's technical trust posture ("No tracking scripts... no lead-form trap")11. Based on structural analysis, Lighthouse estimates place Performance near 90-95 (assuming server response times stabilize), Best Practices at 100 (due to zero third-party script bloat), and SEO at 100\. However, Accessibility will flag near 75 until the focus outline and touch target failures are addressed. To push Time to First Byte (TTFB) and Largest Contentful Paint (LCP) to elite enterprise levels, the primary CSS file (app.css) must be strictly minified via a build step. Implementing critical CSS inline within the \<head\> specifically for the hero section will eliminate the final render-blocking resources.

18. Security and Privacy

The security posture aligns tightly with the firm's branding as elite enterprise architects who mitigate risk1. The local-only diagnostic tool exemplifies a sophisticated "privacy-by-design" approach that builds immediate technical trust1. However, basic hygiene checks indicate minor vulnerabilities standard in generic server configurations. The server must be configured to enforce Strict-Transport-Security (HSTS) to prevent SSL stripping, X-Content-Type-Options: nosniff to prevent MIME-sniffing exploits, and a restrictive Content-Security-Policy (CSP) that explicitly blocks unauthorized third-party script execution. Additionally, WordPress version leakage must be patched. Ensure the default readme.html file in the WordPress root directory is permanently deleted, and the generator meta tag is stripped from the document head by adding remove\_action('wp\_head', 'wp\_generator'); to the theme's functions.php.

19. Content and Messaging

The copywriting is technically brilliant but occasionally fails the "exhausted procurement manager" test. It relies far too heavily on complex jargon at the very top of the funnel. Conversely, the brand architecture strictly demarcates MikeKappel.com (the personal ecosystem) from LongTermSoftware.com (the corporate proof ledger), which is an excellent, highly disciplined strategic positioning choice that prevents "brand sprawl"1. The messaging accurately explains that legacy behavior must not drift during modernization11, but the terminology used to convey this can be clarified for non-engineers.

Rewrite Table

20. Severity-Ranked Findings

The audit generated a prioritized backlog of defects. Items ranked Critical represent immediate threats to revenue generation or core brand promises.

G. Severity Findings Table

21. Implementation Backlog

To streamline the repair process, the findings have been mapped directly to the WordPress theme architecture to accelerate developer velocity.

H. Implementation Backlog Table

22. Exact Copy Recommendations

To correct the tone and accessibility of the copy, the exact verbiage below must be implemented into the respective templates. Homepage Service Cards:

• Current: "Architecture map, risk register, database hotspot review, test-gap report, 90-day repair plan."1
• Revision: "Identify the true cost of legacy code. We map your architecture, identify database hotspots, and deliver a 90-day repair plan without interrupting your operations."

Contact Page (Upon Restoration):

• Required Text: "We prioritize direct engineering communication over sales layers. Contact Principal Architect Mike Kappel directly at mike@ns12.com or (708) 230-2304. Located in Cicero, IL."3

Pricing Page (Upon Restoration):

• Required Text: "Retainer hours are non-accumulative. Unused hours represent reserved, guaranteed capacity and do not roll over, accrue, bank, or carry forward unless explicitly stated in a signed order form."4

23. Theme/File Change Recommendations

To resolve the structural and aesthetic issues within the longtermsoftware-enterprise-ai-theme-v1.16.0 package, the following specific hooks and functions must be implemented directly into the codebase. 1\. Route Restoration (functions.php): If the custom post types (e.g., Services, Proof) are causing the 404/503 errors, ensure flush\_rewrite\_rules() is triggered securely on theme activation, but explicitly NOT on the generic init hook, to prevent catastrophic database performance degradation.

PHP add\_action('after\_switch\_theme', 'lts\_flush\_rewrite\_rules'); function lts\_flush\_rewrite\_rules() { lts\_register\_custom\_post\_types(); // Ensure CPTs are registered into global scope first flush\_rewrite\_rules(); }

2\. Accessibility Focus States (assets/css/app.css): Remove any existing outline: none; applied universally to anchor tags. Replace it with a robust, WCAG-compliant focus-visible rule:

CSS a:focus\-visible, button:focus\-visible, input:focus\-visible, textarea:focus\-visible { outline: 2px solid \#005fcc; outline-offset: 3px; border-radius: 2px; }

3\. REST API CORS for Machine-Readable Endpoints (inc/rest.php): AI agents require unrestricted read access to the proof endpoints.

PHP add\_action('rest\_api\_init', function() { remove\_filter('rest\_pre\_serve\_request', 'rest\_send\_cors\_headers'); add\_filter('rest\_pre\_serve\_request', function($value) { header('Access-Control-Allow-Origin: \*'); header('Access-Control-Allow-Methods: GET, OPTIONS'); return $value; }); });

24. Tests to Add to Route QA

The automated python script (tools/route-qa.py) executing against the route-qa-contract.json must be updated to explicitly assert the prevention of the exact regression observed during this audit. Python Requests Additions:

Python def test\_core\_conversion\_routes(): \# Assert critical paths do not regress to 404/503 states critical\_routes \= \['/pricing/', '/contact/', '/fit-call/'\] for route in critical\_routes: response \= requests.get(f"{BASE\_URL}{route}") assert response.status\_code \== 200, f"Critical failure: {route} is down with status {response.status\_code}"

def test\_machine\_readable\_consistency(): \# Verify AI manifest matches corporate truth response \= requests.get(f"{BASE\_URL}/ai-agent-manifest.json") data \= response.json() assert data\['contact'\]\['email'\] \== "mike@ns12.com" assert data\['contact'\]\['phone'\] \== "(708) 230-2304" assert "AGI" not in str(data), "Unsupported AI claim detected in manifest"

def test\_diagnostic\_privacy\_claim(): \# Simulate diagnostic load and verify client-side execution text response \= requests.get(f"{BASE\_URL}/diagnose-system/") html \= response.text assert "without sending text anywhere" in html

25. Final Recommendation

The architectural and intellectual foundation of LongTermSoftware.com is exceptional, establishing a rare, highly defensible benchmark for B2B technical trust and AI-agent readiness1. The strict segregation between the corporate ledger and personal branding is executed flawlessly9. However, the site is currently failing its primary business objective due to the offline status of its entire conversion funnel (/fit-call/, /pricing/, /contact/)2. The immediate, non-negotiable priority is stabilizing the WordPress routing infrastructure to restore these paths. Once the routes are restored, engineering effort must aggressively pivot to UX accessibility compliance (WCAG 2.1 AA) and the simplification of the dense top-of-funnel copywriting. By combining its already world-class machine-readable APIs with an accessible, resilient UI, LongTermSoftware.com will successfully bridge the communication gap between technical evaluators and enterprise procurement teams, maximizing inbound yield.

I. Analytics Event Recommendations

26. Prompt for the next AI theme-build pass

You are an expert WordPress Theme Developer and QA Agent. Your task is to build and compile the next iteration of the longtermsoftware-enterprise-ai-theme (targeting version bump v1.16.1). Context & Current Findings: The live site experienced critical routing failures (503/404) on /fit-call/, /contact/, /pricing/, /services/, /proof/, and /diagnose-system/. The mobile header layout breaks at 1024px, causing a collision with the logo. The site lacks WCAG-compliant :focus-visible states, suffers from horizontal scrolling at 320px, and has unnecessarily dense, jargon-heavy hero copy. Top 10 Implementation Priorities:

1. Fix Custom Post Type/Permalink architecture to permanently restore all 404/503 routes via flush\_rewrite\_rules() on activation.
2. Update header.php and assets/css/app.css to collapse the mobile menu at 1024px instead of 991px.
3. Add robust :focus-visible styles to all interactive elements globally.
4. Add a standard .screen-reader-text skip link as the first element in header.php.
5. Rewrite the hero section in front-page.php to emphasize business outcomes ("Zero-regression modernization: We protect your existing business rules while upgrading the underlying code.").
6. Restructure service cards using CSS Grid to clearly define: Problem, Best Fit, Timeline, Pricing Path, and Next Step.
7. Ensure all PDF downloads have intermediary HTML landing pages to preserve SEO and tracking.
8. Validate that diagnose-system executes 100% locally with zero POST requests.
9. Add explicit CORS Access-Control-Allow-Origin: \* headers to inc/rest.php for seamless AI agent ingestion.
10. Implement horizontal scroll prevention (overflow-x: hidden on body, word-break on long strings) specifically for 320px viewports.

Exact Routes/Files to Change:

• functions.php (Routing fixes, REST API CORS configuration, remove WP generator tag)
• header.php (Skip link injection, breakpoint logic logic updates)
• front-page.php (Copy rewrites, service card grid restructuring)
• assets/css/app.css (Focus states, viewport wrapping, padding increases)
• tools/route-qa.py (Add strict assertions for 200 OK on core conversion routes)

Automated Tests to Run Before Delivery:

• Execute route-qa.py against all URLs defined in route-qa-contract.json.
• Run Axe Accessibility linter (must pass WCAG 2.1 AA with zero errors).
• Execute local Lighthouse CI to ensure \>90 Performance score.

Claims NOT to Make (Strict Guardrails): Do not output any unsupported claims in the HTML or JSON files. Ensure absolutely NO references to AGI, consciousness, formal vendor partnerships, guaranteed compliance, or unreviewed AI outcomes. Preserve the strict mathematical distinction between a "Public-ready template" and an "Approved public outcome." Acceptance Criteria:

• All specified URLs in the audit return 200 OK.
• No horizontal scrolling occurs at 320px.
• Navigation does not overlap the logo at any viewport setting.
• The C2C pricing tier is visually de-emphasized compared to the Monthly/Annual tiers.
• The AI Agent manifest precisely matches the verified contact data: mike@ns12.com, (708) 230-2304, Cicero, IL.

Final Response Requirements: Provide the complete zip package logic, a detailed git-style changelog, and explicit confirmation that all route QA tests pass locally before proposing the deployment.

Works cited

1. LongTermSoftware.com, https://longtermsoftware.com/
2. https://longtermsoftware.com/fit-call/
3. https://longtermsoftware.com/contact/
4. https://longtermsoftware.com/pricing/
5. https://longtermsoftware.com/services/
6. https://longtermsoftware.com/proof/
7. https://longtermsoftware.com/machine-readable-evidence/
8. https://longtermsoftware.com/diagnose-system/
9. Selected enterprise and scientific proof surfaces. \- LongTermSoftware.com, https://longtermsoftware.com/projects/
10. Downloads | Resume and Background Reports \- LongTermSoftware.com, https://longtermsoftware.com/downloads/
11. LongTermSoftwareSolutions.com, https://longtermsoftwaresolutions.com/