Add drawing without account access to the comparison tables

[patrickchugh]

Type of Change

• Bug Fix
• New Feature
• Refactor
• Documentation

What and why

Follow-up to #229. The FAQ and the scanner comparison now say that TerraVision draws from code plus a variables file, so it can draw an environment you cannot log in to or one that is not built yet. The two comparison tables did not reflect that.

• README.md, "How it compares": a new row, "Draw an environment you have no access to, or one not built yet", placed after "Draw from Terraform". TerraVision: from the code and a variables file, --varfile prod.tfvars for prod and --varfile dev.tfvars for dev, with no access to the target account or its state. Manual tools, AI workspaces and diagram as code: partly, by hand or from pasted code. Live scanners: no, they draw only an account they can connect to.
• docs/alternatives.md, comparison table: the same row after "Diagram from Terraform". The existing "Needs access to your cloud account" row is unchanged: TerraVision itself never accesses a cloud account.

Checks: both tables keep their column counts, mkdocs build passes with no warnings, no em-dashes in added lines.

Checklist

All Submissions:

• Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• Have you written Documentation/Tests?
• Have you done your own code-review?
• Have you disclosed any use of AI tools and models with their version?

AI Assistance Declaration

• Tools used: Claude Code
• Model: Claude Fable 5.1
• Scope: Wrote the two table rows; verified the build. Reviewed by the author.

Checklist for Changes to Core Features:

• Have you discussed any major revamp with a reviewer/maintainer first? (It's okay to just raise a PR directly for minor bugfixes)
• Have you ensured your PR is focused on one major improvement and is not trying to do too many changes at once?
• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your core changes, as applicable, and made sure the new tests PASS? (documentation only)
• Have you successfully run all previous system wide tests with your changes locally? (mkdocs build; core code unchanged)

🤖 Generated with Claude Code