docs: finalize open-source readiness baseline

Author: chocoHunter

.github/ISSUE_TEMPLATE/config.yml

@@ -1,5 +1,5 @@
 blank_issues_enabled: false
 contact_links:
   - name: Security report
-    url: https://github.com/chocoHunter/matcha/security
+    url: https://github.com/chocoHunter/matcha/security/advisories/new
     about: Please use private security reporting for vulnerabilities or sensitive power-management issues.

.gitignore

@@ -5,7 +5,6 @@ Build/
 *.xcworkspace/
 *.xcodeproj
 *.xcworkspace
-Matcha.entitlements
 Sources/Matcha
 *.app/
 *.dmg

CHANGELOG.md

@@ -4,14 +4,19 @@ All notable changes to this project will be documented in this file.
 
 ## Unreleased
 
-- Added battery-mode recovery using stored `pmset` snapshots instead of fixed restore values.
-- Added startup self-healing and clearer recovery behavior for battery-mode power overrides.
-- Added lid-close display sleep handling for battery mode to better match closed-lid background use.
-- Added unit tests for `pmset` parsing, restore planning, and lid-close display-sleep transitions.
-- Added a release build script for generating and validating `.app` and `.dmg` artifacts.
-- Added CI, open-source readiness docs, and repository metadata files.
-- Improved README and README-CN with clearer mode explanations, recovery guidance, and build steps.
+- Added open-source community files: `CONTRIBUTING.md`, `SECURITY.md`, issue templates, and PR template.
+- Improved `README.md` and `README-CN.md` structure with clearer mode differences and onboarding screenshots.
+- Added release documentation for signing, notarization, and verification workflow.
+- Improved battery-mode safety behavior and recovery documentation.
 
-## 1.0.0
+## 1.0.1 - 2026-03-08
+
+- Added **Lid Closed (Battery)** mode for closed-lid operation without power adapter.
+- Improved menu UI with mutually exclusive mode checkmarks.
+- Moved **Resume Sleep** to the top as the default state.
+- Updated app icon.
+- Fixed password prompt behavior so admin auth is only requested when enabling battery mode.
+
+## 1.0.0 - 2026-02-28
 
 - Initial public project structure and menu bar sleep-prevention modes.

CODE_OF_CONDUCT.md

@@ -0,0 +1,64 @@
+# Code of Conduct
+
+## Our Pledge
+
+We as contributors and maintainers pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes
+- Focusing on what is best for the community and project users
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Project maintainers are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned with this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all project spaces and also applies when an individual is officially representing the project in public spaces.
+
+## Reporting and Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported via:
+
+- Private vulnerability reporting: https://github.com/chocoHunter/matcha/security/advisories/new
+
+All reports will be reviewed and investigated promptly and fairly.
+
+## Enforcement Guidelines
+
+Maintainers will follow these Community Impact Guidelines in determining consequences for any action deemed in violation of this Code of Conduct:
+
+1. Correction: Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome.
+Consequence: A private, written warning from maintainers, with clarity around the nature of the violation and an explanation of why the behavior was inappropriate.
+
+2. Warning: Community Impact: A violation through a single incident or series of actions.
+Consequence: A warning with consequences for continued behavior. No interaction with the people involved for a specified period of time.
+
+3. Temporary Ban: Community Impact: A serious violation of community standards, including sustained inappropriate behavior.
+Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period.
+
+4. Permanent Ban: Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+Consequence: A permanent ban from any sort of public interaction within the project.
+
+## Attribution
+
+This Code of Conduct is adapted from the Contributor Covenant, version 2.1:
+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html

README-CN.md

@@ -11,6 +11,19 @@
 - 定时模式：15 分钟到 24 小时，或永久
 - 开机自启
 
