[Test] Derive expected values from resolver output, not original cells

[coderabbitai]

Context

From PR #34 review discussion: #34

The integration test reads expected cell data from data-cell attributes which contain the original cells from base/current/incoming, not what the resolver actually constructs.

Problem

The test assumes the resolver will output cells identical to the originals, but doesn't account for:

• Resolver might modify metadata
• Resolver might normalize source format
• Resolver might handle outputs differently

Impact

Low priority - this is more of a testing principle issue. The resolver is unlikely to transform cells unexpectedly.

Suggested Enhancement

Consider deriving expected values from the resolver's actual output path rather than the original input cells, or document why the current approach is valid.

Backlinks:

• PR [FEAT] Create a Testing Harness #34: [FEAT] Create a Testing Harness #34
• Requested by: @Avni2000