MeloongGod/docs/superpowers/plans/2026-08-25-meloonggod-repository.md

MeloongGod Repository Implementation Plan

For agentic workers: REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (- [ ]) syntax for tracking.

Goal: Create the public PCLPro/MeloongGod GitHub repository with a manifesto-style README, the supplied logo, and an MIT license.

Architecture: Keep the repository intentionally small: one README for project identity and status, one standard license file, one image asset, and the approved design documentation. Create and verify everything locally before switching GitHub CLI to dizuoyun, checking organization access, and publishing the existing main branch.

Tech Stack: Git, GitHub CLI, GitHub Markdown/HTML, PNG, MIT License, PowerShell

---

Task 1: Add the project logo

Files:

• Create: assets/logo.png

• Source: C:\Users\ACX\Downloads\a141f462-0780-4f11-a759-ce88f61c359b..png

• [ ] Step 1: Create the asset directory

Run:

New-Item -ItemType Directory -Path assets -Force

Expected: assets exists under the repository root.

• Step 2: Copy the supplied logo without transforming it

Run:

Copy-Item -LiteralPath 'C:\Users\ACX\Downloads\a141f462-0780-4f11-a759-ce88f61c359b..png' -Destination 'assets\logo.png'

Expected: assets/logo.png exists and retains the source file size.

• Step 3: Verify source and destination hashes match

Run:

Get-FileHash -Algorithm SHA256 'C:\Users\ACX\Downloads\a141f462-0780-4f11-a759-ce88f61c359b..png','assets\logo.png'

Expected: both rows have the same SHA-256 hash.

Task 2: Create the manifesto README

Files:

• Create: README.md

• [ ] Step 1: Write the complete README

Create README.md with exactly this content:

<p align="center">
  <img src="assets/logo.png" alt="我不是尹神 Logo" width="360">
</p>

<h1 align="center">我不是尹神</h1>

<p align="center"><em>I'm not the God of Meloong</em></p>

<p align="center">
  <strong>适用于 Plain Craft Launcher 2 的高级版土豆码生成器</strong>
</p>

---

## 一个土豆码的幽灵

一个土豆码的幽灵，在 PCL2 社区徘徊。

为了对这个幽灵进行神圣的围剿，旧世界的一切势力都联合起来了：不会写正则表达式的人、忘记复制完整报错的人、把配置文件删掉以后说“我什么也没动”的人，以及每一个面对神秘字符串陷入沉思的普通启动器用户。

可是，土豆码凭什么只能由少数掌握古老仪式的人手工搓出？生成按钮凭什么不能属于每一位 PCL2 用户？历史已经把答案写在了启动日志里：土豆码的生产力必须得到解放，土豆码的生产资料必须向全体玩家开放。

于是，`MeloongGod` 诞生了。

我们郑重声明：这里没有尹神，只有一群试图让机器替人搓土豆码的普通劳动者。

## 尹神、PCL2 与未竟的理想

在 PCL2 社区的宏大叙事里，尹海航先生与 Plain Craft Launcher 2 的名字早已被写进启动器民间神话。有人研究界面，有人研究下载，有人研究为什么同一个错误换台电脑就消失，还有人研究那串看起来像土豆、读起来像密码、复制时总会漏掉最后一个字符的代码。

“尹神”是社区玩梗中的光辉称号，而不是本项目开发者的自我认证。本项目名为“我不是尹神”，正因为我们深知：神只有一个，输入框却可以有很多个；神谕难以复现，算法应当可以运行；手工劳动值得尊重，自动生成才是先进生产力。

我们希望以高级版土豆码生成器，继续推动那份朴素而伟大的 PCL 共产主义梦想：复杂的事情交给程序，生成的成果归于用户，人人都能在需要时获得属于自己的土豆码。

## 什么是 MeloongGod

`MeloongGod` 是一个面向 Plain Craft Launcher 2 使用场景的高级版土豆码生成器项目。

它的目标并不神秘：收集生成所需的信息，建立清晰、可复现的处理流程，减少重复手工操作，并把最终结果交还给用户。项目将以公开仓库持续建设，让实现、问题、改进和争论都留在阳光能够照到的地方。

当前仓库处于宣言与基础建设阶段，尚未发布可执行版本。我们拒绝用不存在的下载按钮欺骗群众，也拒绝把尚未完成的功能提前写进胜利公报。

## 土豆码生产纲领

- **生产资料公有化**：生成逻辑公开，项目成果依据 MIT 许可证自由使用、修改与分发。
- **按需生成**：让使用者提交必要信息，由程序承担可以自动化的重复劳动。
- **面向 PCL2**：围绕 Plain Craft Launcher 2 的实际使用场景设计，而不是制造脱离群众的抽象土豆。
- **过程可复现**：同样的有效输入应得到可以解释和验证的结果。
- **错误说人话**：失败时提供明确反馈，不让用户独自凝视一片沉默的控制台。
- **不崇拜手搓**：能够交给计算机的工作，就不要求每位用户重新修炼一遍远古秘术。

## 五步土豆计划

1. **整理生产关系**：明确输入、输出与土豆码生成规则，建立可检验的项目边界。
2. **建设生成核心**：实现稳定、独立且可测试的核心生成流程。
3. **铺设群众界面**：提供清晰的交互入口，让普通 PCL2 用户无需阅读源码即可使用。
4. **建立质量公社**：补充测试、错误处理和兼容性验证，让每一次生成都有据可查。
5. **实现土豆自由**：发布可用版本，接受社区反馈，并持续改进实际体验。

