maogeigei
d3f98dda77
- 工作台大版本升级：hash 路由 + 6 数据功能页（周榜/热门账号/账号详情/视频详情/AI写脚本/AI写作复盘），只读复用 dsh 库副本 + 抖音榜单 JSON - 数据库隔离：复制 dsh 库到 mcn-work-shop/，与 dsh 原库各访问各的（已 gitignore） - 图标全面扁平化：Lucide 线性 SVG，功能图标亮色区分，文字标题去图标 - 首页重构：功能入口卡 + AI写剧本快捷卡片(2列/8个/5行预览) + 独立帮助页 + header 精简 - 新增设计技能 impeccable + taste-skill（生成网页时参考） - 修复：fmtTime 跨 script 全局冲突(P0)、弹窗关闭、外链新标签打开等
4.6 KiB
Report and repair drift between this project's Impeccable artifacts and what the installed version reads: PRODUCT.md, DESIGN.md and its .impeccable/design.json sidecar, .impeccable/config.json, persisted surface briefs, and the design hook.
This is maintenance, not design. Do not redesign anything, do not open files outside the ones the report names, and do not run any other command as a side effect.
What this owns, and what it does not
Three kinds of drift travel under "out of date". Keep them apart:
- Tool version. The installed skill is older than the published one.
context.mjsreports that at boot asUPDATE_AVAILABLEandnpx impeccable updatefixes it. Not this command's job. - Schema drift. An artifact was written by an older Impeccable: fields nothing reads, fields now expected, files in retired locations. Mechanical, and this command repairs most of it.
- Truth drift. The code moved on and the document no longer describes it. No file comparison settles this.
documentowns DESIGN.md,initowns PRODUCT.md, and this command's job is to hand them a specific gap rather than a vague suspicion.
Step 1: Run the pass
node {{scripts_path}}/doctor.mjs --json
Add --target <path> when the user named a workspace, file, or route in a monorepo. Without it the report describes the repo root, and in a monorepo that is often the wrong project.
The output carries findings (each with id, artifact, path, severity, summary, fix) and, in a monorepo, workspaces with each app's product and design resolution. ruleRegistryAvailable: false means ignored rule ids could not be validated; say so rather than implying that list is clean.
An empty findings array is the good outcome. Say so in one line and stop.
Step 2: Act by severity
The severity says what should happen, not how bad it is.
autocarries no decision. Runnode {{scripts_path}}/doctor.mjs --fixonce to apply these, then report what it moved in one line. Do not ask permission first, and do not ask about them afterward.mentionneeds the user to know but not to decide anything now. State each one in a sentence with its offered fix.routeneeds a specific command. Name the command and the gap it would close. Run it only if the user asks in this turn;initanddocumentare conversations, not repairs you perform unattended.
Report all three groups in one pass. Findings are not errors and the command does not fail on them.
Step 3: Deprecated fields are binding
A finding that reports a deprecated field (## Register is the current one) is not a style note. Treat that field as absent for every decision from here on, whatever value it holds, and offer to delete the section. Preserving it "just in case" is how a retired axis keeps steering current output.
Step 4: Do not overclaim on truth drift
design-md-drift counts commits to the visual source directories since DESIGN.md was last edited. A commit count is not a contradiction. Report the number, say what it measures, and if the user wants to know whether the document is actually wrong, read DESIGN.md against the current tokens and components and answer from that. Never assert that DESIGN.md is stale because the number is large.
The same restraint applies to workspace-context-inherited. Inheritance is a designed behavior. Whether one product record truthfully describes several apps is a question for the user, not a defect to fix.
Monorepo notes
workspace-platform-native-evidenceis the finding that matters most here: a workspace carrying native build files while inheriting a root record that resolves to web gets web guidance for its whole life and never loads ios.md or android.md. The repair is a child PRODUCT.md in that workspace, because one inherited record cannot hold two platforms.config-project-roots-match-nothingmeans everyprojectRootsglob missed, so the repo root is silently standing in as the active project. A renamed workspace directory is the usual cause. Report the patterns and ask which directories they should name.- Use the
workspacestable to show the user which apps carry their own context, which inherit, and which have none, before proposing any change.
Opting out of the boot check
context.mjs reports the cheap subset of these findings at session start, throttled to once a week per project. Set "stalenessCheck": false in .impeccable/config.json to silence that, or IMPECCABLE_NO_STALENESS_CHECK=1 for one session. This command still works with the check disabled, and that is the combination to suggest for a user who wants the report only when they ask for it.