#66 Fix ARM64 APK workflow failure by restoring Tailwind/PostCSS compatibility

User description

The ARM64 APK GitHub Actions run failed in the Next.js build step because the CSS pipeline was using an incompatible Tailwind/PostCSS pairing. This PR realigns the frontend build toolchain so CI can compile src/app/globals.css without PostCSS plugin errors.

• Root cause addressed

  • Build was executed with Tailwind v4 behavior while the repository is configured in Tailwind v3 style (@tailwind directives + tailwind.config.ts theme extension + tailwindcss PostCSS plugin), causing Turbopack/PostCSS evaluation failure.

• Dependency alignment

  • Pin tailwindcss to ^3.4.17 in devDependencies.
  • Regenerate package-lock.json to reflect the resolved dependency graph used by CI.

• PostCSS pipeline correction

  • Keep postcss.config.mjs on the Tailwind v3 plugin entry (tailwindcss) to match the project’s CSS and config conventions.

• Illustrative config

  // postcss.config.mjs
  const config = {
    plugins: {
      tailwindcss: {},
    },
  };
  
  export default config;
  

---

Summary by cubic

Fixes the ARM64 APK GitHub Actions workflow, which failed during the Next.js build because the CSS pipeline was running with Tailwind v4 while the repo's CSS and config use the Tailwind v3 style (@tailwind directives, tailwind.config.ts, and the tailwindcss PostCSS plugin).

• Pins tailwindcss to ^3.4.17 in devDependencies.
• Regenerates package-lock.json to match the resolved dependency graph.

---

PR Type

Bug fix

---

Description

• Fixes CI build failures.

• Pins tailwindcss to compatible version.

• Resolves Tailwind/PostCSS incompatibility.

---

File Walkthrough

	Relevant files
Dependency update	package.jsonPin `tailwindcss` version for build compatibility                package.json Downgraded the tailwindcss dependency from ^4.3.3 to ^3.4.17. Ensures compatibility with the project's existing PostCSS configuration. Resolves build failures caused by an incompatible CSS pipeline. +1/-1

---