feat: add license files for JavaScript assets and implement DocItem component

- Added LICENSE.txt file for JavaScript assets in the build directory, including licenses for NProgress and React libraries.
- Introduced a new runtime JavaScript file for handling module loading.
- Created a new DocItem component to manage document rendering and metadata handling in the Docusaurus theme.
- Implemented tests for the docs proxy server to ensure proper routing to the configured docsPort.
This commit is contained in:
catlog22
2026-02-06 10:25:24 +08:00
parent f9188eb0b6
commit a9b9ec48f1
91 changed files with 780 additions and 217 deletions

View File

@@ -184,3 +184,33 @@ Brief summary:
3. Guess field names - ALWAYS copy from schema
4. Assume structure - ALWAYS verify against schema
5. Omit required fields
---
## Post-Exploration: Exploration Notes (Generated by Orchestrator)
**Note**: This section is executed by the orchestrator (workflow-lite-plan) after all cli-explore-agents complete, NOT by this agent.
**Trigger**: After all exploration-{angle}.json files are generated
**Output Files**:
- `exploration-notes.md` - Full version (consumed by Plan phase)
- `exploration-notes-refined.md` - Refined version (consumed by Execute phase, generated after Plan completes)
**Full Version Structure (6 Sections)**:
1. **Part 1: Multi-Angle Exploration Summary** - Key findings from each angle
2. **Part 2: File Deep-Dive Summary** - Core files with relevance ≥ 0.7 (code snippets, line numbers, references)
3. **Part 3: Architecture Reasoning Chains** - Reasoning process for key decisions (problem → reasoning → conclusion)
4. **Part 4: Potential Risks and Mitigations** - Identified risks and mitigation strategies
5. **Part 5: Clarification Questions Summary** - Aggregated clarification_needs from all angles
6. **Part 6: Execution Recommendations Checklist** - Task checklist grouped by priority (P0/P1/P2)
**Refined Version Structure** (generated after Plan completes):
- Execution-relevant file index (only files related to plan.json tasks)
- Task-relevant exploration context (relevant findings per task)
- Condensed code reference (only plan-related files)
- Execution notes (constraints, integration points, dependencies)
**Consumption Pattern**:
- Plan phase: Fully consumes `exploration-notes.md`
- Execute phase: Consumes `exploration-notes-refined.md`, reduced noise, improved efficiency