+## 安装方式
+
+### 方式一：下载发布包（推荐）
+
+1. 打开 [Releases](https://github.com/chocoHunter/matcha/releases)。
+2. 下载最新 `Matcha.dmg`。
+3. 将 `Matcha.app` 拖到 `/Applications`。
+4. 首次启动时按提示授权。
+
+### 方式二：本地源码构建
+
+可直接使用文末 `如何构建` 章节。
+
 ## 使用方法
 
 1. 点击菜单栏 Matcha 图标。
@@ -80,6 +93,7 @@ sudo pmset restoredefaults
 ## 项目文档
 
 - `CONTRIBUTING.md`：贡献流程与测试要求
+- `CODE_OF_CONDUCT.md`：社区协作行为准则
 - `SECURITY.md`：安全漏洞反馈方式
 - `CHANGELOG.md`：项目重要变更记录
 - `docs/release.md`：发布检查、签名与公证流程

README.md

@@ -11,6 +11,19 @@ A macOS menu bar app for preventing sleep, with practical lid-closed modes for M
 - Flexible timer (15 min to 24 hours, or permanent)
 - Launch at login
 
+## Install
+
+### Option 1: Download release (recommended)
+
+1. Open [Releases](https://github.com/chocoHunter/matcha/releases).
+2. Download the latest `Matcha.dmg`.
+3. Drag `Matcha.app` into `/Applications`.
+4. Launch Matcha and grant permissions when prompted.
+
+### Option 2: Build from source
+
+Use the build steps in `How to Build` below.
+
 ## Usage
 
 1. Click the Matcha menu bar icon.
@@ -80,6 +93,7 @@ sudo pmset restoredefaults
 ## Project Docs
 
 - `CONTRIBUTING.md`: contributor workflow and testing expectations
+- `CODE_OF_CONDUCT.md`: community standards and enforcement rules
 - `SECURITY.md`: vulnerability reporting guidance
 - `CHANGELOG.md`: notable project changes
 - `docs/release.md`: release checklist, signing, and notarization workflow

SECURITY.md

@@ -8,7 +8,11 @@ Matcha is currently maintained on the latest `main` branch.
 
 Please do not open a public GitHub issue for security-sensitive reports.
 
-Instead, report vulnerabilities privately to the maintainer through GitHub security reporting if available, or by direct maintainer contact before public disclosure.
+Please report vulnerabilities through GitHub Private Vulnerability Reporting:
+
+- https://github.com/chocoHunter/matcha/security/advisories/new
+
+If that page is unavailable for any reason, open an issue titled `SECURITY: private contact request` without technical details, and we will move to a private channel.
 
 When reporting, please include:
 

Sources/Info.plist

@@ -17,9 +17,9 @@
     <key>CFBundlePackageType</key>
     <string>APPL</string>
     <key>CFBundleShortVersionString</key>
-    <string>1.0.0</string>
+    <string>$(MARKETING_VERSION)</string>
     <key>CFBundleVersion</key>
-    <string>1</string>
+    <string>$(CURRENT_PROJECT_VERSION)</string>
     <key>LSMinimumSystemVersion</key>
     <string>$(MACOSX_DEPLOYMENT_TARGET)</string>
     <key>LSUIElement</key>

Sources/Matcha.entitlements

@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+<plist version="1.0">
+<dict/>
+</plist>

docs/2026-03-14-open-source-readiness-todo.md

@@ -9,6 +9,9 @@
 - [x] 明确危险能力说明：在 README/README-CN 加入“会修改系统电源策略（pmset）”的风险提示和恢复说明
 - [x] 清理发布流程中的本地产物策略：确认 `Build/`、`*.dmg`、`Matcha.xcodeproj` 是否应提交；若不提交，完善 `.gitignore`（当前仅忽略 `build/`，未覆盖 `Build/`）
 - [x] 增加最小可验证构建说明（本机若未安装完整 Xcode，会导致 `xcodebuild` 不可用）
+- [x] 对齐版本与发布记录（`project.yml`、`Info.plist`、`CHANGELOG.md`）
+- [ ] 仓库切换为 Public，并补充仓库描述与 Topics
+- [ ] 完成 Developer ID 签名、公证、staple 与 `spctl` 校验后再发布二进制
 
 ## P1 - 建议在首次开源后尽快补齐
 
@@ -18,6 +21,7 @@
 - [x] 增加 `SECURITY.md`（漏洞报告渠道、处理 SLA）
 - [x] 增加 Issue / PR Template，减少社区沟通成本
 - [x] 增加发布文档：签名、公证、DMG 产物生成与校验步骤
+- [x] 增加 `CODE_OF_CONDUCT.md`，补齐社区协作规范
 
 ## P2 - 体验与可维护性优化