docs(launch): add maintainer install and trust guide

[jonathanchang31]

Summary

Adds a maintainer-facing launch guide for installing and trusting Gittensory in a repository. The new guide documents GitHub App setup, maintainer controls, command authorization, public-safe previews, browser extension states, audit expectations, CI/check separation from human reviewer approval, and criteria for rejecting weak Gittensory-driven PRs.

Related Issue

Closes: #253

Change Type

• Documentation
• UI / Docs route
• Navigation
• Generated route metadata
• Sitemap update
• Screenshot / evidence artifact
• Bug fix
• Feature runtime change
• Refactor
• Security fix

Real Behavior Proof

Validated locally with the built UI worker:

GET /docs/maintainer-install-trust 200 OK

Checklist

• I added maintainer-facing launch documentation.
• I made the guide discoverable from docs navigation.
• I updated generated route metadata.
• I updated sitemap discovery.
• I validated the project builds.
• I validated tests pass.
• I ran the project locally.
• I captured screenshot evidence.
• I did not change runtime API behavior.

---

UI Evidence

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.

[ghost]

Note

Gittensory Gate skipped

PR closed before full evaluation. No late first comment was created.

Signal	Result	Evidence	Action
Gate result	⚠️ Skipped	#481 is no longer open.	No action.

---

Checked by Gittensory, a quiet PR intelligence layer for OSS maintainers.

[JSONbored]

@jonathanchang31 the guide topic is useful, but this branch needs cleanup before it can merge.

A few notes:

• This is visible docs work, so the screenshot evidence belongs in the PR description as GitHub-hosted JPG/PNG evidence, not as a committed review-only file.
• package-lock.json and worker-configuration.d.ts are unrelated churn for a docs route unless there is a concrete generated-artifact reason, and the PR does not establish that.
• The docs route/nav/sitemap shape is otherwise in the right area.

Required changes:

- Remove docs/evidence/issue-253-maintainer-install-trust-guide.png from the repository.
- Move the required visual evidence into the PR body under a clear UI Evidence or Screenshots section.
- Revert unrelated package-lock.json and worker-configuration.d.ts changes unless they are directly required and explained.
- Re-run the docs/UI validation that covers routeTree, sitemap, nav, lint, typecheck, and build.

Validation expected:

- git diff --check
- ui:lint
- ui:typecheck
- ui:build
- route/sitemap generation check if this repo has a dedicated command for it

[jonathanchang31]

@JSONbored Could you review my PR?

[JSONbored]

@jonathanchang31 this is good to land.

A few notes:

• The previous blockers are fixed: the committed review-only evidence and unrelated generated/package churn are gone.
• The route, nav, sitemap, and generated route metadata are aligned.
• The public/private-boundary wording is acceptable here because it tells maintainers what must not appear in public output; it does not expose actual identifiers, private packets, or optimization tactics.
• Screenshot formatting could be better as clickable thumbnails with captions, but the required evidence is present.

No code changes requested.