Bump library patch version to 2.0.7

[Copilot]

Increment the XTerm.NET package version from 2.0.6 to 2.0.7.

• Version: Update the <Version> value in XTerm.NET.csproj.

• Fixes bump library patch version by 1 #173

[github-actions]

Perf comparison — this change, against its base

3 run(s) of each side, alternating on one machine. Allocation is a count and is gated exactly. Time is a measurement, so its gate is derived from the spread this job just observed in itself rather than fixed in advance.

corpus	bytes/char	gen0/Mchar	ns/char	Δ time	noise	gate
scroll-ascii	0.00 → 0.00	0.00 → 0.00	2.81 → 2.99	+6.4% 👀	±8%	23%
sgr-churn	0.00 → 0.00	0.00 → 0.00	6.23 → 6.52	+4.7% 👀	±15%	45%
truecolor	0.00 → 0.00	0.00 → 0.00	5.94 → 6.13	+3.3%	±12%	35%
alt-redraw	0.00 → 0.00	0.00 → 0.00	8.33 → 8.55	+2.6%	±8%	23%
unicode	7.66 → 7.66	0.09 → 0.09	21.51 → 21.35	-0.7%	±2%	7%
flood	0.00 → 0.00	0.00 → 0.00	87.74 → 87.75	+0.0%	±7%	21%

Each corpus is gated at max(4%, 3 × its own noise). A wide noise column means this runner was busy and the timing half of the table should be read as advisory; the allocation half is exact either way.

assemblies measured

• base: XTerm.NET 2.0.5.0 mvid:598f9e1e-19dc-4f1f-b5b6-1948c5514a93
• head: XTerm.NET 2.0.7.0 mvid:7c2cce29-b56f-44c6-a81e-41501e32845d

Worth a look — over the floor, under this run's gate, so not failed:

• scroll-ascii time 2.81 → 2.99 ns/char (6.4%, under its 23.0% gate but over the 4% floor)
• sgr-churn time 6.23 → 6.52 ns/char (4.7%, under its 44.8% gate but over the 4% floor)

Re-run on a quieter machine, or with more --chars, to tell a real change from a busy runner. Both narrow the noise column, which tightens the gate.

---

Perf comparison — cumulative, everything since 2.0.3

3 run(s) of each side, alternating on one machine. Allocation is a count and is gated exactly. Time is a measurement, so its gate is derived from the spread this job just observed in itself rather than fixed in advance.

corpus	bytes/char	gen0/Mchar	ns/char	Δ time	noise	gate
scroll-ascii	0.00 → 0.00	0.00 → 0.00	2.84 → 2.99	+5.4% 👀	±8%	24%
sgr-churn	0.00 → 0.00	0.00 → 0.00	6.30 → 6.52	+3.5%	±15%	45%
truecolor	0.00 → 0.00	0.00 → 0.00	5.96 → 6.13	+2.9%	±12%	35%
alt-redraw	0.00 → 0.00	0.00 → 0.00	8.36 → 8.55	+2.3%	±8%	23%
unicode	7.66 → 7.66	0.09 → 0.09	21.52 → 21.35	-0.8%	±2%	6%
flood	0.00 → 0.00	0.00 → 0.00	86.58 → 87.75	+1.3%	±7%	21%

Each corpus is gated at max(5%, 3 × its own noise). A wide noise column means this runner was busy and the timing half of the table should be read as advisory; the allocation half is exact either way.

assemblies measured

• base: XTerm.NET 2.0.3.0 mvid:9ba0ce98-0d1e-4424-8aa1-9ab012cdc07a
• head: XTerm.NET 2.0.7.0 mvid:7c2cce29-b56f-44c6-a81e-41501e32845d

Worth a look — over the floor, under this run's gate, so not failed:

• scroll-ascii time 2.84 → 2.99 ns/char (5.4%, under its 23.6% gate but over the 5% floor)

Re-run on a quieter machine, or with more --chars, to tell a real change from a busy runner. Both narrow the noise column, which tightens the gate.