Docs: clarify @arg type vs signature type hint relationship

[Copilot]

The docs showed both @arg type keywords and signature type hints without explaining which wins, whether both are required, or what each one actually controls at runtime.

Changes

• docs/attributes-and-interpreters.md — Updated the @arg bullet to note the type keyword is a fallback (not the primary driver), and added a blockquote callout spelling out the full precedence rules:

  • Signature type hint controls MCP JSON schema type and drives runtime value conversion in polyglot functions
  • @arg type is consulted only when there is no typed signature (legacy $1/$2-style shell functions)
  • @arg description is always used regardless
  • On conflict, signature type hint wins

• docs/arguments.md — Added a summary sentence to the "Types in signatures" section with a cross-link to the detailed note above

Precedence in one glance

# @arg env string Target environment  ← fallback; ignored here because signature is typed
deploy(env: str, version = "latest") { ... }
#             ^^^^ primary: sets MCP schema type + polyglot runtime conversion

[nihilok]

@copilot clippy is failing

[Copilot]

@copilot clippy is failing

Fixed in 81ef41f — three duration_suboptimal_units errors in tests/mcp_server_test.rs (lines 549, 607, 997): replaced from_millis(1000)/from_millis(2000) with from_secs(1)/from_secs(2). Clippy now passes cleanly.