Establish repository-specific contribution governance #43

Problem

eApps spans native C/LVGL applications, web and mobile apps, browser extensions, desktop apps, developer tools, CLI tools, enterprise packaging, and the public marketplace catalog. Its current agent guidance is a generic role scaffold, its two case-only pull request templates do not require a GitHub-recognized same-repository closing issue, and the published Wiki is not preserved in the source tree.

Without a repository-local contract, automated contributors can choose the wrong validation path or modify unrelated product surfaces. Without an enforced closing issue, changes can reach review without an auditable rationale and acceptance criteria.

Proposed governance baseline

• Replace the generic root AGENTS.md with eApps-specific architecture, validation, security, and change-scope guidance.
• Add .github/workflows/linked-issue.yml from the organization canonical template, pinning both references to 92cb596c773496ec4df76717e8acf0e6b7700f73.
• Reconcile the local pull request template so human-authored PRs require a GitHub-recognized closing keyword for an issue in this repository while retaining native/platform test checklists.
• Consolidate the duplicate case-only PR template paths so behavior is deterministic on case-insensitive systems.
• Mirror the six currently published Wiki pages into docs/wiki/ for reviewable history and offline access.

Acceptance criteria

• The reusable policy caller has read-only permissions and uses the full immutable policy SHA in both uses and policy_ref.
• AGENTS.md identifies the major eApps delivery surfaces and their appropriate validation paths.
• The PR template contains an explicit Fixes #123 same-repository requirement and preserves eApps-specific checks.
• docs/wiki/ contains Home.md, Getting-Started.md, Development.md, Security.md, FAQ.md, and _Sidebar.md, byte-identical to the published Wiki revision.
• YAML parsing, Markdown checks for authored governance files, relative Wiki links, and the repository functional/performance/simulation suites are validated.