Conversation
analyze what changed: 1. A new directory structure was created in `.ai-context/`: - `SKILL.md` - new file (entry point for knowledge tiers) - `DYNAMICS.md` - new file (active issues & constraints) - `references/ARCHITECTURE.md` - new file - `references/DECISIONS.md` - new file - `references/PROJECT-ESSENCE.md` - new file - `meta/MAINTENANCE.md` - new file 2. Old files were deleted: - `.ai-context/architecture-decisions.md` - `.ai-context/core/constraints.md` - `.ai-context/core/modules.map` - `.ai-context/domains/domain-logic.md` - `.ai-context/domains/pipeline.md` - `.ai-context/domains/tools.md` - `.ai-context/manifest.yaml` - `.ai-context/project.snapshot` - `.ai-context/prompts/coding-context.md` 3. `AGENTS.md` was significantly updated/reorganized So this is a major restructuring of the `.ai-context/` knowledge base from a flat structure to a tiered structure with better organization. The new structure follows the tiered knowledge system (0-3) mentioned in the AGENTS.md. Let me write a concise commit message: Subject: Restructure .ai-context knowledge base into tiered system Body should briefly explain the change without repeating the subject. The key points: - Flat structure → tiered structure (PROJECT-ESSENCE, ARCHITECTURE, DECISIONS, DYNAMICS) - New SKILL.md entry point - Improved maintenance workflow Let me follow the rules: - Limit subject to 50 chars: "Restructure .ai-context into tiered knowledge system" = 50 chars ✓ - Capitalize first letter, imperative mood, avoid trailing punctuation - Blank line separating subject and body - Body wraps at 72 characters, keeps it concise - Subject and body should complement each other, not repeat The commit message conveys the organizational shift without redundancy, using action-oriented language and a clean structure that highlights the key architectural improvement. </think> Restructure .ai-context into tiered knowledge system Organize AI knowledge base with tiered files (PROJECT-ESSENCE, ARCHITECTURE, DECISIONS, DYNAMICS), add SKILL.md entry point, and add maintenance guide. Consolidate scattered files into structured references/ directory.
AdkError::Tool constructor changed to AdkError::tool in adk-rust 0.5.0. Updated all tool error constructions across 12+ modules. Refactored chat UI CSS with improved message styling and component classes. Added get_save_tool_name and get_artifact_filename helpers to stage_executor.
The `get_artifact_filename` function now returns `Option<&'static str>` instead of `&'static str`, returning `None` for stages like "coding" that don't produce a single artifact file. All artifact path handling in `execute_stage_with_instruction` now works with the `Option`, treating stages without artifact files as successful when they produce text output or when no output but no artifact expected stages without artifacts are now considered successful based on execution completion rather than artifact existence
The preview command now detects projects with HTML files but no frontend/backend configuration (vanilla HTML or static sites) and serves them via a built-in static server on port 8000. This allows previewing static HTML projects without requiring a standard frontend framework setup.
Added avatar images for PM, Designer, RD, and QA roles with automatic stage/agent mapping. Replaces generic Ant Design icons with custom visuals in chat messages and thinking indicators.
Add comprehensive CSS for markdown elements (headings, paragraphs, lists, blockquotes, tables, code blocks) to improve readability of rendered artifacts. Remove border-radius from artifact-content to align with new design.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.