codecartographer-pi 0.9.1 → 0.11.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.codecarto/GUIDE.md +10 -3
- package/.codecarto/findings/porting/SKILL.md +7 -0
- package/.codecarto/findings/reimplementation-spec/SKILL.md +10 -0
- package/.codecarto/templates/architecture-map.md +9 -0
- package/.codecarto/templates/behavioral-contracts.md +9 -0
- package/.codecarto/templates/defect-report.md +9 -0
- package/.codecarto/templates/mechanical-defects.md +9 -0
- package/.codecarto/templates/phase-checkpoint.md +41 -0
- package/.codecarto/templates/protocols-and-state.md +9 -0
- package/.codecarto/templates/reimplementation-spec-opinionated.md +10 -0
- package/.codecarto/templates/reimplementation-spec.md +10 -0
- package/.codecarto/templates/reverse-engineering-bundle.md +29 -3
- package/.codecarto/templates/semantic-defects.md +9 -0
- package/.codecarto/workflow/pipeline-architecture-only.yaml +1 -0
- package/.codecarto/workflow/pipeline-defect-scan.yaml +2 -0
- package/.codecarto/workflow/pipeline-full-with-audit.yaml +8 -3
- package/.codecarto/workflow/pipeline-full-with-deep-audit.yaml +9 -5
- package/.codecarto/workflow/pipeline-lite.yaml +3 -0
- package/.codecarto/workflow/pipeline.yaml +7 -3
- package/README.md +38 -2
- package/dist/core/dashboard.js +178 -15
- package/dist/core/prompts.js +6 -0
- package/dist/core/usage.d.ts +11 -0
- package/dist/core/usage.js +64 -46
- package/dist/extensions/codecarto/agent-rewriter.js +0 -1
- package/dist/extensions/codecarto/agent-runner.d.ts +19 -0
- package/dist/extensions/codecarto/agent-runner.js +68 -6
- package/dist/extensions/codecarto/agent-state.d.ts +3 -0
- package/dist/extensions/codecarto/agent-state.js +2 -0
- package/dist/extensions/codecarto/agent-summary.d.ts +5 -0
- package/dist/extensions/codecarto/agent-summary.js +9 -0
- package/dist/extensions/codecarto/agent-widget.js +6 -0
- package/dist/extensions/codecarto/auto-runner.js +13 -1
- package/dist/extensions/codecarto/dashboard-narrator.js +0 -1
- package/dist/extensions/codecarto/index.d.ts +1 -1
- package/dist/extensions/codecarto/index.js +28 -1
- package/dist/extensions/codecarto/phase-compaction.d.ts +11 -0
- package/dist/extensions/codecarto/phase-compaction.js +115 -0
- package/package.json +2 -2
package/.codecarto/GUIDE.md
CHANGED
|
@@ -55,8 +55,9 @@ Read these files in order before doing any analysis:
|
|
|
55
55
|
1. This `GUIDE.md` (you are here — `.codecarto/GUIDE.md`).
|
|
56
56
|
2. `workflow/status.yaml` to see which phases are done and what is next.
|
|
57
57
|
3. The current phase's existing output file, if one exists (to avoid repeating work).
|
|
58
|
-
4.
|
|
59
|
-
5. The
|
|
58
|
+
4. `scratch/checkpoints/<phase>.md`, if present, to resume durable in-phase progress after compaction or interruption.
|
|
59
|
+
5. The current phase's `SKILL.md` for detailed instructions on what to analyze and produce.
|
|
60
|
+
6. The output template from `templates/` for the current phase (if starting a new output).
|
|
60
61
|
|
|
61
62
|
All paths in this guide are relative to `.codecarto/` unless stated otherwise.
|
|
62
63
|
|
|
@@ -81,7 +82,7 @@ Some files in this workspace are **read-only instructions** and must not be modi
|
|
|
81
82
|
| Conventions (orchestrator-maintained) | `CONVENTIONS.md` | Cross-cutting patterns promoted to project-wide invariants. Implementing sessions propose; the orchestrator writes. |
|
|
82
83
|
| Decisions (orchestrator-maintained, append-only) | `DECISIONS.md` | Numbered log of decisions that diverge from spec, prompt, or obvious-default. Appended at session close. |
|
|
83
84
|
| Backlog (read-write) | `BACKLOG.md` | Deferred items with rationale. |
|
|
84
|
-
| Scratch (read-write) | `scratch/*` |
|
|
85
|
+
| Scratch (read-write) | `scratch/*` | Working notes; `scratch/checkpoints/<phase>.md` is the durable in-phase continuation checkpoint until the phase validates. |
|
|
85
86
|
|
|
86
87
|
If you are uncertain whether a file should be modified, treat it as read-only.
|
|
87
88
|
|
|
@@ -158,8 +159,14 @@ Before beginning a phase, estimate how much source material you need to read. Fo
|
|
|
158
159
|
- Read structural files first (manifests, entrypoints, READMEs) from the repository root (`../`).
|
|
159
160
|
- Use the architecture map to prioritize which packages to read in detail.
|
|
160
161
|
- Defer deep reads until the current phase actually needs them.
|
|
162
|
+
- For long phases, update `scratch/checkpoints/<phase>.md` after each major subsystem or output section. Pi writes a phase-aware checkpoint automatically after phase compaction; other hosts should use `templates/phase-checkpoint.md` manually.
|
|
163
|
+
- Every primary output must include `Coverage and limits`: inspected scope, skipped scope, evidence basis, known blind spots, and a `COMPLETE` or `PARTIAL` disposition.
|
|
161
164
|
- If you are running low on context, finish the current section, write a PARTIAL validation, and document what remains in `open_questions` (truly unknown) or `carry_forward` (deferred to a specific later phase) in status.yaml. See "Open Questions vs Carry-Forward" below.
|
|
162
165
|
|
|
166
|
+
### Synthesis compression boundary
|
|
167
|
+
|
|
168
|
+
The porting bundle is the intentional compression boundary before `reimplementation-spec`. Its Source Index must preserve load-bearing claims, defect dispositions, coverage gaps, and exact pointers for targeted deep reads. The final synthesis phase reads the bundle by default; it opens architecture, contracts, protocols, or defect reports only when the bundle names a gap or conflict, an acceptance scenario needs omitted detail, a claim needs stronger evidence, or a defect disposition needs its rationale. If the bundle cannot support that selective workflow, mark validation `PARTIAL` instead of loading every upstream report by habit.
|
|
169
|
+
|
|
163
170
|
### Subagent Delegation for Large Codebases
|
|
164
171
|
|
|
165
172
|
For codebases over roughly 50 source files or 100K LOC, do not burn primary context on bulk extraction work. Delegate dependency mapping, file inventories, manifest enumeration, and cross-document comparisons to subagents and cite their scratch artifacts (`scratch/<topic>.md`) from the primary output. The primary session reads the synthesized scratch note, not the raw walks. Bless this pattern explicitly so primary context stays for the load-bearing reasoning that the subagent can't do — naming layers, pinning invariants, classifying findings.
|
|
@@ -7,6 +7,12 @@ description: Synthesize architecture, contracts, and protocol findings into a re
|
|
|
7
7
|
|
|
8
8
|
This phase synthesizes the outputs of architecture, contracts, and protocols. If defect reports exist, also read and integrate them: `findings/defect-scan/defect-report.md` (full-with-audit pipeline) or both `findings/defect-scan-mechanical/mechanical-defects.md` and `findings/defect-scan-semantic/semantic-defects.md` (full-with-deep-audit pipeline). The pipeline ensures all required phases are complete before this one runs. Read the prior phase artifacts before starting.
|
|
9
9
|
|
|
10
|
+
Treat the reverse-engineering bundle as the pipeline's intentional compression boundary. It must be self-sufficient enough for `reimplementation-spec` to start from this one artifact rather than loading every upstream report. Preserve compact source pointers instead of copying upstream prose:
|
|
11
|
+
- Add a Source Index covering architecture, contracts, protocols/state, and defects when present.
|
|
12
|
+
- Carry forward every load-bearing invariant, acceptance obligation, compatibility hazard, and defect disposition.
|
|
13
|
+
- For omitted detail, name the canonical upstream section and the exact condition that should trigger a targeted deep read.
|
|
14
|
+
- Surface conflicts and incomplete coverage explicitly; never hide them behind synthesis.
|
|
15
|
+
|
|
10
16
|
The source code to analyze is in the parent directory (`../` relative to `.codecarto/`). This is the repository root.
|
|
11
17
|
|
|
12
18
|
Keep four classes of findings separate throughout:
|
|
@@ -43,6 +49,7 @@ Use the output template at `templates/reverse-engineering-bundle.md`. Produce:
|
|
|
43
49
|
- A protocol and state note set.
|
|
44
50
|
- Portability hazards consolidated from all prior phases.
|
|
45
51
|
- Observed facts separated from inferred structure.
|
|
52
|
+
- A compact Source Index and explicit coverage gaps that let downstream synthesis deep-read selectively.
|
|
46
53
|
|
|
47
54
|
Bias toward evidence over cleverness:
|
|
48
55
|
- Prefer tests over assumptions.
|
|
@@ -7,6 +7,14 @@ description: Convert reverse-engineering findings into a language-agnostic reimp
|
|
|
7
7
|
|
|
8
8
|
Use this skill after the architecture, behavior, and protocol passes are complete enough to trust.
|
|
9
9
|
|
|
10
|
+
Start with `findings/porting/reverse-engineering-bundle.md`; it is the default compression boundary for this phase. Do not load every lower-level finding automatically. Follow the bundle's Source Index and deep-read architecture, contracts, protocols, or defect reports only when:
|
|
11
|
+
- the bundle names a gap or conflict,
|
|
12
|
+
- an acceptance scenario needs detail the bundle deliberately omitted,
|
|
13
|
+
- a load-bearing claim lacks enough evidence to state safely, or
|
|
14
|
+
- a defect disposition needs its original rationale.
|
|
15
|
+
|
|
16
|
+
Record those targeted deep reads in the spec's Coverage and limits section. If the bundle is not self-sufficient, mark the affected validation criterion PARTIAL and route the gap through `open_questions` or `carry_forward` rather than silently reconstructing the whole pipeline in context.
|
|
17
|
+
|
|
10
18
|
Treat the source repo as evidence, not as a template.
|
|
11
19
|
|
|
12
20
|
Define concept-level modules:
|
|
@@ -61,6 +69,8 @@ End with a spike list:
|
|
|
61
69
|
- risky performance assumptions
|
|
62
70
|
- platform-sensitive areas that need targeted tests
|
|
63
71
|
|
|
72
|
+
For every defect in the bundle, preserve its disposition (`fix before porting`, `port differently`, or `leave behind`) and convert it into an explicit design consequence or acceptance check.
|
|
73
|
+
|
|
64
74
|
Use the output template at `templates/reimplementation-spec.md`.
|
|
65
75
|
|
|
66
76
|
The source code to analyze is in the parent directory (`../` relative to `.codecarto/`). This is the repository root.
|
|
@@ -104,6 +104,14 @@
|
|
|
104
104
|
logs, caches, databases, generated artifacts.
|
|
105
105
|
-->
|
|
106
106
|
|
|
107
|
+
## Coverage and limits
|
|
108
|
+
|
|
109
|
+
- Inspected scope:
|
|
110
|
+
- Skipped scope:
|
|
111
|
+
- Evidence basis: source inspection | tests | runtime verification | upstream findings
|
|
112
|
+
- Known blind spots:
|
|
113
|
+
- Coverage disposition: COMPLETE | PARTIAL
|
|
114
|
+
|
|
107
115
|
## Open Questions
|
|
108
116
|
|
|
109
117
|
<!-- Items that are still genuinely unknown — need a runtime test, maintainer decision, or spec ruling.
|
|
@@ -138,6 +146,7 @@
|
|
|
138
146
|
| 3 | Public surfaces are identified. | PASS / PARTIAL / FAIL | |
|
|
139
147
|
| 4 | Runtime lifecycle, concurrency model, and porting priorities are summarized. | PASS / PARTIAL / FAIL | |
|
|
140
148
|
| 5 | Findings are marked with evidence levels. | PASS / PARTIAL / FAIL | |
|
|
149
|
+
| 6 | Coverage and limits name inspected scope, skipped scope, evidence basis, and blind spots. | PASS / PARTIAL / FAIL | |
|
|
141
150
|
|
|
142
151
|
**Validated by:** [session identifier or date]
|
|
143
152
|
**Overall:** PASS / PASS WITH GAPS / FAIL
|
|
@@ -91,6 +91,14 @@
|
|
|
91
91
|
|---|----------|--------------|--------|------------------|
|
|
92
92
|
| 1 | | | | |
|
|
93
93
|
|
|
94
|
+
## Coverage and limits
|
|
95
|
+
|
|
96
|
+
- Inspected scope:
|
|
97
|
+
- Skipped scope:
|
|
98
|
+
- Evidence basis: source inspection | tests | runtime verification | upstream findings
|
|
99
|
+
- Known blind spots:
|
|
100
|
+
- Coverage disposition: COMPLETE | PARTIAL
|
|
101
|
+
|
|
94
102
|
## Open Questions
|
|
95
103
|
|
|
96
104
|
<!-- Items that are still genuinely unknown — need a runtime test, maintainer decision, or spec ruling.
|
|
@@ -129,6 +137,7 @@
|
|
|
129
137
|
| 4 | Contract ownership is mapped back to a layer or package. | PASS / PARTIAL / FAIL | |
|
|
130
138
|
| 5 | A black-box acceptance list is included. | PASS / PARTIAL / FAIL | |
|
|
131
139
|
| 6 | Findings are marked with evidence levels. | PASS / PARTIAL / FAIL | |
|
|
140
|
+
| 7 | Coverage and limits name inspected scope, skipped scope, evidence basis, and blind spots. | PASS / PARTIAL / FAIL | |
|
|
132
141
|
|
|
133
142
|
**Validated by:** [session identifier or date]
|
|
134
143
|
**Overall:** PASS / PASS WITH GAPS / FAIL
|
|
@@ -99,6 +99,14 @@
|
|
|
99
99
|
|
|
100
100
|
---
|
|
101
101
|
|
|
102
|
+
## Coverage and limits
|
|
103
|
+
|
|
104
|
+
- Inspected scope:
|
|
105
|
+
- Skipped scope:
|
|
106
|
+
- Evidence basis: source inspection | tests | runtime verification | upstream findings
|
|
107
|
+
- Known blind spots:
|
|
108
|
+
- Coverage disposition: COMPLETE | PARTIAL
|
|
109
|
+
|
|
102
110
|
## Validation
|
|
103
111
|
|
|
104
112
|
<!-- Fill in this table per workflow/VALIDATE.md. The rows below match the full pipeline.
|
|
@@ -111,6 +119,7 @@
|
|
|
111
119
|
| 3 | Findings are organized by pass and sorted by severity. | PASS / PARTIAL / FAIL | |
|
|
112
120
|
| 4 | Summary tables are complete and counts match the detailed findings. | PASS / PARTIAL / FAIL | |
|
|
113
121
|
| 5 | Findings are marked with evidence levels. | PASS / PARTIAL / FAIL | |
|
|
122
|
+
| 6 | Coverage and limits name inspected scope, skipped scope, evidence basis, and blind spots. | PASS / PARTIAL / FAIL | |
|
|
114
123
|
|
|
115
124
|
**Validated by:** [session identifier or date]
|
|
116
125
|
**Overall:** PASS / PASS WITH GAPS / FAIL
|
|
@@ -88,6 +88,14 @@
|
|
|
88
88
|
|
|
89
89
|
---
|
|
90
90
|
|
|
91
|
+
## Coverage and limits
|
|
92
|
+
|
|
93
|
+
- Inspected scope:
|
|
94
|
+
- Skipped scope:
|
|
95
|
+
- Evidence basis: source inspection | tests | runtime verification | upstream findings
|
|
96
|
+
- Known blind spots:
|
|
97
|
+
- Coverage disposition: COMPLETE | PARTIAL
|
|
98
|
+
|
|
91
99
|
## Validation
|
|
92
100
|
|
|
93
101
|
<!-- Fill in this table per workflow/VALIDATE.md. The rows below match the mechanical-pass scope. -->
|
|
@@ -99,6 +107,7 @@
|
|
|
99
107
|
| 3 | Findings are organized by pass and sorted by severity. | PASS / PARTIAL / FAIL | |
|
|
100
108
|
| 4 | Summary tables are complete and counts match the detailed findings. | PASS / PARTIAL / FAIL | |
|
|
101
109
|
| 5 | Findings are marked with evidence levels. | PASS / PARTIAL / FAIL | |
|
|
110
|
+
| 6 | Coverage and limits name inspected scope, skipped scope, evidence basis, and blind spots. | PASS / PARTIAL / FAIL | |
|
|
102
111
|
|
|
103
112
|
**Validated by:** [session identifier or date]
|
|
104
113
|
**Overall:** PASS / PASS WITH GAPS / FAIL
|
|
@@ -0,0 +1,41 @@
|
|
|
1
|
+
---
|
|
2
|
+
phase: <phase-id>
|
|
3
|
+
updated_at: <ISO-8601 timestamp>
|
|
4
|
+
source: manual | pi-compaction
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# Phase checkpoint
|
|
8
|
+
|
|
9
|
+
## Goal and output
|
|
10
|
+
|
|
11
|
+
- Phase:
|
|
12
|
+
- Primary output:
|
|
13
|
+
- Current objective:
|
|
14
|
+
|
|
15
|
+
## Evidence established
|
|
16
|
+
|
|
17
|
+
<!-- Preserve evidence levels and exact source paths. -->
|
|
18
|
+
|
|
19
|
+
## Files and subsystems inspected
|
|
20
|
+
|
|
21
|
+
- Inspected:
|
|
22
|
+
- Not yet inspected:
|
|
23
|
+
|
|
24
|
+
## Output progress
|
|
25
|
+
|
|
26
|
+
- Sections complete:
|
|
27
|
+
- Sections remaining:
|
|
28
|
+
|
|
29
|
+
## Open questions and carry-forward candidates
|
|
30
|
+
|
|
31
|
+
- Open questions:
|
|
32
|
+
- Carry-forward:
|
|
33
|
+
|
|
34
|
+
## Validation gaps
|
|
35
|
+
|
|
36
|
+
- Criteria satisfied:
|
|
37
|
+
- Criteria at risk:
|
|
38
|
+
|
|
39
|
+
## Exact next steps
|
|
40
|
+
|
|
41
|
+
1.
|
|
@@ -86,6 +86,14 @@
|
|
|
86
86
|
|---|---|---|---|
|
|
87
87
|
| | | | |
|
|
88
88
|
|
|
89
|
+
## Coverage and limits
|
|
90
|
+
|
|
91
|
+
- Inspected scope:
|
|
92
|
+
- Skipped scope:
|
|
93
|
+
- Evidence basis: source inspection | tests | runtime verification | upstream findings
|
|
94
|
+
- Known blind spots:
|
|
95
|
+
- Coverage disposition: COMPLETE | PARTIAL
|
|
96
|
+
|
|
89
97
|
## Open Questions
|
|
90
98
|
|
|
91
99
|
<!-- Items that are still genuinely unknown — need a runtime test, maintainer decision, or spec ruling.
|
|
@@ -121,6 +129,7 @@
|
|
|
121
129
|
| 3 | Persistent schema notes are documented. | PASS / PARTIAL / FAIL | |
|
|
122
130
|
| 4 | Compatibility hazards are documented. | PASS / PARTIAL / FAIL | |
|
|
123
131
|
| 5 | Findings are marked with evidence levels. | PASS / PARTIAL / FAIL | |
|
|
132
|
+
| 6 | Coverage and limits name inspected scope, skipped scope, evidence basis, and blind spots. | PASS / PARTIAL / FAIL | |
|
|
124
133
|
|
|
125
134
|
**Validated by:** [session identifier or date]
|
|
126
135
|
**Overall:** PASS / PASS WITH GAPS / FAIL
|
|
@@ -146,6 +146,14 @@
|
|
|
146
146
|
integrations that will be stubbed first.
|
|
147
147
|
-->
|
|
148
148
|
|
|
149
|
+
## Coverage and limits
|
|
150
|
+
|
|
151
|
+
- Inspected scope:
|
|
152
|
+
- Skipped scope:
|
|
153
|
+
- Evidence basis: source inspection | tests | runtime verification | upstream findings
|
|
154
|
+
- Known blind spots:
|
|
155
|
+
- Coverage disposition: COMPLETE | PARTIAL
|
|
156
|
+
|
|
149
157
|
## Known Unknowns
|
|
150
158
|
|
|
151
159
|
<!-- Items that are still genuinely unknown — need a prototype, runtime test, maintainer decision,
|
|
@@ -178,6 +186,8 @@
|
|
|
178
186
|
| 3 | Protocol and persisted state expectations are stated. | PASS / PARTIAL / FAIL | |
|
|
179
187
|
| 4 | Acceptance scenarios and known unknowns are included. | PASS / PARTIAL / FAIL | |
|
|
180
188
|
| 5 | Findings are marked with evidence levels. | PASS / PARTIAL / FAIL | |
|
|
189
|
+
| 6 | Coverage and limits name inspected scope, skipped scope, evidence basis, and blind spots. | PASS / PARTIAL / FAIL | |
|
|
190
|
+
| 7 | Lower-level findings are deep-read only when the porting bundle identifies a gap, conflict, missing acceptance detail, or defect rationale. | PASS / PARTIAL / FAIL | |
|
|
181
191
|
|
|
182
192
|
**Validated by:** [session identifier or date]
|
|
183
193
|
**Overall:** PASS / PASS WITH GAPS / FAIL
|
|
@@ -99,6 +99,14 @@
|
|
|
99
99
|
integrations that will be stubbed first.
|
|
100
100
|
-->
|
|
101
101
|
|
|
102
|
+
## Coverage and limits
|
|
103
|
+
|
|
104
|
+
- Inspected scope:
|
|
105
|
+
- Skipped scope:
|
|
106
|
+
- Evidence basis: source inspection | tests | runtime verification | upstream findings
|
|
107
|
+
- Known blind spots:
|
|
108
|
+
- Coverage disposition: COMPLETE | PARTIAL
|
|
109
|
+
|
|
102
110
|
## Known Unknowns
|
|
103
111
|
|
|
104
112
|
<!-- Items that are still genuinely unknown — need a prototype, runtime test, maintainer decision, or spec ruling.
|
|
@@ -143,6 +151,8 @@
|
|
|
143
151
|
| 3 | Protocol and persisted state expectations are stated. | PASS / PARTIAL / FAIL | |
|
|
144
152
|
| 4 | Acceptance scenarios and known unknowns are included. | PASS / PARTIAL / FAIL | |
|
|
145
153
|
| 5 | Findings are marked with evidence levels. | PASS / PARTIAL / FAIL | |
|
|
154
|
+
| 6 | Coverage and limits name inspected scope, skipped scope, evidence basis, and blind spots. | PASS / PARTIAL / FAIL | |
|
|
155
|
+
| 7 | Lower-level findings are deep-read only when the porting bundle identifies a gap, conflict, missing acceptance detail, or defect rationale. | PASS / PARTIAL / FAIL | |
|
|
146
156
|
|
|
147
157
|
**Validated by:** [session identifier or date]
|
|
148
158
|
**Overall:** PASS / PASS WITH GAPS / FAIL
|
|
@@ -10,6 +10,22 @@
|
|
|
10
10
|
|
|
11
11
|
<!-- One to three paragraphs summarizing the system in plain language, aimed at someone who will reimplement it. -->
|
|
12
12
|
|
|
13
|
+
## Source Index
|
|
14
|
+
|
|
15
|
+
<!--
|
|
16
|
+
This bundle is the default compression boundary for reimplementation-spec.
|
|
17
|
+
Point to the canonical upstream section for every load-bearing claim. A later
|
|
18
|
+
phase should deep-read an upstream report only when this index identifies a
|
|
19
|
+
gap, conflict, or detail that cannot be represented responsibly here.
|
|
20
|
+
-->
|
|
21
|
+
|
|
22
|
+
| Area | Canonical upstream section | Summary carried forward | Deep-read trigger |
|
|
23
|
+
|---|---|---|---|
|
|
24
|
+
| Architecture | | | |
|
|
25
|
+
| Contracts | | | |
|
|
26
|
+
| Protocols and state | | | |
|
|
27
|
+
| Defects (if scanned) | | | |
|
|
28
|
+
|
|
13
29
|
## Layer Map With Ownership
|
|
14
30
|
|
|
15
31
|
<!--
|
|
@@ -68,9 +84,9 @@
|
|
|
68
84
|
re-list every finding. Keep it under one screen.
|
|
69
85
|
-->
|
|
70
86
|
|
|
71
|
-
| Defect ID | Source Report | One-line Description | Severity |
|
|
72
|
-
|
|
73
|
-
| | | | | fix before porting / port differently / leave behind |
|
|
87
|
+
| Defect ID | Source Report | One-line Description | Severity | Disposition | Required design consequence |
|
|
88
|
+
|-----------|---------------|----------------------|----------|-------------|-----------------------------|
|
|
89
|
+
| | | | | fix before porting / port differently / leave behind | |
|
|
74
90
|
|
|
75
91
|
## Observed Facts vs. Inferred Structure
|
|
76
92
|
|
|
@@ -101,6 +117,14 @@
|
|
|
101
117
|
|---|---|---|
|
|
102
118
|
| | | |
|
|
103
119
|
|
|
120
|
+
## Coverage and limits
|
|
121
|
+
|
|
122
|
+
- Inspected scope:
|
|
123
|
+
- Skipped scope:
|
|
124
|
+
- Evidence basis: source inspection | tests | runtime verification | upstream findings
|
|
125
|
+
- Known blind spots:
|
|
126
|
+
- Coverage disposition: COMPLETE | PARTIAL
|
|
127
|
+
|
|
104
128
|
## Open Questions
|
|
105
129
|
|
|
106
130
|
<!-- Items that are still genuinely unknown — need a runtime test, maintainer decision, or spec ruling.
|
|
@@ -136,6 +160,8 @@
|
|
|
136
160
|
| 3 | Feature importance is sorted for porting. | PASS / PARTIAL / FAIL | |
|
|
137
161
|
| 4 | Known defects are referenced in the Defect Synthesis with porting recommendations (fix before porting / port differently / leave behind), or the section explicitly notes that no defect scan ran. | PASS / PARTIAL / FAIL | |
|
|
138
162
|
| 5 | Findings are marked with evidence levels. | PASS / PARTIAL / FAIL | |
|
|
163
|
+
| 6 | Coverage and limits name inspected scope, skipped scope, evidence basis, and blind spots. | PASS / PARTIAL / FAIL | |
|
|
164
|
+
| 7 | The Source Index makes the bundle a self-contained compression boundary and identifies targeted deep-read triggers. | PASS / PARTIAL / FAIL | |
|
|
139
165
|
|
|
140
166
|
**Validated by:** [session identifier or date]
|
|
141
167
|
**Overall:** PASS / PASS WITH GAPS / FAIL
|
|
@@ -93,6 +93,14 @@
|
|
|
93
93
|
|
|
94
94
|
---
|
|
95
95
|
|
|
96
|
+
## Coverage and limits
|
|
97
|
+
|
|
98
|
+
- Inspected scope:
|
|
99
|
+
- Skipped scope:
|
|
100
|
+
- Evidence basis: source inspection | tests | runtime verification | upstream findings
|
|
101
|
+
- Known blind spots:
|
|
102
|
+
- Coverage disposition: COMPLETE | PARTIAL
|
|
103
|
+
|
|
96
104
|
## Validation
|
|
97
105
|
|
|
98
106
|
<!-- Fill in this table per workflow/VALIDATE.md. The rows below match the semantic-pass scope. -->
|
|
@@ -104,6 +112,7 @@
|
|
|
104
112
|
| 3 | Pass 5 findings cite the contract or protocol reference they violate. | PASS / PARTIAL / FAIL | |
|
|
105
113
|
| 4 | Findings are organized by pass and sorted by severity; summary tables match the detailed findings. | PASS / PARTIAL / FAIL | |
|
|
106
114
|
| 5 | Findings are marked with evidence levels. | PASS / PARTIAL / FAIL | |
|
|
115
|
+
| 6 | Coverage and limits name inspected scope, skipped scope, evidence basis, and blind spots. | PASS / PARTIAL / FAIL | |
|
|
107
116
|
|
|
108
117
|
**Validated by:** [session identifier or date]
|
|
109
118
|
**Overall:** PASS / PASS WITH GAPS / FAIL
|
|
@@ -32,6 +32,7 @@ phases:
|
|
|
32
32
|
- Public surfaces are identified.
|
|
33
33
|
- Runtime lifecycle, concurrency model, and porting priorities are summarized.
|
|
34
34
|
- Findings are marked with evidence levels.
|
|
35
|
+
- Coverage and limits name inspected scope, skipped scope, evidence basis, and blind spots.
|
|
35
36
|
handoff_requirements:
|
|
36
37
|
- Run validation per workflow/VALIDATE.md. Append validation block to primary output.
|
|
37
38
|
- Update workflow/status.yaml.
|
|
@@ -33,6 +33,7 @@ phases:
|
|
|
33
33
|
- Public surfaces are identified.
|
|
34
34
|
- Runtime lifecycle, concurrency model, and porting priorities are summarized.
|
|
35
35
|
- Findings are marked with evidence levels.
|
|
36
|
+
- Coverage and limits name inspected scope, skipped scope, evidence basis, and blind spots.
|
|
36
37
|
handoff_requirements:
|
|
37
38
|
- Run validation per workflow/VALIDATE.md. Append validation block to primary output.
|
|
38
39
|
- Update workflow/status.yaml.
|
|
@@ -55,6 +56,7 @@ phases:
|
|
|
55
56
|
- Findings are organized by pass and sorted by severity.
|
|
56
57
|
- Summary tables are complete and counts match the detailed findings.
|
|
57
58
|
- Findings are marked with evidence levels.
|
|
59
|
+
- Coverage and limits name inspected scope, skipped scope, evidence basis, and blind spots.
|
|
58
60
|
handoff_requirements:
|
|
59
61
|
- Run validation per workflow/VALIDATE.md. Append validation block to primary output.
|
|
60
62
|
- Update workflow/status.yaml.
|
|
@@ -37,6 +37,7 @@ phases:
|
|
|
37
37
|
- Public surfaces are identified.
|
|
38
38
|
- Runtime lifecycle, concurrency model, and porting priorities are summarized.
|
|
39
39
|
- Findings are marked with evidence levels.
|
|
40
|
+
- Coverage and limits name inspected scope, skipped scope, evidence basis, and blind spots.
|
|
40
41
|
handoff_requirements:
|
|
41
42
|
- Run validation per workflow/VALIDATE.md. Append validation block to primary output.
|
|
42
43
|
- Update workflow/status.yaml.
|
|
@@ -59,6 +60,7 @@ phases:
|
|
|
59
60
|
- Findings are organized by pass and sorted by severity.
|
|
60
61
|
- Summary tables are complete and counts match the detailed findings.
|
|
61
62
|
- Findings are marked with evidence levels.
|
|
63
|
+
- Coverage and limits name inspected scope, skipped scope, evidence basis, and blind spots.
|
|
62
64
|
handoff_requirements:
|
|
63
65
|
- Run validation per workflow/VALIDATE.md. Append validation block to primary output.
|
|
64
66
|
- Update workflow/status.yaml.
|
|
@@ -90,6 +92,7 @@ phases:
|
|
|
90
92
|
- Contract ownership is mapped back to a layer or package.
|
|
91
93
|
- A black-box acceptance list is included.
|
|
92
94
|
- Findings are marked with evidence levels.
|
|
95
|
+
- Coverage and limits name inspected scope, skipped scope, evidence basis, and blind spots.
|
|
93
96
|
handoff_requirements:
|
|
94
97
|
- Run validation per workflow/VALIDATE.md. Append validation block to primary output.
|
|
95
98
|
- Update workflow/status.yaml.
|
|
@@ -120,6 +123,7 @@ phases:
|
|
|
120
123
|
- Persistent schema notes are documented.
|
|
121
124
|
- Compatibility hazards are documented.
|
|
122
125
|
- Findings are marked with evidence levels.
|
|
126
|
+
- Coverage and limits name inspected scope, skipped scope, evidence basis, and blind spots.
|
|
123
127
|
handoff_requirements:
|
|
124
128
|
- Run validation per workflow/VALIDATE.md. Append validation block to primary output.
|
|
125
129
|
- Update workflow/status.yaml.
|
|
@@ -157,6 +161,8 @@ phases:
|
|
|
157
161
|
- Feature importance is sorted for porting.
|
|
158
162
|
- Known defects are referenced with porting recommendations (fix before porting / port differently / leave behind).
|
|
159
163
|
- Findings are marked with evidence levels.
|
|
164
|
+
- Coverage and limits name inspected scope, skipped scope, evidence basis, and blind spots.
|
|
165
|
+
- The Source Index makes the bundle a self-contained compression boundary and identifies targeted deep-read triggers.
|
|
160
166
|
handoff_requirements:
|
|
161
167
|
- Run validation per workflow/VALIDATE.md. Append validation block to primary output.
|
|
162
168
|
- Update workflow/status.yaml.
|
|
@@ -172,9 +178,6 @@ phases:
|
|
|
172
178
|
required_reads:
|
|
173
179
|
- GUIDE.md
|
|
174
180
|
- workflow/status.yaml
|
|
175
|
-
- findings/architecture/architecture-map.md
|
|
176
|
-
- findings/contracts/behavioral-contracts.md
|
|
177
|
-
- findings/protocols/protocols-and-state.md
|
|
178
181
|
- findings/porting/reverse-engineering-bundle.md
|
|
179
182
|
completion_criteria:
|
|
180
183
|
- Concept-level modules are defined.
|
|
@@ -182,6 +185,8 @@ phases:
|
|
|
182
185
|
- Protocol and persisted state expectations are stated.
|
|
183
186
|
- Acceptance scenarios and known unknowns are included.
|
|
184
187
|
- Findings are marked with evidence levels.
|
|
188
|
+
- Coverage and limits name inspected scope, skipped scope, evidence basis, and blind spots.
|
|
189
|
+
- Lower-level findings are deep-read only when the porting bundle identifies a gap, conflict, missing acceptance detail, or defect rationale.
|
|
185
190
|
handoff_requirements:
|
|
186
191
|
- Run validation per workflow/VALIDATE.md. Append validation block to primary output.
|
|
187
192
|
- Update workflow/status.yaml.
|
|
@@ -38,6 +38,7 @@ phases:
|
|
|
38
38
|
- Public surfaces are identified.
|
|
39
39
|
- Runtime lifecycle, concurrency model, and porting priorities are summarized.
|
|
40
40
|
- Findings are marked with evidence levels.
|
|
41
|
+
- Coverage and limits name inspected scope, skipped scope, evidence basis, and blind spots.
|
|
41
42
|
handoff_requirements:
|
|
42
43
|
- Run validation per workflow/VALIDATE.md. Append validation block to primary output.
|
|
43
44
|
- Update workflow/status.yaml.
|
|
@@ -61,6 +62,7 @@ phases:
|
|
|
61
62
|
- Summary tables are complete and counts match the detailed findings.
|
|
62
63
|
- Items spotted that are actually semantic in nature are routed to defect-scan-semantic via carry_forward in workflow/status.yaml.
|
|
63
64
|
- Findings are marked with evidence levels.
|
|
65
|
+
- Coverage and limits name inspected scope, skipped scope, evidence basis, and blind spots.
|
|
64
66
|
handoff_requirements:
|
|
65
67
|
- Run validation per workflow/VALIDATE.md. Append validation block to primary output.
|
|
66
68
|
- Update workflow/status.yaml.
|
|
@@ -93,6 +95,7 @@ phases:
|
|
|
93
95
|
- Contract ownership is mapped back to a layer or package.
|
|
94
96
|
- A black-box acceptance list is included.
|
|
95
97
|
- Findings are marked with evidence levels.
|
|
98
|
+
- Coverage and limits name inspected scope, skipped scope, evidence basis, and blind spots.
|
|
96
99
|
handoff_requirements:
|
|
97
100
|
- Run validation per workflow/VALIDATE.md. Append validation block to primary output.
|
|
98
101
|
- Update workflow/status.yaml.
|
|
@@ -124,6 +127,7 @@ phases:
|
|
|
124
127
|
- Persistent schema notes are documented.
|
|
125
128
|
- Compatibility hazards are documented.
|
|
126
129
|
- Findings are marked with evidence levels.
|
|
130
|
+
- Coverage and limits name inspected scope, skipped scope, evidence basis, and blind spots.
|
|
127
131
|
handoff_requirements:
|
|
128
132
|
- Run validation per workflow/VALIDATE.md. Append validation block to primary output.
|
|
129
133
|
- Update workflow/status.yaml.
|
|
@@ -153,6 +157,7 @@ phases:
|
|
|
153
157
|
- Findings are organized by pass and sorted by severity; summary tables match the detailed findings.
|
|
154
158
|
- Any carry_forward entries that targeted defect-scan-semantic have been resolved or explicitly re-routed.
|
|
155
159
|
- Findings are marked with evidence levels.
|
|
160
|
+
- Coverage and limits name inspected scope, skipped scope, evidence basis, and blind spots.
|
|
156
161
|
handoff_requirements:
|
|
157
162
|
- Run validation per workflow/VALIDATE.md. Append validation block to primary output.
|
|
158
163
|
- Update workflow/status.yaml.
|
|
@@ -193,6 +198,8 @@ phases:
|
|
|
193
198
|
- Feature importance is sorted for porting.
|
|
194
199
|
- Defect Synthesis consolidates mechanical-defects.md and semantic-defects.md with porting recommendations (fix before porting / port differently / leave behind).
|
|
195
200
|
- Findings are marked with evidence levels.
|
|
201
|
+
- Coverage and limits name inspected scope, skipped scope, evidence basis, and blind spots.
|
|
202
|
+
- The Source Index makes the bundle a self-contained compression boundary and identifies targeted deep-read triggers.
|
|
196
203
|
handoff_requirements:
|
|
197
204
|
- Run validation per workflow/VALIDATE.md. Append validation block to primary output.
|
|
198
205
|
- Update workflow/status.yaml.
|
|
@@ -208,12 +215,7 @@ phases:
|
|
|
208
215
|
required_reads:
|
|
209
216
|
- GUIDE.md
|
|
210
217
|
- workflow/status.yaml
|
|
211
|
-
- findings/architecture/architecture-map.md
|
|
212
|
-
- findings/contracts/behavioral-contracts.md
|
|
213
|
-
- findings/protocols/protocols-and-state.md
|
|
214
218
|
- findings/porting/reverse-engineering-bundle.md
|
|
215
|
-
- findings/defect-scan-mechanical/mechanical-defects.md
|
|
216
|
-
- findings/defect-scan-semantic/semantic-defects.md
|
|
217
219
|
completion_criteria:
|
|
218
220
|
- Concept-level modules are defined.
|
|
219
221
|
- Required behaviors are stated.
|
|
@@ -221,6 +223,8 @@ phases:
|
|
|
221
223
|
- Acceptance scenarios and known unknowns are included.
|
|
222
224
|
- Defects identified in either scan are explicitly designed-around or noted as "left behind", with the choice cited.
|
|
223
225
|
- Findings are marked with evidence levels.
|
|
226
|
+
- Coverage and limits name inspected scope, skipped scope, evidence basis, and blind spots.
|
|
227
|
+
- Lower-level findings are deep-read only when the porting bundle identifies a gap, conflict, missing acceptance detail, or defect rationale.
|
|
224
228
|
handoff_requirements:
|
|
225
229
|
- Run validation per workflow/VALIDATE.md. Append validation block to primary output.
|
|
226
230
|
- Update workflow/status.yaml.
|
|
@@ -34,6 +34,7 @@ phases:
|
|
|
34
34
|
- Public surfaces are identified.
|
|
35
35
|
- Runtime lifecycle, concurrency model, and porting priorities are summarized.
|
|
36
36
|
- Findings are marked with evidence levels.
|
|
37
|
+
- Coverage and limits name inspected scope, skipped scope, evidence basis, and blind spots.
|
|
37
38
|
handoff_requirements:
|
|
38
39
|
- Run validation per workflow/VALIDATE.md. Append validation block to primary output.
|
|
39
40
|
- Update workflow/status.yaml.
|
|
@@ -64,6 +65,7 @@ phases:
|
|
|
64
65
|
- Contract ownership is mapped back to a layer or package.
|
|
65
66
|
- A black-box acceptance list is included.
|
|
66
67
|
- Findings are marked with evidence levels.
|
|
68
|
+
- Coverage and limits name inspected scope, skipped scope, evidence basis, and blind spots.
|
|
67
69
|
handoff_requirements:
|
|
68
70
|
- Run validation per workflow/VALIDATE.md. Append validation block to primary output.
|
|
69
71
|
- Update workflow/status.yaml.
|
|
@@ -94,6 +96,7 @@ phases:
|
|
|
94
96
|
- Persistent schema notes are documented.
|
|
95
97
|
- Compatibility hazards are documented.
|
|
96
98
|
- Findings are marked with evidence levels.
|
|
99
|
+
- Coverage and limits name inspected scope, skipped scope, evidence basis, and blind spots.
|
|
97
100
|
handoff_requirements:
|
|
98
101
|
- Run validation per workflow/VALIDATE.md. Append validation block to primary output.
|
|
99
102
|
- Update workflow/status.yaml.
|
|
@@ -36,6 +36,7 @@ phases:
|
|
|
36
36
|
- Public surfaces are identified.
|
|
37
37
|
- Runtime lifecycle, concurrency model, and porting priorities are summarized.
|
|
38
38
|
- Findings are marked with evidence levels.
|
|
39
|
+
- Coverage and limits name inspected scope, skipped scope, evidence basis, and blind spots.
|
|
39
40
|
handoff_requirements:
|
|
40
41
|
- Run validation per workflow/VALIDATE.md. Append validation block to primary output.
|
|
41
42
|
- Update workflow/status.yaml.
|
|
@@ -67,6 +68,7 @@ phases:
|
|
|
67
68
|
- Contract ownership is mapped back to a layer or package.
|
|
68
69
|
- A black-box acceptance list is included.
|
|
69
70
|
- Findings are marked with evidence levels.
|
|
71
|
+
- Coverage and limits name inspected scope, skipped scope, evidence basis, and blind spots.
|
|
70
72
|
handoff_requirements:
|
|
71
73
|
- Run validation per workflow/VALIDATE.md. Append validation block to primary output.
|
|
72
74
|
- Update workflow/status.yaml.
|
|
@@ -97,6 +99,7 @@ phases:
|
|
|
97
99
|
- Persistent schema notes are documented.
|
|
98
100
|
- Compatibility hazards are documented.
|
|
99
101
|
- Findings are marked with evidence levels.
|
|
102
|
+
- Coverage and limits name inspected scope, skipped scope, evidence basis, and blind spots.
|
|
100
103
|
handoff_requirements:
|
|
101
104
|
- Run validation per workflow/VALIDATE.md. Append validation block to primary output.
|
|
102
105
|
- Update workflow/status.yaml.
|
|
@@ -132,6 +135,8 @@ phases:
|
|
|
132
135
|
- Portability hazards and open questions are separated from facts.
|
|
133
136
|
- Feature importance is sorted for porting.
|
|
134
137
|
- Findings are marked with evidence levels.
|
|
138
|
+
- Coverage and limits name inspected scope, skipped scope, evidence basis, and blind spots.
|
|
139
|
+
- The Source Index makes the bundle a self-contained compression boundary and identifies targeted deep-read triggers.
|
|
135
140
|
handoff_requirements:
|
|
136
141
|
- Run validation per workflow/VALIDATE.md. Append validation block to primary output.
|
|
137
142
|
- Update workflow/status.yaml.
|
|
@@ -147,9 +152,6 @@ phases:
|
|
|
147
152
|
required_reads:
|
|
148
153
|
- GUIDE.md
|
|
149
154
|
- workflow/status.yaml
|
|
150
|
-
- findings/architecture/architecture-map.md
|
|
151
|
-
- findings/contracts/behavioral-contracts.md
|
|
152
|
-
- findings/protocols/protocols-and-state.md
|
|
153
155
|
- findings/porting/reverse-engineering-bundle.md
|
|
154
156
|
completion_criteria:
|
|
155
157
|
- Concept-level modules are defined.
|
|
@@ -157,6 +159,8 @@ phases:
|
|
|
157
159
|
- Protocol and persisted state expectations are stated.
|
|
158
160
|
- Acceptance scenarios and known unknowns are included.
|
|
159
161
|
- Findings are marked with evidence levels.
|
|
162
|
+
- Coverage and limits name inspected scope, skipped scope, evidence basis, and blind spots.
|
|
163
|
+
- Lower-level findings are deep-read only when the porting bundle identifies a gap, conflict, missing acceptance detail, or defect rationale.
|
|
160
164
|
handoff_requirements:
|
|
161
165
|
- Run validation per workflow/VALIDATE.md. Append validation block to primary output.
|
|
162
166
|
- Update workflow/status.yaml.
|