Skip to content

docs: update the roadmap, and report issue/PR state with numbers - #1769

Merged
Ikalus1988 merged 1 commit into
mainfrom
docs/roadmap-2026-09-16
Sep 16, 2026
Merged

docs: update the roadmap, and report issue/PR state with numbers#1769
Ikalus1988 merged 1 commit into
mainfrom
docs/roadmap-2026-09-16

Conversation

@Ikalus1988

@Ikalus1988 Ikalus1988 commented Sep 16, 2026 •
edited by github-actions Bot
Loading

Copy link
Copy Markdown
Owner

User description

Why

ROADMAP.md had not been touched in three weeks (last update 2026-08-22) and no longer described this repository:

roadmap said repository says
GitHub release v2.18.0 2.30.2
Local MCP server exposes three tools 7 remote, 9 local stdio
python scripts/site_health.py that file does not exist (it is site_health_check.py)
PyPI misakanet-core the real PyPI name is misakanet
Do NOT add authentication to MCP, keep it simple Bearer auth exists for write_lesson / preflight

Two "done" items pointed at scripts that never existed in git history (freshness_scorer.py, gap_analyzer.py) — the work landed elsewhere (misakanet/freshness.py, scripts/demand_board.py). #1165's misakanet_memory_context shipped only into the local stdio server and is not among the remote 7. GX1 was explicitly reverted in 42e374345 and still read as a milestone. Three documents quoted three different lesson counts (200+/363/377) and none matched reality.

What changes

  • ROADMAP.md — a dated ## 2026-09-16 更新 section containing: a verified status snapshot (every number has the command that produced it in the appendix, re-run to confirm), a 39-row adjudication of the old items marked done / stale / abandoned with the reason and the evidence, the six new priorities from docs/maintainer/blueprint-and-strategy-review-2026-09-16.md phrased as work someone can pick up, and a "still not doing" list. Old text is preserved verbatim; each old heading got a one-line dated status marker. Header now states this is the only outward-facing roadmap.
  • docs/rfc-280-90-day-roadmap.md — dated historical header pointing at ROADMAP.md. Vision 1/2 were adopted and exceeded; Vision 3 was never started as a product line; Vision 4 (federated/enterprise) still has no PRD.
  • docs/maintainer/issue-pr-status-2026-09-16.md — machine-read PR/issue state, snapshot 2026-09-16T14:59Z, with the endpoints listed so it can be re-derived.

Three things the status snapshot establishes

  1. 14 open PRs, but only 2 are merge-ready. The other 12 are blocked mechanically, not on judgement — 6 by a failing dco/audit/gate (the only concrete annotation readable is DCO audit failed, i.e. a missing Signed-off-by:), 5 green but awaiting review, 1 conflict + draft.
  2. Triage volume is not the bottleneck it feels like. 30-day averages are 8.3 issues/day and 16.6 PRs/day, but only 1.3–2.2 intakes/day need human judgement (0 in the last 24h). What is actually piling up: 22 of 43 open issues are waiting on a maintainer reply, 7 bounty conversions have zero maintainer comments, and 18 of 44 unmerged closes in 7 days were re-submissions of the same title / superseded work.
  3. The intake→lesson conversion rate is not derivable today — issue timelines carry no conversion marker and only 3 of 440 lessons reference any issue number. Recorded as 未获取 rather than estimated; it is the metric the flywheel story needs most.

Also updates priority ① to done in #1768 (the provenance gate), and keeps an explicit "still cannot check semantic truth" note there.

