[filipagr]

Fixes from the 2026-11-11 docs audit (follow-up to FIL-1563). Each fact was checked against the product repo at origin/main 6a972b29, and each HIGH finding was re-checked against the code by hand.

HIGH

• S3 compatibility:
  • PutBucketVersioning, PutBucketObjectLockConfiguration and Get/PutBucketEncryption can't be granted to any access key in either region, per the product's key-permission grants. The docs marked them supported or accepted.
  • Retention can be extended, not shortened. The pages contradicted each other about this.
• JavaScript presigned uploads:
  • Every JS client now sets requestChecksumCalculation: "WHEN_REQUIRED". Without it, SDK v3.729+ signs a CRC32 checksum into presigned PUT URLs and uploads fail with BadDigest. The product's own S3 client sets the same option for that reason.
  • Verified locally: the default URL carries x-amz-checksum-crc32, and the fixed one doesn't.
• Billing: an Owner can Reactivate from Billing. The docs said "contact support to restore access".
• Organizations: no longer described as beta, because the beta flag was removed. Members, Billing and Audit log now sit in the sidebar's Organization group.
• Object Lock: a :::danger now sits next to the retention examples. The examples use Governance mode with a placeholder date.

MED

• Console pages updated to the current UI:
  • create-bucket (Advanced settings)
  • API keys (no Last Used, Active/Expired, details drawer, filters, bulk delete), which supersedes docs: access keys show Expired and drop Last Used (FIL-1501) #39
  • Support, Settings, Billing (Active badge, manual billing), Dashboard (Get started)
• Snippets:
  • AWS_* env vars, matching the console's Download .env
  • boto3 signature_version="s3v4"
  • Go and JS fragments compile
  • CreateBucket examples use us-east-1 clients
  • .mjs and go mod init notes
  • CLI quickstart steps connect, and nothing overwrites the default AWS profile
• Trial: one per person, on the first organization the person owns. S3 writes can continue for up to about 12 hours after the trial ends.
• Warnings: Empty bucket, bucket delete, key delete, and member removal (which revokes keys).
• Errors: a "First-request problems" troubleshooting table.
• Limits: counted per organization; the console limits and the reserved filone-rag- prefix are added.
• Overclaims: "works with any S3 app", "built-in compliance", "always recoverable", "39/39 tests".
• JSON-LD: an Offer with a price unit. The navbar says "Log in".
• Both llms*.txt mirrors: the page sections are regenerated from the pages, so they now match them word for word. Mirror-only claims are removed: "account closure does NOT purge data", FINRA/HIPAA, "deal lifecycle".

Testing

• Local S3 emulator (moto, dummy credentials, nothing sent to Fil One):
  • The SDK quickstarts (Python, JS, Go) and the CLI quickstart ran end to end.
  • Every Go snippet passes go vet, given the assumptions the page states.
• npm run build passes, and the mirror and snippet checks from ci: build, mirror and snippet checks on every PR; docs-impact checklist #40 pass on this branch.
• Not verified against real Fil One (needs credentials): exact error codes, SSE-C in us-east-1, and SigV2 acceptance. The console wasn't checked signed in, so it's unconfirmed whether the console changes merged Nov 3–10 are deployed.

Merge notes

• Merge ci: build, mirror and snippet checks on every PR; docs-impact checklist #40 first. This PR and ci: build, mirror and snippet checks on every PR; docs-impact checklist #40 both touch the mirrors' Introduction entry and the same code fence in reference/overview.mdx, so expect small conflicts.
• docs: replace AI Agent Toolkit page with an AI agent guide (FIL-1775) #44 removes the AI Agent Toolkit page, which this branch still mirrors. Whichever merges second needs that entry and section updated in both mirrors.
• docs: access keys show Expired and drop Last Used (FIL-1501) #39 is superseded by this PR.

Not changed: product and marketing issues

• Marketing claims bucket policies, IAM, and per-object proof.
• Marketing says egress is subject to "reasonable use", while the docs say no egress fees.
• The console's plan dialog says "unlimited buckets".
• The trial reminder email schedule has no sender in the product code.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
filone-docs	Ready	Preview	Nov 11, 2026 7:10pm UTC