Int32 to Bool mapping behaves differently for positional constructor than for property

This may or may not be a bug but the behavior seemed interesting, so I thought I'd ask.

I isolated this test case, where two identical query strings fill objects with the same shape but different constructors. The one mapped by constructor does not work, but the one mapped by property does work.

private record InConstructor(bool B);

[Fact] // This one will fail
public void TestFillInConstructor()
{
    InConstructor ctor = connection.Query<InConstructor>("select 1 B").First();
    Assert.True(ctor.B);
}

private record InProperty
{
    public bool B { get; init; }
}

[Fact] // This one will succeed
public void TestFillInProperty()
{
    InProperty prop = connection.Query<InProperty>("select 1 B").First();
    Assert.True(prop.B);
}

It looks like the constructor version is looking for an Int32 in the position where Bool exists, since the returned type from the SQL is an int

Start by reproducing the two record-mapping tests from the issue against the Dapper query path, comparing positional constructor binding with property binding for select 1 B. Trace where the returned Int32 is matched to the constructor's Bool parameter; done means the two equivalent object shapes map consistently, with regression coverage for both cases.