action1-v0.1.3

Fixed

• A client secret supplied through the environment was written to disk in cleartext.
  ACTION1_CLIENT_SECRET was read into the config struct without being marked as an
  environment override, and the save path restored only ACTION1_OAUTH2 from the on-disk copy
  • so the live secret was copied into config.toml under client_secret on the next save.
    ACTION1_CLIENT_ID had the same gap. Both are now marked and restored, so a value supplied
    by the environment stays in the environment. If you have run this CLI with either variable
    set, a cleartext copy may already be on disk. Upgrading does not remove it: inspect
    ~/.config/action1-cli/config.toml, delete it, and rotate the credential.

Added

• ACTION1_NO_CONFIG_WRITE=1 keeps every credential off disk. Set it and the CLI mints a token per
  invocation instead of caching one in config.toml. The MCP server honours the same switch,
  which it previously could not: it resolved its own config path and ignored --config
  entirely, so a Claude Desktop setup kept a plaintext token cache even when the CLI had been
  told not to write one. auth logout still clears a config that already exists - the switch
  suppresses credential writes, not the erase.

Changed

• Install and remote-agent documentation corrected against the shipped binaries. The remote
  section named mcp-remote, which bridges the opposite direction and cannot publish a local
  stdio server at all; connectors that parse --transport http now point at the native flag
  and the rest at supergateway. The HTTP endpoint is /mcp, not the bare root the docs gave.
  The Windows install path and a fallback paragraph describing an npx install that is not
  offered were both wrong and are gone. A new check_install_docs gate holds these claims
  against the binaries and installers so they cannot drift again.