Publish LinxCore architecture contracts and policy-driven SPEC lane docs

[zhoubot]

Summary

• package the current model-generated LinxCore docs and helper updates from the existing checkout
• add the architecture contract pages for overview, interfaces, microarchitecture, stage catalog, module catalog, and verification matrix
• align SPEC helper scripts with named governance phases and manifest-driven bringup subsets

Testing

• git diff --check

Not tested

• MkDocs contract lint
• SPEC Stage-A helper execution

[gemini-code-assist]

Code Review

This pull request introduces comprehensive architectural documentation for LinxCore v0.56, including external interface contracts, microarchitecture specifications, a module catalog, a pipeline stage catalog, and a verification matrix mapping architectural intent to validation gates. Additionally, it updates the SPEC benchmark test scripts to dynamically resolve the bring-up subset from the policy manifest instead of using hardcoded lists. Feedback on the documentation highlights a hardcoded user-specific absolute path in the overview document that should be replaced with a generic placeholder for portability.

[gemini-code-assist]

The document contains a hardcoded absolute path specific to a user (/Users/zhoubot/LinxCore). Hardcoded user-specific paths should be avoided in shared documentation to ensure portability and maintain privacy. Consider using a generic placeholder or referring to local development clones abstractly.

Suggested change

	- Standalone trees such as `/Users/zhoubot/LinxCore` are development mirrors,
	not contract authority.
	- Standalone trees (e.g., local development clones) are development mirrors,
	not contract authority.