dsh-hunyuan-3d

In-app configuration

The plugin registers a settings card under Settings → Plugins → Configurable ("腾讯云混元生3D"). It edits the plugin's hunyuan-3d settings namespace and, for the credentials, writes through the host credential store.

Card control	Where it lands
API Key (compatible) or SecretId / SecretKey / STS Token (native)	dsh credential store (.credentials.yaml), write-only
provider, baseUrl, region, endpoint	settings.yaml under hunyuan-3d
resultDir, pollIntervalMs, defaultWaitMs, httpTimeoutMs	settings.yaml under hunyuan-3d

Two rules the card follows, matching dsh's shipped configuration cards:

• A credential value never travels host → browser. The card learns only whether a reference is configured and whether it is writable; typing a value posts it one-way. An untouched field never clears a stored key.
• Settings take effect immediately. The tools read the resolved section on every call, so a saved change applies to the next call without a restart.

The card talks to the host through a loopback-fenced bridge:

Route	Purpose
GET/POST /api/dsh-hunyuan-3d/settings	read the resolved section + credential status; save a patch
POST /api/dsh-hunyuan-3d/credentials	{ role, action: set | unset, value? }
POST /api/dsh-hunyuan-3d/test	authenticate against the live endpoint without billing (compatible: POST /v1/ai3d/query on a job id that cannot exist; native: QueryHunyuanTo3DProJob on the same)

Non-loopback callers (foreign host, non-loopback peer address, cross-site fetch metadata) get 403; any other method gets 405.