Publish standalone bilingual LinxISA docs

[zhoubot]

Summary

• import the latest public LinxISA manual hierarchy into the repo docs tree
• publish English and Chinese Material sites with and builds
• scrub provenance/vendor/person/confidential references so the manual reads as a standalone public document
• keep the appendix/reference surfaces and LinxCore contract checks working

Verification

• mkdocs build --strict
• mkdocs build --strict -f mkdocs.zh.yml -d site/zh
• python3 tools/isa/build_golden.py --profile v0.56 --check
• python3 tools/isa/validate_spec.py --profile v0.56
• python3 tools/isa/check_canonical_v056.py --root .
• python3 tools/bringup/check_linxcore_arch_contract.py --root . --strict --require-mkdocs

[gemini-code-assist]

Code Review

This pull request updates the documentation for the LinxISA architecture, including changes to the ISA manual, backend architecture descriptions, and various change logs. The updates primarily focus on refining the documentation for standalone public consumption by removing internal server links, vendor-specific references, and corrupted placeholders. My review identified several formatting issues in Markdown tables and image tags, as well as remaining internal references that need to be updated to relative links to ensure the documentation is suitable for public release.

[gemini-code-assist]

The link target (ZXM DLINK6QXZ) appears to be a broken placeholder or internal reference that was not correctly resolved during the scrubbing process.

[gemini-code-assist]

This URL contains an internal IP address. It should be removed or replaced with a public download link.

[gemini-code-assist]

The term ZXTERMZH36QXZ appears to be a corrupted placeholder or an internal identifier that should have been scrubbed.

[gemini-code-assist]

The image tag has a duplicated width attribute and a syntax error.

Suggested change

	{ width="800"){ width="800" }
	{ width="800" }

[gemini-code-assist]

Two table rows are merged into a single line, which will break the table rendering.

Suggested change

	| TAGE | HIT_b2w0 | | √ | √ | 1 | 33 | || TAGE | U_b1w0 | | √ | √ | 2 | 35 | |
	| TAGE | HIT_b2w0 | | √ | √ | 1 | 33 | |
	| TAGE | U_b1w0 | | √ | √ | 2 | 35 | |

[gemini-code-assist]

Typo: instructionheader instruction should be header instruction.

Suggested change

	v0.31 defines 10 types of block instructionheader instruction including **standard block**, **standard super block**, **standard compression fast**, **standard super compression block**, **standard floating point block**, **standard floating point super block**, **inline block**, **control block**, **template block** and **system block**.
	v0.31 defines 10 types of block header instruction including **standard block**, **standard super block**, **standard compression fast**, **standard super compression block**, **standard floating point block**, **standard floating point super block**, **inline block**, **control block**, **template block** and **system block**.

[gemini-code-assist]

Table formatting error: a new table header is appended to the end of a row.

Suggested change

	| LWU.A | lwu.a \[SrcL, simm<<2\]<, {=>, ->}RegDst> | lhu.a \[SrcL, simm\]<, {=>, ->}RegDst> || Microinstructions | Assembly before update | Assembly after update |
	| LWU.A | lwu.a \[SrcL, simm<<2\]<, {=>, ->}RegDst> | lhu.a \[SrcL, simm\]<, {=>, ->}RegDst> |

[gemini-code-assist]

Table formatting error: the table header is merged with the preceding section title.

Suggested change

	**Floating point comparison class**| Microinstructions | Assembly format | Description |
	**Floating point comparison class**
	| Microinstructions | Assembly format | Description |

[gemini-code-assist]

A newline is required before the table header for it to render correctly in most Markdown parsers.

Suggested change

	As shown in the figure above, the microinstruction ROB is composed of M slices. Each slice is a block of a ROB and contains K instructions. Each slice can be connected at will through the head and tail pointers to form a linked list structure, which can store a total of M*K instructions. Each slice has the following domain segments:| Field segment | Description |
	Each slice has the following domain segments:
	| Field segment | Description |

[gemini-code-assist]

There is a missing newline or space before the second point, which will cause rendering issues in Markdown.

Suggested change

	Depended Source indicates which pipe the source operand comes from. It has been recorded in OOO in the REN module when the instruction is distributed, and the signal records the pipe through which the instruction is distributed. When subsequent dependent instructions enter the issue queue, the microarchitecture will not only query the wake-up status of its source operand in the rename module, but also query the production pipeline of its source operand, and record it in the issue queue. For ease of understanding, we can regard the Depended Source information as the ordinate of the target data source.2. **Tracking Vector**:
	For ease of understanding, we can regard the Depended Source information as the ordinate of the target data source.
	2. **Tracking Vector**: