Link the landing page to Tools

[asim]

Summary

• replace the landing corner's Sign up · Log in pair with Tools · Log in
• keep signup available from the login page
• add regression coverage for the two-link corner

Why

/tools is the public machine-facing catalogue but the landing page no longer linked to it. Adding it without removing anything would leave three competing links in a small corner; signup and login are two routes into the same account journey.

Validation

• re-fetched both committed blobs after writing
• focused test updated for the intended two-link navigation
• GitHub Actions provides build/test validation

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-05T10:44:09.279908Z	e9c25d6	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e9c25d6b03

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Keep Sign up visible on the landing page

For a first-time visitor arriving at /, this removes the only explicit registration action and requires them to choose “Log in” before learning they can create an account. This is a known acquisition regression: the rationale for headCorner in internal/app/app.go lines 1473–1480 records that the same one-hop design caused the instance to stop receiving signups because new visitors do not select Log in. Keep a visible Sign up action on the public front door while adding Tools rather than reintroducing that behavior.

Useful? React with 👍 / 👎.