Dark Triple Patcher

Roadmap Checklist

Current: v3.3.002 · Phase 3B0

Phase 0–7 roadmap for the extractor/patcher. Each phase is staged into 4–5 small builds so the work can ship in manageable chunks.

Done In progress / partly live Planned / not started
One row = one build slice
Phase 0 Baseline Extractor / Patcher
Triple dark shell, basic extract/merge, versioned saves.
Done ✓
›
  • 0.A — Triple Dark Shell + Editors Core UI
    Dark triple-pane layout with Ace editors for HTML, CSS, and JS, plus basic UI chrome.
    Shipped in early 3.0.x
  • 0.B — Source IO & Versioning Source
    Load/split/save source HTML into HTML/CSS/JS panes with semantic versioned filenames and _original backups.
    Complete
  • 0.C — Target IO & Patch Application Target
    Load/save full target HTML (“Full HTML to be patched”) and apply merged fragments back into the target document.
    Complete
  • 0.D — ID / Class Extraction & Preview Extractor
    Extract by ID or class with ancestry comments, heuristic CSS/JS extraction, preview of patched documents, and merge from the extract workspace.
    Complete
Phase 1 Hardening & Precision
Predictable extracts, stable mapping, ID rules.
Done ✓
›
  • 1.A — Per-node Extraction for Class Mode Precision
    After a class extract, show a node list and allow “All nodes” vs “Only Node N” extraction/patching in the workspace.
    Complete (v3.1)
  • 1.B — Stable Fragment ↔ Instance Mapping Mapping
    Maintain 1:1 ordering between DOM class instances and Extract HTML snippets so indexes are predictable.
    Complete (v3.1)
  • 1.C — Robust ID Handling Rules Identity
    Preserve original IDs by default, respect IDs in snippets, and only auto-generate IDs (e.g., className-n) when necessary.
    Complete (v3.1)
  • 1.D — General Safety & Error Handling Safety
    Defensive DOM parsing and error handling around extracts/merges to avoid hard crashes on malformed HTML.
    Complete (v3.1) Strict parse & duplicate-ID checks moved to Phase 6
Phase 2 Selector Power & Fragment Intelligence
Target exactly what you want, with project-aware patterns.
Done ✓
›
  • 2.A — Selector Tester Selectors
    CSS selector tester with source/target/both contexts, match counts, DOM paths, and click-to-preview matches in an iframe.
    Complete (v3.2)
  • 2.B — ID/Class Map Inspector Structure
    Combined ID/Class index for source and target, showing collisions, missing elements, and quick-jumps into the selector tester.
    Complete (v3.2)
  • 2.C — Pattern Rules Editor Patterns
    UI for persistent ID/Class transform rules (prefix/replace/regex) with local storage and preview of sample transformations.
    Complete (v3.2)
  • 2.D — Pattern-aware Extract & CSS Rewrite Integration
    Apply pattern rules to extracted fragments and rewrite CSS selectors so IDs/classes stay in sync across HTML and styles.
    Complete (v3.2)
Phase 3 Diffs, Patch Plans & Reverts
See it before you commit it. Build history for what changed.
Done •
›
  • 3.A — PatchPlan Engine & Diff Viewer 3A
    Build PatchPlan from the current extraction, show side-by-side before/after diffs with stats, and confirm before applying the plan.
    Live in v3.3 Works on “current fragment” only
  • 3.B — PatchSet & History Contracts (Data Layer) 3B0
    Define and persist PatchSet and PatchHistory structures to local storage (no UI yet), laying the groundwork for multi-fragment bundles and timelines.
    Current build: v3.3.002 · PH3B0
  • 3.C — PatchSet UI & Multi-fragment Apply 3B1
    UI to create/edit PatchSets from the current extraction(s) and apply a saved PatchSet across source/target in a single PatchPlan run.
    Complete
  • 3.D — Patch History Writer & Timeline 3C
    On each PatchPlan apply, write a PatchHistory entry and expose a timeline viewer listing patches with basic metadata and warnings.
    Done
  • 3.E — Fragment-only Preview & Per-fragment Revert 3D
    Mini preview mode for just the fragment + CSS/JS, plus one-click revert of a fragment in the workspace or document back to its original version.
    Done
