Add end-to-end integration test for full pipeline

[Copilot]

No integration test existed to verify the full CLI → config → transform → pipeline → strategy → output path as a unit. Failures at integration boundaries (e.g. transform output reaching the strategy, output file actually written) were only catchable at runtime.

Changes

tests/pipeline_integration_test.rs — new integration test file with three tests:

• test_full_pipeline_end_to_end (#[ignore], requires pandoc): creates a temp markdown file with emoji content (exercises EmojiTransform), writes a YAML config, invokes the compiled binary, and asserts the output .html file exists on disk and is non-empty
• test_full_pipeline_missing_input_file: asserts non-zero exit when config references a missing input — verifies the pipeline never starts
• test_full_pipeline_invalid_config: asserts non-zero exit for a semantically invalid config (empty outputs, empty input)

#[test]
#[ignore = "requires pandoc to be installed"]
fn test_full_pipeline_end_to_end() {
    // markdown with emoji → exercises EmojiTransform before strategy renders
    fs::write(&input_path, "# Test 😀\n\nRendered end-to-end.\n")?;
    // ... invoke CLI binary, assert output file exists and is non-empty
    assert!(output_dir.join("document.html").exists());
}

Follows existing patterns from tests/cli_tests.rs — reuses tests/common, uses tempfile for isolation, and marks pandoc-dependent tests with #[ignore] consistently.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>🧠 Add end-to-end integration test for full pipeline</issue_title>
<issue_description>Title: 🧠 Add end-to-end integration test for full pipeline

---

Description

Add an integration test that verifies the entire system:

CLI → config → transform → pipeline → strategy → output

---

Goals

• Validate system works end-to-end
• Catch integration issues early

---

Requirements

• Use a test input file
• Run full pipeline
• Verify output file is generated

---

Notes

• Keep test lightweight
• Do not rely on complex fixtures

---

Acceptance Criteria

• End-to-end test implemented
• Output file generated successfully
• Test passes reliably</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes 🧠 Add end-to-end integration test for full pipeline #27

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

[devactivity-app]

Pull Request Summary by devActivity

Metrics

Achievements

• @szmyty
  Earned XP: 15⭐
  Check Your Progress