WorkBuddy merging two tables keeps shifting dates by a day—did I misconfigure something?

Title: WorkBuddy merges two tables, and if the column order is different it gets misaligned — is it just hard-concatenating by position?

This afternoon I exported last week's reading data from the WeChat official account backend into a table, and also exported the topic-selection table while I was at it, thinking I'd have WorkBuddy merge them by column name so I wouldn't have to match them up one by one.

After the first run I was completely stunned. The row count matched up, but the columns were entirely misaligned — the reads column ended up under "title," and the title got squeezed into the date column. I thought the column order had gotten scrambled during export, so I re-exported, and it was still wrong. Later I opened both tables to compare and found one was "date, title, reads" and the other was "title, date, reads" — same column names, just different order. It seems like it's hard-concatenating by column position, not matching by column name. I'm not sure if that understanding is right. I've hit a similar pitfall with other tools before — back then I had to manually make the column order of both tables exactly identical before feeding them in. But with WorkBuddy I couldn't find any "align by column name" type of toggle.

A couple days ago I also came across an article about self-media entrepreneurship, saying that now with AI creation for everyone, the barrier to entry for ordinary people making content has dropped a lot. After reading it I thought, barrier or no barrier, I can't even get past the daily table-matching hurdle.

Right now my crude workaround is to manually adjust the column order of both tables to be the same first, then let it merge. Once or twice is fine, but doing this every day is a bit much. I want to ask if anyone on the forum has used WorkBuddy for similar table merges — is there some toggle for column alignment that I missed? Or is it just not suited for this, and I should change my approach, like first unifying the column names and order of both tables into a template before feeding them in.

Anyone who's hit this pitfall, please point me in a direction.