Skip to content

Conversation

@maxachis
Copy link
Collaborator

@maxachis maxachis commented Feb 10, 2026

Summary

  • Added docs/ folder with six cross-cutting guides: architecture, API reference, development, testing, deployment, and collectors
  • Slimmed down README.md to a quick-start and documentation index table, moving detailed content into docs/
  • Added CLAUDE.md with project context for AI-assisted development (tech stack, key commands, architecture patterns, conventions)
  • Added .vscode/ to .gitignore

Existing per-module READMEs (39+) are untouched — the new docs complement them by covering topics that span multiple modules.

Test plan

  • Verify all links in README.md point to valid docs/ files
  • Verify internal cross-links between docs/ files resolve correctly
  • Confirm Mermaid diagrams render in docs/architecture.md
  • Review each doc for accuracy against current codebase

🤖 Generated with Claude Code

maxachis and others added 4 commits July 22, 2025 17:37
Reorganize documentation into dedicated guides (architecture, API reference,
development, testing, deployment, collectors) so cross-cutting topics are
discoverable without duplicating the existing per-module READMEs. Slim the
root README down to a quick-start and doc index. Add CLAUDE.md for AI-assisted
development context. Add .vscode/ to .gitignore.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@maxachis maxachis changed the base branch from main to dev February 10, 2026 23:07
@gitguardian
Copy link

gitguardian bot commented Feb 10, 2026

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
15086721 Triggered Generic Password 5de5f98 .github/workflows/test_app.yml View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants