Owner account workflows

# Owner account workflows

These tools operate on the authenticated OWNER account. They do not require a selected channel and never substitute a channel manager's credential for the account credential. Account, seller, and main profile IDs are distinct; the tools resolve their targets rather than accepting arbitrary IDs.

| User task | Tool path |
| --- | --- |
| Read or change account display nickname | [Read profile](../tools/publ_account_profile_get.md) → [save nickname](../tools/publ_account_profile_apply.md) |
| Read or change operator name and phone | [Read contact](../tools/publ_seller_contact_get.md) → [save contact form](../tools/publ_seller_contact_apply.md) |
| Inspect seller identity fields and document metadata | [Read seller information](../tools/publ_seller_information_get.md) → original human console when changes are needed |

Read the matching screen first. Copy its revision, collect all required business inputs, and use a stable requestId. `dryRun:true` plans without saving or refreshing credentials. Submit the same input with dryRun false to apply. A no-op skips mutation and refresh. Profile saves include account credential refresh; contact saves do not.

After uncertainty, retain the original task and use `account-profile` or `seller-contact` with `task_status` and `task_resume` described in the [agent guide](../agent-guide.md). Unknown saves and refreshes are not repeated. Completed replays are explicitly historical and have verification.confirmed:false; get tools supply current values. Account, owner, profile, connection, and input changes block reuse. There is no transaction, conditional server write, or automatic rollback.

Seller information reads do not expose document URLs or contents. An attachment is not approval, legal identity verification, or settlement eligibility. The returned centrally generated console link handles seller-type, identity, and document work; payments and settlement remain human actions. Profile image changes, password reset, and withdrawal also use the original account console. Never place credentials or identity documents into MCP arguments or the conversation.

The separate hosted MCP user console handles login, connection instructions, and account/channel selection. It is not a replacement publ business console. Current stdio operation still uses one private account connection; these tools do not implement hosted multi-user isolation.

[Account workflow contract](../core/account-details.md) · [Seller information contract](../core/seller-information.md) · [Runtime tool index](../runtime.md)

## Saved record identity

Existing apply/dry-run calls and task status/resume require both the saved task ID
and saved input requestId to match the requested ID. A mismatching or malformed
saved identity returns `TASK_STATE_UNVERIFIED` before workflow context or business
reads. Preserve the original record for inspection; do not rename/edit it, try
its embedded ID or create a replacement request to bypass the error. No record
is repaired or resent. Matching records retain their existing recovery and
freshness checks; this rule does not convert them into universally read-only calls.