Explain shadow listing behavior

[efirs]

---

Summary by Gitar

• Clarifies object listing behavior during data migration - when write-through mode is enabled, the list API returns the full contents of the shadow bucket; when disabled, only migrated objects are listed
• Documents that objects in the shadow bucket that haven't been accessed yet are not visible in list operations until they're migrated on first access
• Updates permission requirements to be conditional - write and delete permissions are only needed when write-through mode is enabled, not for all migration scenarios
• Improves documentation clarity in docs/migration/index.md by adding explicit explanation of listing behavior after the "under the hood" section

[gitar-bot]

Gitar analyzes/fixes CI failures, runs prompts as workflows and addresses comments starting with Gitar (docs)

Rules Evaluated

Gitar Rules

✅ PR Summary Enhancement: Previously applied - PR has comprehensive description with technical summary, still valid after force push

✖️ Flaky Test Auto-Retry: Previous CI failure was formatting issue (now fixed), current build is pending/passing

---

⚙️ Options:

• Auto-apply Gitar suggestions
  Allow Gitar to commit updates to this branch. When off, suggestions appear as comments.

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
docs-redirect	Ready	Preview	Comment	Nov 14, 2025 4:03am
tigris-os-docs	Ready	Preview	Comment	Nov 14, 2025 4:03am

[greptile-apps]

Greptile Overview

Greptile Summary

Added clarification about object listing behavior in migration scenarios, distinguishing between write-through enabled and disabled modes. Also updated AWS S3 permission requirements to accurately reflect that write/delete permissions are only needed when write-through mode is enabled.

• Clarified that list API behavior differs based on write-through configuration
• Updated permission requirements to be more precise about when write/delete access is needed
• Improved documentation accuracy for migration setup

Confidence Score: 5/5

• This PR is safe to merge with no identified issues
• The changes add valuable clarification to the documentation without introducing any technical errors. The listing behavior explanation is accurate and the permission requirements are now correctly scoped to the configuration mode. The writing is clear and follows existing documentation patterns.
• No files require special attention

Important Files Changed

File Analysis

Filename	Score	Overview
docs/migration/index.md	5/5	Clarified shadow bucket listing behavior for write-through vs non-write-through modes, and updated AWS permission requirements to match the actual needs based on configuration

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[gitar-bot]

CI failed for 60b8d49: CI build failed due to Prettier formatting issues in docs/migration/index.md

Issue

The CI build job failed during the npm run lint step, specifically in the lint:format phase.

Root Cause

Prettier detected code style issues in docs/migration/index.md that don't match the project's formatting standards. The file was modified in this PR but wasn't formatted according to Prettier rules before commit.

Details

[warn] docs/migration/index.md
[warn] Code style issues found in the above file. Run Prettier with --write to fix.
##[error]Process completed with exit code 1.

The lint process runs:

1. ✅ lint:apidocs - Passed
2. ✅ lint:code (eslint) - Passed
3. ❌ lint:format (prettier) - Failed on docs/migration/index.md

Suggested Fix

Run npm run lint:format -- --write or prettier --write docs/migration/index.md to automatically format the file according to project standards, then commit the formatting changes.

Reply with Gitar please fix to apply these suggestions.
_{Auto-apply is off - enable it here to let Gitar commit future updates automatically.
Did we get this right? 👍 / 👎 to help improve future analysis.}