SmartPerfetto Documentation Center

English | 中文

This repository keeps only documentation that still defines the current user, architecture, runtime, or maintainer contract. Start with the Quick Start. Git history, issues, and PRs retain implementation history; completed plans, review reports, research dumps, and agent evidence are not maintained as permanent documentation.

Usage And Operations

• Quick Start
• Windows Setup And Run
• Feature Overview
• Basic Usage
• Configuration
• Application Updates
• Agent-Assisted GitHub Feedback
• Self-Evolution Usage And Acceptance
• Code-Aware Analysis
• Multi-Trace Analysis Result Comparison
• Android Internals Knowledge
• Troubleshooting

Reference

• CLI
• HTTP/SSE API
• MCP Tools
• Skill System
• Platform Compatibility And Verification Boundaries
• Release
• Portable Packaging
• Windows Launcher

Core Architecture

• Architecture Overview: product entries, data flow, and output contract.
• Technical Architecture: component boundaries and change map.
• Agent Runtime: runtime, provider, and session semantics.
• Dual Trace Workspace: dual-pane and comparison state machine.
• Private Analysis Context: authorization, continuity, and deletion.
• Self-Improving: currently integrated and explicitly unavailable capabilities.
• Use the Self-Evolution guide for the user entry point, permissions, persistence, and acceptance tests.
• Use Agent-Assisted GitHub Feedback when a regular user turns an analysis gap into an external report; it never enters Self-Evolution or GitHub automatically.
• Data Contract: DataEnvelope, Query Review, Analysis Receipt, UI Actions, and cross-surface projections.

Contribution And Governance

• Contributing Guide
• Agent Entry Rules
• Product Surface Rules
• Testing Rules
• Security Policy
• Sponsorship And Commercial Support

Documentation Retention Policy

• Commit only documents required by current users, architecture, runtime, or maintenance workflows.
• Do not commit completed plans, RFC implementation logs, reviews, research dumps, presentation sources, or agent evidence. Merge durable conclusions into a core document.
• Strategies, prompt templates, Skill SOPs, test fixtures, licenses, and pre-built UI help happen to use Markdown but are runtime code or release assets, not ordinary docs.
• npm run verify:docs checks links, images, npm scripts, CLI coverage, release commands, and retired documentation topology. npm run verify:i18n checks bilingual product surfaces.

Runtime-Read Content

docs/rendering_pipelines/ is Android 17 teaching content synchronized from a pinned upstream commit and copied into backend/dist/rendering_pipelines/ during builds. Moving or changing it requires synchronized pipeline catalog and Skill references plus:

npm run verify:rendering-pipelines
cd backend && npm run validate:skills