Design enforceable per-module reconciliation intent artifacts
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- javascript
- 领域
- devtools
调研方向
Start by reviewing roadmap item B04-01 and dependency #17, then map the existing guidance and apply flow to identify where intent is resolved and enforced. Draft an artifact schema bound to each module’s target, discovery inputs, and apply/adapt/leave decision; define rejection behavior for missing or mismatched intent and verification that leave causes zero writes or creates. Done means the design review covers these cases; runtime behavior remains unchanged until a prototype is approved.
由索引模型根据 Issue 内容生成。
描述
Goal
Design a per-module apply/adapt/leave intent artifact bound to its target and discovery inputs, replacing LLM-only guidance with an enforceable record.
Observations
- Current guidance is LLM-only; the backend does not record intent.
- A plain
approved:trueflag is not human proof and must not gate enforcement. - Leave must produce zero writes or creates, including for missing state;
managed:falsealone still creates missing state and is not a way to encode leave.
Decision gate
Approve the design before any code. Controls come from an actor's exact decision, never a guessed CLI flag.
Acceptance criteria
- Every module resolves to one explicit apply/adapt/leave intent bound to its target and discovery inputs.
- Leave produces zero writes or creates, including for missing state.
-
managed:falsealone is not treated as leave and never falsely reports a module as off.
Verification
- Design review -> the artifact schema covers target, discovery inputs, and per-module decision.
- Prototype -> a missing or mismatched intent is rejected; leave performs zero writes.
Release checkpoint
Remaining risk: design alone changes no runtime behavior. The final-SHA apply gate stays in place.
Tracking
Roadmap item: B04-01. All acceptance criteria remain pending; publication does not grant approval or release authority.
Dependencies
- Depends on #17 (B02-02).
- 主要语言
- JavaScript
- 星标
- 22
- 派生
- 3
- 平均合并
- 27 分钟
- 30 天内合并 PR
- 27
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
egdev6/github-repository-bootstrap 的其他 Issue
-
status:approved type:chore
难度 5/5 一周以上 新手友好度 25/100
egdev6/github-repository-bootstrap#57 ·
维护者通常 1 天内回复
-
type:docs
难度 1/5 1 小时以内 新手友好度 20/100
egdev6/github-repository-bootstrap#50 ·
维护者通常 1 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 22/100
egdev6/github-repository-bootstrap#49 ·
维护者通常 1 天内回复
-
status:approved type:chore
难度 5/5 一周以上 新手友好度 25/100
egdev6/github-repository-bootstrap#30 ·
维护者通常 1 天内回复
-
status:approved type:chore
难度 5/5 一周以上 新手友好度 42/100
egdev6/github-repository-bootstrap#29 ·
维护者通常 1 天内回复
查看 egdev6/github-repository-bootstrap 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 8 天内回复
-
docs(stream-protocol): document messageMetatadata on start/finish and the message-metadata chunk可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭factory-active task-identify-harness-labels-done task-identify-issue-type-done
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
feature request
难度 1/5 1 小时以内 新手友好度 88/100
维护者通常 1 天内回复
-
docs hacktoberfest help wanted
难度 2/5 1-3 小时 新手友好度 85/100
pacocartones/free-llm-api-hub#347 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
wpilibsuite/wpilib-docs#3378 ·
维护者通常 1 天内回复