Skip to content

docs(site): reconcile three-platform GUI availability with current release assets #26

Open

Description

@turinglambdaai

Public-site support matrix disagreement (2026-10-27)

The current public site text at https://autarx.jrtx.site/ includes both:

  • Platform table: GUI macOS, Windows/Linux GUI still developing, and CLI for macOS/Linux/Windows.
  • Later download section: macOS .dmg, Windows .msi, Linux .deb/.rpm/.AppImage GUI.

The current repository README says native GUI workbenches ship on all three desktops and lists the platforms. Latest published release v0.5.0 (2026-10-15) includes autarx-0.5.0-windows-x64.msi, macOS DMGs and Linux GUI archives/packages. A release asset alone is not native acceptance proof: qualify each target before declaring support.

Acceptance

  • Find the actual source/deployment of the product page; compare published bytes/source SHA and search cache before interpreting the discrepancy as still live.
  • Establish a single, truth-tested matrix for macOS, Windows and Linux GUI vs CLI using exact v0.5.0 release assets, installer first-launch and native acceptance evidence. Clearly label not-validated architectures/channels.
  • Update both site languages, README EN/ZH and guides to agree; remove the contradiction between “in development” and download cards. Link to release asset by correct artifact, and distinguish preview from commercial sale.
  • Product page should show one validated task (open an example ARXML and inspect, with synthetic fixture), with copyable CLI output and optional version-labelled native screenshots rather than an unexplained empty-state hero alone.
  • Verify canonical deployed URL, CTAs, mobile, light/dark, keyboard and alt; record source SHA/release evidence and rollback.

Related: portfolio documentation issue, presentation standard PR.

Starting repository SHA reviewed: turinglambdaai/autarx default branch on 2026-10-27. Do not claim platform test coverage just from the README or asset names.

Activity

  1. turinglambdaai commented on Oct 27, 2026

    @turinglambdaai
    OwnerAuthor

    Concrete fix now proposed

    PR #27 updates the no-JavaScript Chinese HTML fallback to agree with the existing two-language dictionary and current README/release asset matrix. It also localizes screenshot alt text, explicitly marks screenshot version provenance unverified, and adds a lightweight CI check for six public fallback claims. Published release v0.5.0 has relevant Windows/Linux GUI assets; this does not prove successful native acceptance. PR remains subject to CI, dual-language/no-JS and actual deployment checks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions