docs: add customized HER Hack-Astron issue template

[FenjuFu]

What changed

• Add a repository-specific HER Hack-Astron challenge proposal template.
• Pre-fill HER Hack-Astron #出题｜赛题名称 and apply the HER Hack-Astron label.
• Keep proposals unofficial until @FenjuFu reviews them, assigns the round number, and renames the issue.
• Customize challenge directions, deliverables, acceptance criteria, review dimensions, and safety constraints for this project.

Repository-specific design

• Focus: 文件原生记忆写入、检索、巩固、冲突、遗忘、隐私和可重复评测
• Evidence used: 要求 before/after 任务评测、Token/延迟/磁盘指标及用户可查看修改删除

Contributor impact

Community partners can propose challenges that produce changes aligned with this repository instead of submitting a generic Agent demo. The template also preserves the HER Hack-Astron rule that women must represent at least 50% of contributors recorded in PR commits.

Validation

• Valid Markdown issue-template frontmatter
• Title prefix and default label configured; reviewer and participation guidance documented in the Markdown template (not programmatically enforced)
• Template committed directly from the latest default branch
• Prettier, DCO, lint, unit tests, CodeQL, and e2e-k8s checks pass

[Copilot]

Pull request overview

Adds a repository-specific GitHub Issue Template for proposing HER Hack-Astron challenges, tailored to MemFlywheel’s “file-native memory” scope (write/retrieve/consolidate/conflict/forget/privacy) and requiring structured deliverables and evaluation criteria.

Changes:

• Added a new Markdown issue template for HER Hack-Astron challenge proposals.
• Pre-filled the issue title pattern and applied the HER Hack-Astron label via template frontmatter.
• Documented challenge directions, deliverables, acceptance criteria, and review dimensions in the template body.

Suppressed comments (1)

.github/ISSUE_TEMPLATE/her-hack-astron-challenge.md:5

• Frontmatter labels is using an inline YAML list, while the repo’s other Markdown issue templates use a scalar string (e.g. .github/ISSUE_TEMPLATE/bug_report.md:5, feature_request.md:5). Using the scalar format is more consistent here and avoids any template parser edge cases.

title: 'HER Hack-Astron #出题｜赛题名称'
labels: ['HER Hack-Astron']

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[dongjiang1989]

@FenjuFu Please sign DCO and fix lint

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

Suppressed comments (2)

.github/ISSUE_TEMPLATE/her-hack-astron-challenge.md:6

• Frontmatter here differs from the repository’s other issue templates: they use a scalar labels: value and include an explicit assignees: "" field (see .github/ISSUE_TEMPLATE/bug_report.md:5-6 and feature_request.md:5-6). Aligning this template avoids surprises in how GitHub parses labels/assignees across templates.

name: 🌸 HER Hack-Astron 出题
about: 面向文件原生 Agent 记忆、检索、巩固与评测发布赛题
title: "HER Hack-Astron #出题｜赛题名称"
labels: ["HER Hack-Astron"]
---

.github/ISSUE_TEMPLATE/her-hack-astron-challenge.md:10

• Including @FenjuFu directly in the template body will notify that user on every issue created from this template. If you want to avoid automatic notification spam, consider removing the inline mention and instead instruct authors to tag the reviewer in a follow-up comment when the draft is ready for review.

> **赛题确认：** @FenjuFu 审核并将标题改为正式期号后生效。
>
> **活动标签：** 本模板自动添加 `HER Hack-Astron`。

[FenjuFu]

Thanks for the reminder. The commit has been re-signed with a matching DCO identity, and the template has been formatted with Prettier. DCO, lint, unit tests, CodeQL, and e2e-k8s are now all passing.

[FenjuFu]

该 PR 已等待了一段时间，期间没有其他维护者接手处理。现已完成统一复核：变更仅新增仓库定制的 HER Hack-Astron issue 模板，未发现阻塞问题，CLA/DCO 及现有 CI 均通过，因此按维护决策合并。