Bugs happen, no amount of testing can avoid that completely. And if we mess up, we need a way to tell which WARCs produced by crocoite (and tools) are affected by a bug and – possibly – fix it. For that we need:
[x] -merge should write an additional warcinfo record, containing the same information as -grab, so we know which tool modified the WARC.
[x] Add a tool which uses an internal errata database (yaml?) and checks warcinfo crocoite version+dependencies+chrome version against known bugs.
[ ] The same tool should be able to fix the WARC (if possible) and write a new one, indicating it was modified.
Bugs happen, no amount of testing can avoid that completely. And if we mess up, we need a way to tell which WARCs produced by crocoite (and tools) are affected by a bug and – possibly – fix it. For that we need: