guide: Box

[walker-tx]

Closes #145

Factory research-only pause for guides/box/ — material open questions need Decisions before draft.

Pipeline status: awaiting scope. See the issue comment Scope check.
Answer with Decision N: …, then re-add guide:draft to continue.

This PR is a draft until the issue Decisions / blockers are settled.

Scope check (box)

Research finished with material open questions that change what the guide should document. Drafting is paused until you answer — then re-add guide:draft.

Decisions needed (1)

1. Box documents two conflicting configuration surfaces and save orders: Configuration > Add Integration Credentials versus Additional Configuration > + Add Integration Credentials followed by an earlier credential-name Save.

• Why this blocks draft: Conflicting or mutually exclusive setup paths — pick one before drafting.

Reply with one of:

• Decision 1: verified — … (paste exact labels / path to document)
• Decision 1: drop this branch (omit the recovery/optional path)
• Decision 1: hedge — … (keep a soft line; do not invent chrome)

Soft open questions (17) — no pause

These stay as dossier hedges / conditionals. No reply required to continue.

• Box does not publish the exact Access scopes checkbox labels or their mapping to root_readwrite, ai.readwrite, and docgen.readwrite.
• Box does not state whether Access scopes remain editable after reopening a saved credential entry.
• Box does not identify the pre-filled Redirect URI value that its setup flow tells administrators to change.
• Box does not state whether the Client Secret remains viewable after credential creation.
• Box does not state whether Custom Box MCP Server requires a separate availability-state change; its documented custom-credential flow contains none.
• Except for four sharing tools documented as off by default, Box does not publish each tool category's default enablement state.
• Box does not state whether changing the row-level Enablement control requires a separate Save.
• Box does not document how the Box AI APIs setting appears on Business, Business Plus, or Enterprise plans when Box AI Units have not been purchased.
• Configuration surface labels and save order. docs.box.com's
• Exact Access-scopes checkbox labels. docs.box.com names the
• Whether a saved entry's Access scopes are editable on re-open.
• Pre-filled Redirect URI value. Step 4 says to "change the Box
• Client Secret revisibility. No documentation states whether the
• **Whether the Custom Box MCP Server integration needs its own
• Default tool-enablement state per category. Beyond the four
• Whether an Enablement-control change needs its own Save.
• Box AI APIs setting appearance without purchased Units. On

How to continue

1. Reply on this issue using the Decision N: … lines above.
2. Re-add the guide:draft label. Distill folds your replies into pipeline notes.
3. The next run resumes on the factory branch, revises research if needed, then drafts.

Source: run-record.json