chore: remove static llms.txt files from git

[web3jenks]

Summary

Removes static/llms.txt, static/llms-full.txt, and static/llms-ctx.txt from git tracking and adds them to .gitignore.

These files are now managed by the generate-llmstxt workflow in the actions repo, which uploads directly to S3 after generation. No need to maintain them in git.

Note: After merging this + the S3 workflow PR (actions repo #38), the next site deploy will not include these files in the build artifact. The generate-llmstxt workflow fires automatically post-deploy and re-uploads them to S3.

🤖 Generated with Claude Code

[github-actions]

🔐 Commit Signature Verification

✅ All 1 commit(s) passed verification

Commit	Author	Signature	Key Type	Key Check
f190f7c83767	Jenks	✅	sk-ssh-ed25519	✅

Summary

• Commits verified: 1
• Signature check: ✅ All passed
• Key type enforcement: ✅ All sk-ssh-ed25519

---

Required key type: sk-ssh-ed25519 (FIDO2 hardware key)

Last verified: 2026-04-13 08:18 UTC

[greptile-apps]

Greptile Summary

This PR removes static/llms.txt, static/llms-full.txt, and static/llms-ctx.txt from git and adds them to .gitignore, since they are now managed by the generate-llmstxt workflow in the actions repo (PR #38) which uploads directly to S3 after each deploy. The existing LlmCopyButton.tsx component fetches /llms.txt at runtime via a client-side fetch, and robots.txt already allows crawling of these paths — both will continue to work once the S3 workflow is active, as the URLs remain unchanged.

Confidence Score: 5/5

Safe to merge; the change is a clean housekeeping operation with no logic changes and the PR description clearly documents the deployment sequencing dependency.

All four changed files are either deleted content or a .gitignore addition with no logic impact. The only runtime concern (a brief gap where /llms.txt 404s between deploy and the S3 re-upload) is acknowledged in the PR description and handled gracefully by LlmCopyButton.tsx's error state.

No files require special attention.

Important Files Changed

Filename	Overview
.gitignore	Adds gitignore entries for static/llms.txt, static/llms-full.txt, and static/llms-ctx.txt with a clear comment explaining they are managed by the S3 workflow.
static/llms.txt	Deleted from git tracking; will now be generated and uploaded to S3 by the generate-llmstxt workflow in the actions repo.
static/llms-full.txt	Deleted from git tracking; to be managed by the S3 workflow post-deploy.
static/llms-ctx.txt	Deleted from git tracking; to be managed by the S3 workflow post-deploy.

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant GH as GitHub (this repo)
    participant CI as CI/CD (actions repo)
    participant S3 as AWS S3
    participant Site as Live Site

    Dev->>GH: Push to main (this PR)
    GH->>CI: Trigger deploy workflow
    CI->>CI: npm run build (llms files NOT in artifact)
    CI->>S3: Upload build artifact
    S3->>Site: Serve static site (no llms files yet)
    CI->>CI: Trigger generate-llmstxt workflow (post-deploy)
    CI->>CI: Generate llms.txt / llms-full.txt / llms-ctx.txt
    CI->>S3: Upload llms files directly to S3
    S3->>Site: Serve llms files at /llms.txt etc.
    Note over Site: LlmCopyButton fetches /llms.txt at runtime — works once S3 upload completes

Loading

_{Reviews (1): Last reviewed commit: "chore: remove static llms.txt files from..." | Re-trigger Greptile}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f190f7c837

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Keep llms assets in this repo’s build output

By ignoring and deleting static/llms*.txt, this repo’s npm run build output no longer contains /llms.txt, but the UI still requests it (src/components/LlmCopyButton.tsx, fetch to /llms.txt). I checked .github/workflows/gh-pages.yml, and this pipeline only builds and uploads the tarball from build/ with no in-repo regeneration step, so any environment that deploys this artifact without the external post-deploy uploader will serve 404s and break the copy action. Please keep a fallback in-repo generation/source file path or add generation to this repository’s build workflow.

Useful? React with 👍 / 👎.

[kkkk666]

look good
Let's run it in the dev environment right now.