guide: NetSuite

[walker-tx]

Closes #140

Factory draft of guides/netsuite/ via draft-guide (pipeline agents).

Updated by a factory re-run (resume) — prior research/setup on this branch were reused where the lock allowed.

Pipeline converged — ready for human review (agents never commit; this Action did).

Pipeline review (netsuite)

Outcome: Reviewers passed after 1 round(s). Still skim the open questions below before merging.

Open questions (4)

Research could not prove these from public docs. Check the boxes by replying with answers, or say “unknown / omit”. Silence + an existing hedge in the guide usually means omit / keep hedge — not a console capture.

• Oracle's current public Marketplace installation page names MCP Standard Tools but does not expose Bundle ID 522506 in its text. The ID comes from operator validation; confirm it against the authenticated SuiteApp Marketplace listing during screenshot capture.
• Oracle documents the account-ID endpoint template and the Company URLs page, but does not name a dedicated MCP URL field or give an exact text label for the account ID on that page. The Guide therefore uses the documented account ID and hostname normalization rather than claiming a copyable MCP row.
• Oracle does not publish, on the reviewed MCP setup and SuiteApp installation pages, the exact MCP Standard Tools folder path in the File Cabinet or the role-form control used to grant folder access. If File Cabinet restrictions are in use, obtain those account-specific details from the NetSuite owner.
• Oracle does not publish, on the reviewed MCP setup pages, whether this MCP endpoint exposes protected-resource metadata usable by Speakeasy discovery. The Speakeasy path therefore uses manual configuration.

Optional nits (1)

• create-oauth-integration, step 12: The required OAuth 2.0 Consent Policy choice is organization-specific, but the guide neither names who supplies it nor gives a default action when no policy has been supplied. → Tell the reader to obtain the policy choice from the application or cloud security owner, and state that they may retain the documented default of Always Ask when no different policy is required.

How to retry

1. Reply on this issue using the Decision N: … lines above (render fixes: apply / override; scope gaps: verified / drop / hedge) and answer open questions.
2. Re-add the guide:draft label. Distill reads the issue body and comments into pipeline notes.
3. If a factory draft PR already exists (guide/issue-<N>-*), the next run resumes on that branch and revises prior research/setup instead of starting blank. Late setup-file fidelity misses get one automatic salvage revise at finalization before surfacing here.

Source: run-record.json