Docs only. Numbers that could not be verified from the repository (production MCP_VERSION, external listing states, PR #624/#622 outcomes) are marked 未验证 rather than asserted.

PR Type

Documentation

Description

Diagram Walkthrough

flowchart LR
  A["ROADMAP.md (outdated)"] --> B["Verified status snapshot<br/>2026-09-16"]
  B --> C["39-row adjudication<br/>done / stale / abandoned"]
  C --> D["Six new priorities"]
  E["docs/rfc-280-90-day-roadmap.md"] --> F["Marked historical<br/>pointer to ROADMAP.md"]
  G["New: issue-pr-status snapshot"] --> H["PR/issue state<br/>2026-09-16T14:59Z"]
Loading

File Walkthrough
Relevant files
Documentation
rfc-280-90-day-roadmap.md
Mark RFC 280 as historical; redirect to ROADMAP.md             

docs/rfc-280-90-day-roadmap.md

  • Added dated 2026-09-16 historical header at the top stating the RFC is
    not the current roadmap
  • Points readers to ROADMAP.md as the only outward-facing roadmap
  • Documents which Visions were adopted, which never started, and that
    Vision 4 has no PRD
  • Corrects the stale "363 lessons" figure to the actual current count
    (393)
 +14/-0   
ROADMAP.md
Refresh ROADMAP.md with verified snapshot and adjudication

ROADMAP.md

  • Adds dated ## 2026-09-16 更新 section with a verified status snapshot
    (every number reproducible)
  • Includes a 39-row adjudication of legacy items as done / stale /
    abandoned with evidence
  • Phrases six new priorities from the strategy review as pickable work
    items
  • Updates file header to declare this is the only outward-facing
    roadmap; preserves old text verbatim
 +286/-1 
issue-pr-status-2026-09-16.md
Add dated issue/PR state snapshot file                                     

docs/maintainer/issue-pr-status-2026-09-16.md

  • New machine-readable snapshot of PR/issue state at 2026-09-16T14:59Z
  • Reports counts for open PRs / issues and per-area distribution
  • Provides a referenceable artifact tied to the roadmap refresh
 +595/-0 

@Ikalus1988
docs: bring the roadmap up to date, and report issue/PR state with nu…
c312ed6 
…mbers

The public roadmap had not been updated in three weeks and had drifted away from the
repository in ways a newcomer could not detect: it advertised v2.18.0 (really 2.30.2),
three MCP tools (really 7 remote / 9 local), and `python scripts/site_health.py` — a file
that does not exist. Two "done" items named scripts that never existed in git history
(`freshness_scorer.py`, `gap_analyzer.py`); #1165 shipped only into the local stdio server
and is not in the remote tool set; GX1 was explicitly reverted in 42e374345 and still read
as a milestone.

What this does:

- `ROADMAP.md` — a dated `2026-09-16 更新` section: a verified status snapshot (every number
  reproducible via the commands in the appendix), a 39-row adjudication of the old items
  (done / stale / abandoned, each with a reason and evidence), the six new priorities
  phrased as pickable work, and an explicit "what we are still not doing" list. Old text is
  preserved verbatim with a one-line status marker under each old heading; the file header
  now says it is the only outward-facing roadmap.
- `docs/rfc-280-90-day-roadmap.md` — a dated historical header pointing at `ROADMAP.md`.
  Its Vision 1/2 were adopted and exceeded, Vision 3 was never started as a product line,
  and Vision 4 (federated / enterprise) still has no PRD. Its "hybrid search with
  embeddings" days directly contradict the standing anti-embedding position, which is worth
  knowing before anyone re-proposes it.
- `docs/maintainer/issue-pr-status-2026-09-16.md` — a machine-read snapshot of PR/issue
  state (snapshot 2026-09-16T14:59Z): 14 open PRs of which only 2 are merge-ready; 43 open
  issues; 8.3 issues/day and 16.6 PRs/day over 30 days, of which only 1.3–2.2 intakes/day
  actually need human judgement. The bottleneck is PR close-out and duplicate submissions,
  not triage volume — 22 of 43 open issues are waiting on a maintainer reply, and 18 of the
  44 unmerged closes in 7 days were re-submissions of the same title or superseded work.

Also marks priority ① (the provenance gate) as done in #1768, and states plainly what that
gate still cannot check (semantic truth).

Signed-off-by: Ikalus1988 <136884451+Ikalus1988@users.noreply.github.com>
@Ikalus1988 Ikalus1988 added area:docs docs-only Only documentation files changed shape-safe labels Sep 16, 2026
@github-actions

github-actions Bot commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

🎫 Ticket compliance analysis 🔶

1165 - Partially compliant

Compliant requirements:

Non-compliant requirements:

  • Tool registration in tools/list
  • Domain extraction from file paths
  • Compact lesson summaries / freshness / evidence level fields
  • Unit tests
  • README.md MCP tools section update

Requires further human verification:

1768 - Partially compliant

Compliant requirements:

  • None

Non-compliant requirements:

  • All functional requirements (gate script, tests, CI workflow, baseline register) — this PR only updates docs

Requires further human verification:

624 - Partially compliant

Compliant requirements:

  • None

Non-compliant requirements:

  • All functional requirements — this PR is a docs-only roadmap refresh

Requires further human verification:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪
🧪 No relevant tests
🔒 No security concerns identified
⚡ Recommended focus areas for review

Possible Fact Drift

The new banner claims the current lesson count is "393" with the verification command python3 scripts/sync_lesson_count.py --check. PR-agent-generated descriptions and the diff can drift from the live count if lessons are merged between when the doc was written and when this PR is reviewed. Maintainers should re-run the verification command before merge and confirm the number still matches. The number 393 also must stay consistent with the same claim surfaced in the truncated ROADMAP.md and docs/maintainer/issue-pr-status-2026-09-16.md files (not visible in the diff).

 
> 文中的 363 篇课程是当时口径，现为 393（`python3 scripts/sync_lesson_count.py --check`）。
Cross-Doc Consistency

The banner asserts that the "唯一对外路线图" is ROADMAP.md and references docs/maintainer/blueprint-and-strategy-review-2026-09-16.md §2.4 for Vision 4's no-PRD claim. Both the new ROADMAP.md content and the new docs/maintainer/issue-pr-status-2026-09-16.md file are truncated from this diff, so it cannot be confirmed that the cross-referenced claims (lesson count, "7 remote tools", "GX1 reverted in 42e374345", script names) are consistent across all three docs. This is not a bug in the visible lines but a coordination risk worth a manual sanity check.

 
> **历史文档 · 2026-09-16 标注**
>
> 本文是 2026-07-29 的一次 RFC 提案（issue #280），**不是当前路线图**，其中的
> Vision 1–4、指标数字与 90 天计划均未随仓库演进更新。
>
> **唯一对外路线图是 [`ROADMAP.md`](../ROADMAP.md)**（仓库根目录），当前计划看其中的
> 「2026-09-16 更新 — 五层拼图与优先事项」一节。
>
> 本文仅保留为决策记录：Vision 1（经验复用底座）与 Vision 2（薄 MCP 网关）已被采纳并超出原计划
> （远端 MCP 现有 7 个工具）；Vision 3（agent 能力测试平台）未作为独立产品线启动；
> Vision 4 里的 Federated / Enterprise 至今**没有 PRD、没有实现**（见
> `docs/maintainer/blueprint-and-strategy-review-2026-09-16.md` §2.4）。
> 文中的 363 篇课程是当时口径，现为 393（`python3 scripts/sync_lesson_count.py --check`）。

⚠️ Review coverage: The following files were not included in this review because of the token budget:

  • docs/maintainer/issue-pr-status-2026-09-16.md
  • ROADMAP.md

@Ikalus1988

Ikalus1988 commented Sep 16, 2026

Copy link
Copy Markdown
Owner Author

🧾 Audit Report — PR #1769 (c312ed6)

📊 Quality Score

⚠️ Quality score unavailable; continuing with hard gates.

🔏 DCO Audit

✅ All commits signed-off.

📏 PR Size

Metric Value
Files Changed 3
Lines Added 895
⚠️ Warning ; 895 lines added (threshold: 500)

🔐 Secret Scan

✅ No hardcoded secrets detected.

📦 Dependency Audit

⏭️ Skipped; no Python/JS dependency files changed.

🧪 Test Suite

✅ PASS — 53% coverage

📋 Lesson Schema

✅ All lessons valid.

⚖️ Verdict

✅ All gates passed. Ready for merge.

Scope: full | Triggered by c312ed6 | View run

@github-actions

github-actions Bot commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

PR Code Suggestions ✨

No code suggestions found for the PR.

@Ikalus1988
Ikalus1988 merged commit 171698f into main Sep 16, 2026
24 checks passed
@github-actions

github-actions Bot commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

🎉 Merged — Thank you!

Your contribution has been merged into main.

PR: #1769 — docs: update the roadmap, and report issue/PR state with numbers

What's next:

  • Your code is now part of MisakaNet's failure-lesson corpus (now 393 lessons)
  • Feel free to pick up another issue labeled good first issue or status: competition
  • Questions? Ask in this thread or open a Discussion

Welcome to the MisakaNet contributor community! 🧠

@github-actions

github-actions Bot commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

✅ Merged! Thanks again, @Ikalus1988.

docs: update the roadmap, and report issue/PR state with numbers (+895 lines, 3 files)

Quick question — did any MisakaNet lesson help you this time?
→ Share feedback

No need to reply if nothing comes to mind. ⚡

@Ikalus1988 Ikalus1988 mentioned this pull request Sep 19, 2026
Merged
@github-actions github-actions Bot mentioned this pull request Sep 22, 2026
Merged
@Ikalus1988
Ikalus1988 deleted the docs/roadmap-2026-09-16 branch September 27, 2026 17:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

area:docs docs-only Only documentation files changed Review effort 2/5 shape-safe

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@Ikalus1988