docs(landing): add public "How Logion works" page (closes #163)

[qingguang2025-cmyk]

Summary

Closes #163. Adds a public "How Logion works" page so visitors can understand the product without installing the CLI.

This is a documentation-only change to the landing page — no behavior, pricing, or trust claims were altered beyond what the issue requested.

What changed

• **** (new): explains the marketplace loop, what a course bundle is, what / declarations do, first steps by audience (buyer / creator / contributor / reviewer), install, and an honest trust model.
• ****: reuses the existing legal-page rendering path for a new route (HTML + ), registers it in , and folds it into so agents get the full explanation in one fetch.
• ****: content block, top-nav link, breadcrumbs, and an entry.
• ****: covers the new route (HTML + markdown), sitemap / listing, and folding.

Notes

• All CLI examples use the real, documented verbs from the existing landing copy (no invented commands).
• The trust section explicitly states runtime sandbox enforcement is future work and is not claimed as solved, matching the rest of the site.
• Passes and ; 113 landing tests green.

Verification

[nicolasmelo1]

Review — request changes

Thanks for the focused public-product explanation and for covering HTML, Markdown, sitemap, llms.txt, and llms-full.txt. The runtime-sandbox caveat is also appropriately honest.

High

1. The Contributor section gives the wrong role and an invalid CLI invocation.
   packages/landing/landing/content/how-it-works.md:82

   It tells a contributor to run logion bounties create, which opens a bounty rather than submitting work to one. The example also uses --reward, but the current CLI requires --description and --reward-cents for bounties create.

   Please either:

   • make this a creator example with a complete valid bounties create command, or
   • make it a contributor example using logion bounties submissions create BOUNTY_ID --title ....

2. CI is currently failing on four Ruff E501 violations.
   packages/landing/landing/main.py:187,336,563 and packages/landing/tests/test_landing_routes.py:230.

   Please run the repository lint/format checks and wrap these lines.

Medium

1. Bounty acceptance must remain distinct from publication.
   how-it-works.md:35-36,102

   The text says accepted work “ships as a new reviewed version.” Acceptance creates the contributor payment outcome, but publication review still determines whether the work becomes a new course version. Please state that accepted work remains subject to publication review before it can ship.

2. Avoid framing capability declarations as a guarantee of negative behavior.
   how-it-works.md:56-61

   “what the bundle will not do” sounds like an enforceable runtime guarantee, while runtime sandbox enforcement is explicitly future work. Please use wording such as “expected tools, permissions, and behavior for inspection and review.”

Low

legal_page / legal.html now render a non-legal product document. Not blocking, but a neutral abstraction would be clearer if this route pattern expands.

Please address the high-severity items and re-request review.

[nicolasmelo1]

Just a little couple issues