docs: amend constitution to v1.1.0 (add documentation guidelines)

- Add prohibition of auto-generated summary/report documents
- Clarify acceptable documentation types
- Establish rationale for living documentation approach
- Update version from 1.0.0 to 1.1.0 (MINOR)
- Last amended date: 2025-10-07

Author: overtrue

.specify/memory/constitution.md

@@ -1,11 +1,14 @@
 <!--
 Sync Impact Report:
-Version change: Initial → 1.0.0
-Added sections:
-- Core Principles: Component-First, TypeScript-First, User Experience, Internationalization, Performance
-- Quality Standards: Code quality and testing requirements
-- Development Workflow: Contribution and review process
-Templates requiring updates: ✅ All templates validated
+Version change: 1.0.0 → 1.1.0
+Modified sections:
+- Development Workflow: Added "Documentation Guidelines" subsection
+Added principles/rules:
+- Prohibition of auto-generated summary/report documents
+Templates requiring updates:
+- ✅ .specify/templates/plan-template.md (reviewed, no changes needed)
+- ✅ .specify/templates/spec-template.md (reviewed, no changes needed)
+- ✅ .specify/templates/tasks-template.md (not changed, guideline applies to all outputs)
 Follow-up TODOs: None
 -->
 
@@ -79,6 +82,33 @@ Bundle size must be optimized through code splitting and lazy loading. API calls
 - Performance impact must be assessed for large changes
 - Accessibility compliance must be verified
 
+### Documentation Guidelines
+
+**Prohibition of Generated Summary Documents**
+
+AI agents and automated tools MUST NOT create summary, report, or analysis documents such as:
+
+- Coverage reports (e.g., `COVERAGE_REPORT.md`)
+- Implementation summaries
+- Progress reports
+- Analysis documents
+- Any form of procedurally generated documentation files
+
+**Rationale**: Generated documentation becomes stale immediately, creates maintenance burden, and clutters the repository. Test coverage and implementation progress are better tracked through:
+
+- CI/CD pipeline outputs
+- Version control history
+- Living documentation in README files
+- Inline code comments and JSDoc
+- Test files themselves
+
+**Exceptions**: The only acceptable documentation files are:
+
+- Hand-written README files explaining project setup and architecture
+- API documentation generated by tools like TypeDoc (but only when explicitly configured)
+- Changelog files maintained through conventional commits
+- Project constitution and specification documents (`.specify/` directory)
+
 ## Governance
 
 ### Amendment Process
@@ -105,4 +135,4 @@ Constitution changes require:
 - Use CLAUDE.md for runtime development guidance specific to Claude
 - Regular reviews ensure principles remain relevant
 
-**Version**: 1.0.0 | **Ratified**: 2025-01-27 | **Last Amended**: 2025-01-27
+**Version**: 1.1.0 | **Ratified**: 2025-01-27 | **Last Amended**: 2025-10-07