本计划不规定虚假的胜利日期。代码完成一项，我们便如实推进一项；测试没有通过，锣鼓就暂时不敲。

## 如何参加建设

欢迎通过 Issue 提交需求、复现步骤与问题报告，也欢迎通过 Pull Request 贡献实现、测试和文档。

参加建设时，请尽量说明你使用的 PCL2 版本、操作步骤、预期结果与实际结果。日志比传说可靠，复现步骤比“它就是不行”更能推动生产力发展。

在第一个可执行版本发布前，仓库不会提供杜撰的安装命令。请以 Releases 页面和项目公告为准。

## 许可证公有化决议

本项目采用 [MIT License](LICENSE)。

你可以自由使用、复制、修改、合并、发布、分发、再许可或销售本项目的副本，只需保留许可证要求的版权与许可声明。

本项目是面向 PCL2 社区的衍生项目，不代表 Plain Craft Launcher 2 官方，也不声称获得其官方授权或隶属关系。

---

<p align="center">
  <strong>全世界需要土豆码的 PCL2 用户，联合起来！</strong><br>
  你们失去的只是重复劳动，得到的将是自动生成的土豆码。
</p>

• Step 2: Verify required README elements

Run:

rg -n "我不是尹神|I'm not the God of Meloong|Plain Craft Launcher 2|assets/logo.png|MIT License|尚未发布可执行版本" README.md

Expected: each required phrase appears at least once, and the English title is enclosed by <em>.

• Step 3: Verify sensitive data from the reference was not copied

Run:

rg -n "13990280755|1043137532|东西大街|510681200009170012" README.md

Expected: no matches and exit code 1.

Task 3: Add the MIT license

Files:

• Create: LICENSE

• [ ] Step 1: Write the standard license text

Create LICENSE with exactly this content:

MIT License

Copyright (c) 2026 PCLPro contributors

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

• Step 2: Verify the license markers

Run:

rg -n "MIT License|Copyright \(c\) 2026 PCLPro contributors|Permission is hereby granted|THE SOFTWARE IS PROVIDED" LICENSE

Expected: all four markers are present.

Task 4: Validate and commit the initial repository content

Files:

• Validate: README.md
• Validate: LICENSE
• Validate: assets/logo.png
• Preserve: docs/superpowers/specs/2026-08-25-meloonggod-repository-design.md

• Create: docs/superpowers/plans/2026-08-25-meloonggod-repository.md

• [ ] Step 1: Confirm the intended file set

Run:

rg --files

Expected: the README, license, logo, design spec, and implementation plan are listed.

• Step 2: Confirm Git only sees the intended additions

Run:

git status --short

Expected: only README.md, LICENSE, assets/logo.png, and the implementation plan are untracked or added.

• Step 3: Stage the project content

Run:

git add README.md LICENSE assets/logo.png docs/superpowers/plans/2026-08-25-meloonggod-repository.md

Expected: all four paths are staged.

• Step 4: Commit the project initialization

Run:

git commit -m "docs: launch the MeloongGod manifesto"

Expected: one commit adds the README, license, logo, and implementation plan.

Task 5: Publish the GitHub repository with the correct account

Files:

• Remote repository: PCLPro/MeloongGod

• [ ] Step 1: Switch GitHub CLI to the organization account

Run:

gh auth switch --hostname github.com --user dizuoyun

Expected: GitHub CLI reports dizuoyun as the active account.

• Step 2: Verify the active identity

Run:

gh api user --jq .login

Expected: dizuoyun.

• Step 3: Verify organization membership and role

Run:

gh api user/memberships/orgs/PCLPro --jq "{state: .state, role: .role}"

Expected: state is active; the role and organization policy must permit repository creation.

• Step 4: Confirm the target repository still does not exist

Run:

gh repo view PCLPro/MeloongGod

Expected: command fails because the repository does not exist. If it exists, stop and inspect it instead of overwriting anything.

• Step 5: Create the public repository and push main

Run:

gh repo create PCLPro/MeloongGod --public --source . --remote origin --push --description "适用于 Plain Craft Launcher 2 的高级版土豆码生成器"

Expected: GitHub creates https://github.com/PCLPro/MeloongGod, configures origin, and pushes main.

Task 6: Verify the published repository

Files:

• Verify remote: https://github.com/PCLPro/MeloongGod

• [ ] Step 1: Verify repository metadata

Run:

gh repo view PCLPro/MeloongGod --json nameWithOwner,visibility,url,description,defaultBranchRef

Expected: owner/name is PCLPro/MeloongGod, visibility is PUBLIC, URL is correct, description matches, and the default branch is main.

• Step 2: Verify all required paths through the GitHub API

Run:

gh api repos/PCLPro/MeloongGod/contents --jq '.[].name'

Expected: README.md, LICENSE, assets, and docs are returned.

• Step 3: Verify GitHub detected the MIT license

Run:

gh api repos/PCLPro/MeloongGod/license --jq .license.spdx_id

Expected: MIT.

• Step 4: Verify the working tree is clean and tracks the remote

Run:

git status --short --branch

Expected: main tracks origin/main and there are no uncommitted changes.