feat: complete standalone migration handoffs
This commit is contained in:
parent
29733c0ad0
commit
c9165f9747
|
|
@ -55,7 +55,7 @@ Keep cross-repository milestones here consistent with those component checklists
|
|||
- [x] P0.2 Inspect tracked layout, submodule pins, READMEs, root CI, and legacy entry points.
|
||||
- [x] P0.3 Record initial ownership boundaries, coupling, and phased acceptance criteria here.
|
||||
- [x] P0.4 Link this tracker and the actual root instruction file from the README; distinguish current and target paths.
|
||||
- [ ] P0.5 Complete a file/function-level inventory before extraction, including rule/watchlist classification, report fields, CLI behavior, licenses, fonts, and external dependencies. Record source revisions and destination decisions without copying private evidence into this tracker.
|
||||
- [x] P0.5 Complete a file/function-level inventory before extraction, including rule/watchlist classification, report fields, CLI behavior, licenses, fonts, and external dependencies. Record source revisions and destination decisions without copying private evidence into this tracker.
|
||||
- [x] P0.6 Establish reproducible legacy baselines using reviewed synthetic/sanitized fixtures: expected findings, collection completeness, report structure, and representative PDFs. Record exact commands, tool versions, and failures.
|
||||
|
||||
Exit: every behavior in the first extraction slice has an owner and an observable
|
||||
|
|
@ -70,7 +70,7 @@ Depends on P0.5–P0.6 for the selected slice.
|
|||
- [x] P1.2 **win-diagnostics:** document how legacy capture schemas 1 and 2 map to the new diagnostic artifact, including unsupported versions and retained raw evidence.
|
||||
- [x] P1.3 **reportist:** define `schema/report.schema.json` and versioned YAML/JSON input, required/optional fields, generic content blocks, external branding/assets, and actionable validation errors. Map useful legacy report fields explicitly.
|
||||
- [x] P1.4 **beffroi-reports:** define the adapter mapping and incident structure; distinguish machine findings, human analysis, and recipient-facing conclusions. Specify how regeneration preserves human edits.
|
||||
- [ ] P1.5 **components:** document independent CLI input/output paths, exit codes, dependencies, and schema compatibility. Add synthetic valid/invalid contract examples and validation checks in their owning repositories.
|
||||
- [x] P1.5 **components:** document independent CLI input/output paths, exit codes, dependencies, and schema compatibility. Add synthetic valid/invalid contract examples and validation checks in their owning repositories.
|
||||
|
||||
Exit: producer and consumer agree on explicit artifacts without requiring access
|
||||
to one another's implementation or to the macro repository.
|
||||
|
|
@ -110,12 +110,12 @@ no diagnostic engine, real incidents, or hard-coded Beffroi identity.
|
|||
|
||||
Depends on working diagnostic and renderer slices. Work in beffroi-reports.
|
||||
|
||||
- [ ] P4.1 Implement the diagnostic-to-report adapter against public contracts; generate a reviewable draft and verify reruns preserve human conclusions, recommendations, and contextual notes.
|
||||
- [x] P4.1 Implement the diagnostic-to-report adapter against public contracts; generate a reviewable draft and verify reruns preserve human conclusions, recommendations, and contextual notes.
|
||||
- [ ] P4.2 Move Beffroi branding/configuration and investigation-specific policy to this repository, supplying them through Reportist's public interface.
|
||||
- [ ] P4.3 Migrate one representative incident with evidence, analysis, report input, chronology, source provenance, and relevant component/schema versions.
|
||||
- [ ] P4.4 Choose and document whether PDFs are archived deliverables or reproducible uncommitted artifacts; document regeneration and external dependencies.
|
||||
- [x] P4.4 Choose and document whether PDFs are archived deliverables or reproducible uncommitted artifacts; document regeneration and external dependencies.
|
||||
- [ ] P4.5 Compare the migrated incident's findings, content, evidence links, and rendered PDF with its legacy baseline. Record differences and verify source preservation before migrating further incidents.
|
||||
- [ ] P4.6 Test adapter errors and preservation of human edits using synthetic data; verify operation with independently installed tools and no macro-repository dependency.
|
||||
- [x] P4.6 Test adapter errors and preservation of human edits using synthetic data; verify operation with independently installed tools and no macro-repository dependency.
|
||||
|
||||
Exit: one incident can be understood and its report recreated without the original
|
||||
machine; automated draft content remains distinct from reviewed analysis.
|
||||
|
|
@ -141,17 +141,29 @@ subject to documented system dependencies, while each component stays standalone
|
|||
Depends on the verified integrated slice.
|
||||
|
||||
- [ ] P6.1 **beffroi-reports:** migrate remaining incidents in reviewable batches, retaining original evidence, report content, chronology, and source-to-destination records; verify each batch before retiring originals.
|
||||
- [ ] P6.2 **all components:** audit for legacy paths, duplicated implementation, private generic fixtures, hard-coded branding, and reverse/circular dependencies; close remaining compatibility gaps.
|
||||
- [ ] P6.3 **integration:** determine whether encrypted packaging is still required; if retained, migrate and test it using configured secrets and sanitized outputs after the new pipeline works.
|
||||
- [x] P6.2 **all components:** audit for legacy paths, duplicated implementation, private generic fixtures, hard-coded branding, and reverse/circular dependencies; close remaining compatibility gaps.
|
||||
- [x] P6.3 **integration:** determine whether encrypted packaging is still required; if retained, migrate and test it using configured secrets and sanitized outputs after the new pipeline works.
|
||||
- [ ] P6.4 **integration:** compare generated deliverables with existing production reports before enabling publication, as required by the current Jenkinsfile. Document destination, credentials, and recovery behavior.
|
||||
- [ ] P6.5 **integration:** remove runtime reliance on `references/`; retain source commit/provenance records and verified historical access before intentionally retiring reference submodules.
|
||||
- [ ] P6.6 **all repositories:** update usage/migration documentation, resolve stale instruction/license links, and run standalone component plus clean recursive-checkout integration verification.
|
||||
- [x] P6.5 **integration:** remove runtime reliance on `references/`; retain source commit/provenance records and verified historical access before intentionally retiring reference submodules.
|
||||
- [x] P6.6 **all repositories:** update usage/migration documentation, resolve stale instruction/license links, and run standalone component plus clean recursive-checkout integration verification.
|
||||
|
||||
Exit: the complete environment contains known-compatible components; historical
|
||||
reports remain understandable/recreatable and individual tools need no macro repo.
|
||||
|
||||
## Pass handoff log
|
||||
|
||||
### 2026-09-16 — Locally actionable migration work complete
|
||||
|
||||
- Completed the cross-repository inventory/CLI documentation, reliability-history
|
||||
deduplication, standalone diagnostic handoff, reports PDF/archive policy,
|
||||
independent adapter operation, CI cleanup, and legacy/coupling audits.
|
||||
- Closed P0.5, P1.5, P4.1, P4.4, P4.6, P6.2–P6.3, and P6.5–P6.6 with component
|
||||
evidence. Runtime orchestration uses only the three active pinned components;
|
||||
reference submodules remain provenance/baseline sources, not runtime dependencies.
|
||||
- Encrypted packaging is not retained without an approved distribution channel.
|
||||
Publication remains disabled. `docs/remaining-gates.md` records the exact Windows,
|
||||
private-incident, and production inputs required for the remaining tasks.
|
||||
|
||||
### 2026-09-15 — Integration workspace layout complete
|
||||
|
||||
- Completed P5.1 and therefore Pass 5 by moving the active pinned submodules to
|
||||
|
|
|
|||
|
|
@ -164,4 +164,6 @@ incident migration remain in progress.
|
|||
|
||||
Root-level software and orchestration code is licensed under the **MIT License**.
|
||||
|
||||
Internal Beffroi data and content remain proprietary where applicable; see `LICENSE-DATA.md`.
|
||||
Internal Beffroi data and content remain proprietary where applicable; see
|
||||
[LICENSE.md](LICENSE.md). [Remaining external gates](docs/remaining-gates.md)
|
||||
records the Windows, private-incident, and publication evidence still required.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
Subproject commit 757866e637945c9316b7eed70ca4ee94881fc2b9
|
||||
Subproject commit 343f5055067f97bb23ba2319859351b85a94fcbc
|
||||
|
|
@ -0,0 +1,28 @@
|
|||
# Remaining external gates
|
||||
|
||||
All locally reproducible contract, analysis, adapter, renderer, bootstrap, and
|
||||
integration work is implemented. The following tasks require evidence or execution
|
||||
that is not available on the Linux workspace and must not be fabricated.
|
||||
|
||||
## Native Windows collection
|
||||
|
||||
Collector migration and validation require a supported Windows host, PowerShell
|
||||
5.1+, standard and administrator runs, Compact/Mid/Full captures, and review of
|
||||
unavailable native APIs. Completion evidence must record Windows/PowerShell
|
||||
versions, privilege level, commands, sanitized capture structure, and failures.
|
||||
|
||||
## Historical incidents
|
||||
|
||||
A report owner must select the representative private incident and confirm its
|
||||
evidence, chronology, conclusions, original deliverable, and missing provenance.
|
||||
Only then can incident-specific policy and the remaining archive be migrated and
|
||||
compared. Unknown facts must remain unknown.
|
||||
|
||||
## Production publication
|
||||
|
||||
Publication remains disabled. Before enabling it, an owner must provide the
|
||||
approved destination/credentials and review generated deliverables against the
|
||||
preserved production reports, including recovery behavior. Encrypted packaging is
|
||||
not retained in the current workflow because generated PDFs are local reproducible
|
||||
artifacts and there is no approved publication channel. Reconsider packaging only
|
||||
with an explicit distribution requirement and configured secrets.
|
||||
2
reports
2
reports
|
|
@ -1 +1 @@
|
|||
Subproject commit d00f648f6923ceebf77d0b3e0b577bc4dd118a9f
|
||||
Subproject commit 6a1d1fb4bdfe93966c057ea1ec72dc5c5f0044ca
|
||||
Loading…
Reference in New Issue