docs(builders): consolidate and clean up builder documentation

[davd-gzl]

Depends on: #5755

Reduces docs/builders/ from 11 to 8 files, renames the rest for clarity, and cleans up the bits that got stale or broken in the process.

• Removed anatomy-of-a-gno-package.md and deploy-packages.md — content already lived in getting-started.md or other reference pages.
• local-dev-with-gnodev.md → resources/gnodev.md, rewritten as a reference (features + flags, no longer a Counter walkthrough).
• example-minisocial-dapp.md → tutorial-minisocial.md, tightened throughout: condensed the setup steps into a single block, replaced regex-sliced embedmd snippets with full files for clarity, dropped the redundant gnodev startup walkthrough in favour of a link, and fixed a broken sentence introducing posts.gno.
• resources/gno-testing.md rewritten from tutorial to reference (drops the duplicated Counter setup, fixes broken install link, renames sections to match gno test / gno run).
• Renames: what-is-gnolang → what-is-gno, quick-start → quickstart, connect-clients-and-apps → rpc-clients, become-a-gnome → contributor-guide. H1 titles aligned with new filenames.
• Preserved unique content: package-type import matrix → resources/gno-packages.md; pointers from getting-started.md → gas-fees.md (out-of-gas troubleshooting), storage-deposit.md (-max-deposit).
• Renamed the default gnodev key test1 → devtest everywhere (matches the cheatsheet and gnodev's actual default).
• Fixed broken auto-link in quickstart.md, broken [Docs] reference in tutorial-minisocial, and the stale anatomy-of-a-gno-package.md link in gnoland-whitepaper.tex.
• Cross-links updated across docs/, README.md, and misc/deployments/.

Includes earlier in-flight docs work merged into this branch.

[Gno2D2]

🛠 PR Checks Summary

All Automated Checks passed. ✅

Manual Checks (for Reviewers):

• IGNORE the bot requirements for this PR (force green CI check)
• Determine if infra needs to be updated before merging

Read More

🤖 This bot helps streamline PR reviews by verifying automated checks and providing guidance for contributors and reviewers.

✅ Automated Checks (for Contributors):

🟢 Maintainers must be able to edit this pull request (more info)
🟢 Pending initial approval by a review team member, or review from tech-staff

☑️ Contributor Actions:

1. Fix any issues flagged by automated checks.
2. Follow the Contributor Checklist to ensure your PR is ready for review.
   • Add new tests, or document why they are unnecessary.
   • Provide clear examples/screenshots, if necessary.
   • Update documentation, if required.
   • Ensure no breaking changes, or include BREAKING CHANGE notes.
   • Link related issues/PRs, where applicable.

☑️ Reviewer Actions:

1. Complete manual checks for the PR, including the guidelines and additional checks if applicable.

📚 Resources:

• Report a bug with the bot.
• View the bot’s configuration file.

Debug

Automated Checks

Maintainers must be able to edit this pull request (more info)

If

🟢 Condition met
└── 🟢 And
    ├── 🟢 The base branch matches this pattern: ^master$
    └── 🟢 The pull request was created from a fork (head branch repo: davd-gzl/gno)

Then

🟢 Requirement satisfied
└── 🟢 Maintainer can modify this pull request

Pending initial approval by a review team member, or review from tech-staff

If

🟢 Condition met
└── 🟢 And
    ├── 🟢 The base branch matches this pattern: ^master$
    └── 🟢 Not (🔴 Pull request author is a member of the team: tech-staff)

Then

🟢 Requirement satisfied
└── 🟢 If
    ├── 🟢 Condition
    │   └── 🟢 Or
    │       ├── 🔴 At least one of these user(s) reviewed the pull request: [aronpark1007 davd-gzl jefft0 notJoon omarsy MikaelVallenet] (with state "APPROVED")
    │       ├── 🟢 At least 1 user(s) of the team tech-staff reviewed pull request
    │       └── 🔴 This pull request is a draft
    └── 🟢 Then
        └── 🟢 Not (🔴 This label is applied to pull request: review/triage-pending)

Manual Checks

**IGNORE** the bot requirements for this PR (force green CI check)

If

🟢 Condition met
└── 🟢 On every pull request

Can be checked by

• Any user with comment edit permission

Determine if infra needs to be updated before merging

If

🟢 Condition met
└── 🟢 And
    ├── 🟢 The base branch matches this pattern: ^master$
    └── 🟢 Or
        ├── 🔴 A changed file matches this pattern: Dockerfile
        ├── 🟢 A changed file matches this pattern: ^misc/deployments (filename: misc/deployments/home-alias/home.default.md)
        ├── 🔴 A changed file matches this pattern: ^misc/docker-
        └── 🔴 A changed file matches this pattern: ^.github/workflows/release.*\.yml$

Can be checked by

• team devops

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[alexiscolin]

@davd-gzl Can you resolve the conflicts and let me know when it's ready to merge? I'll take care of it. 👍

[davd-gzl]

(still need to fix the CI)
fix: 84a40b9

[alexiscolin]

Updating the homepage markdown file and the home realm may prevent a 404 error or redirect.

[davd-gzl]

Good catch, fix: 0bbcb61
@alexiscolin

[alexiscolin]

@davd-gzl Here is the actual homepage at the moment. :) https://github.com/gnolang/gno/blob/master/misc/deployments/home-alias/home.default.md

[davd-gzl]

@alexiscolin Sorry I misunderstood, though it was already patched in earlier commit:

gno/misc/deployments/home-alias/home.default.md

Line 45 in 0bbcb61

- [Efficient local development for Gno](https://docs.gno.land/resources/gnodev)