TYDAL 1.3.0

Added

• User guide in docs/user-guide/, for the
  people who use TYDAL rather than run it: viewers, editors, administrators,
  owners and platform admins. Nine chapters with screenshots: getting started,
  finding resources, the upload wizard and AiTy suggestions, tags, the basket
  and bulk actions, workspaces and vaults, the trash, organization settings
  and platform administration. Its Known issues section links to the open
  bug issues on GitHub.
• Agent guide, docs/AGENT_GUIDE.md, for AI agents
  that use a TYDAL installation. It covers the three rings (installation;
  organization, with AiTy and @tydal/org-mcp; vault, with
  @tydal/vault-mcp), which one to use, how to connect, the tools, and rules
  of conduct.
• AGENTS.md for AI coding agents working on this
  repository: layout, tier-aware commands, tests, and the codebase's rules.
• TRUSTED_PROXIES (backend/config/trustedproxy.php): the IPs or CIDRs
  of a TLS-terminating proxy to trust, or * for the direct peer. Behind a
  host nginx, TYDAL saw plain http and built http:// vault and file links;
  with the proxy trusted, they're https://. Empty by default, so
  artisan serve and the docker dev tier are unchanged. In every backend env
  template and in DEPLOYMENT.md.

Upgrading

1. Behind a TLS-terminating proxy (a host nginx, a load balancer): set
   TRUSTED_PROXIES in backend/.env to the proxy's IPs or CIDRs, or to *
   to trust the direct peer. * is safe only when the app's port is published
   on 127.0.0.1, so nothing but the proxy can reach it. The templates have
   the variable, with a comment. Without a proxy, leave it empty.
2. Nothing else: no migrations, and the MCP packages and @tydal/client keep
   their 1.2.0 versions.

Full changes: v1.2.0...v1.3.0