Phase 4 Multi-fragment Sessions & Bundles
Treat the tool like a mini patch IDE with batch commits.
In Progress …
›
  • 4.A — Tabbed Extract Workspace 4A
    Multiple extract tabs in a single session (e.g., header, nav, tool cards, footer), each with its own HTML/CSS/JS and preview/merge settings.
    Done
  • 4.B — Apply All Pending Patches 4B
    Batch-apply all tabs’ patches to the target via a single consolidated PatchPlan, with per-fragment stats and a combined confirmation step.
    Done
  • 4.C — Patch Bundle Export / Import 4C
    Export/import patch bundles (.json/.patch) that serialize PatchSets for reuse on other copies of the same base HTML.
    Done
  • 4.D — Patch History Timeline + Bundles 4D
    Timeline panel tying PatchHistory entries to bundles and fragments, suitable for documentation and audit trails.
    Done
Phase 5 Automation & Power Tools
Make repetitive content surgery fast and clean.
In Progress …
›
  • 5.A — Scoped Search & Replace 5A
    Search/replace within the extract pane with scoping to specific nodes, fragments, or tabs; optional regex mode.
    Done
  • 5.B — Version Bump Helpers 5B
    Regex-based utilities to bump version suffixes in filenames or strings (e.g., _v1.0.000 → _v1.1.000) across the extract.
    Done
  • 5.C — Snippet Macros / Presets 5C
    Reusable transforms like “wrap selection in chip”, “add data-tool-* attributes based on href”, callable from a macro list or shortcuts.
    In Progress
  • 5.D — Template Duplication & Instance Generator 5D
    One-click “clone this card/section” that adds a new instance to the target with a fresh ID and updated placeholders (names, hrefs, etc.).
    In Progress
Phase 6 Profiles, Safety & Project-level Smarts
Adapt to different consoles and guard critical regions.
Planned …
›
  • 6.A — Project Profiles 6A
    Per-project profiles (e.g., warchief-dev-console, other sites) storing ID patterns, naming, and default patch behaviors.
    Planned
  • 6.B — Protected Region Guardrails 6B
    Mark selectors as “protected” (legal text, headers, footers) and require explicit confirmation when patches touch those regions.
    Planned
  • 6.C — Reverse Patching (Target → Source) 6C
    Ability to pull changes from target HTML back into the source triptych, keeping dev and deployed versions aligned.
    Planned
  • 6.D — Strict Parse & Duplicate-ID Validation 6D
    Dedicated strict-parse mode for targets with warnings on malformed HTML and pre-merge duplicate-ID detection for safer patches.
    Planned (migrated from early Phase 1 ideas)
Phase 7 Someday / Stretch Goals
Plugins, embeddable mode, and semantic awareness.
Planned …
›
  • 7.A — Plugin Hook System 7A
    Small JS API to plug in custom validators, patch generators, and project-specific automation scripts into the patcher.
    Stretch
  • 7.B — Embeddable Mini-editor Mode 7B
    Stripped-down “Triple Patcher mini” that can be invoked as a modal from other Warchief tools for focused fragment editing.
    Stretch
  • 7.C — Semantic Awareness 7C
    Recognize common UI patterns (button groups, card lists, tool links) and offer higher-level “change all similar things” operations.
    Stretch
  • 7.D — Smart Suggestions & Bulk Ops 7D
    Suggest applying a text or attribute change across all semantically similar elements (e.g., all “Open HTML editor” buttons).
    Stretch
This file is only a roadmap/checklist; it doesn’t change behavior. Save as roadmap-triple-patcher.html and open in your browser alongside the console.