Skip to content

chore(agents): untrack .mcp.json — internal agent infra in a public repo - #70

Merged
Nexlab-One merged 1 commit into
mainfrom
chore/untrack-mcp-json
Jul 29, 2026
Merged

chore(agents): untrack .mcp.json — internal agent infra in a public repo#70
Nexlab-One merged 1 commit into
mainfrom
chore/untrack-mcp-json

Conversation

@Nexlab-One

Copy link
Copy Markdown
Contributor

.mcp.json declares project-scoped MCP servers (akira-mcp-board, akira-mcp-grc) — Enkom-internal agent infrastructure. Nobody outside Enkom has those commands on PATH, so for an external contributor the file is dead config that only fails to start, and it names internal tooling in the one Enkom repo with an external audience.

Every sibling of this file is already ignored — .cursor/, .claude/, .agents/, AGENTS.md (.gitignore:237-241). .mcp.json was simply missed when that block was written; it came in via 5847caa alongside the hermes-board mount. This adds it to the same block.

The file stays on disk and keeps working locally — only tracking is removed, so the agent tooling can keep regenerating it without producing a diff.

This does not unpublish anything. .mcp.json has been on public main since 5847caa and remains in history; purging it would need a history rewrite + force-push. Not done here, and judged not worth it — the exposed content is two command names, with no paths, credentials, or tokens.

Verified .mcp.json is the only tracked file in this repo that references akira/hermes/kanban/grc, by name or by content.

`.mcp.json` declares project-scoped MCP servers (`akira-mcp-board`,
`akira-mcp-grc`). Those are Enkom-internal agent infrastructure: nobody
outside Enkom has those commands on PATH, so for an external contributor
this file is dead config that only fails to start. It also names internal
tooling in the one Enkom repo with an external audience.

Every sibling of this file is already ignored — .cursor/, .claude/,
.agents/, AGENTS.md (.gitignore:237-241). `.mcp.json` was simply missed
when that block was written; it was added by 5847caa alongside the
hermes-board mount. This adds it to the same block.

The file stays on disk and keeps working locally — only the tracking is
removed, so the agent tooling can keep regenerating it without producing
a diff.

Note this does not unpublish anything: .mcp.json has been on public
origin/main since 5847caa and remains in history. Purging it would need a
history rewrite + force-push. Not done here, and judged not worth it — the
exposed content is two command names, no paths, credentials, or tokens.
@github-actions

Copy link
Copy Markdown

🔒 Security Validation Report

Generated: Tue Jul 28 23:26:38 UTC 2026

📊 Summary

  • NIST compliance: success
  • Cryptographic validation: success
  • Constant-time operations: success
  • Memory safety: success
  • Dependency security: success
  • WASM security: success

✅ Overall Security Status: PASSED

All critical security validations passed successfully.

🔍 Details

This report covers:

  • NIST post-quantum algorithm compliance
  • Constant-time operation verification
  • Memory safety and zeroization checks
  • Dependency vulnerability scanning
  • WASM build artifact validation

📋 Next Steps

✅ Security validation passed. Code is ready for deployment.


Security validation passed! This code meets all security requirements.

@github-actions

Copy link
Copy Markdown

🔍 Pull Request Summary

Generated: Tue Jul 28 23:30:28 UTC 2026

📋 Validation Results

  • Core Validation: success
  • Security Validation: success
  • Test Coverage: success
  • WASM Compatibility: success
  • Documentation: success

✅ Overall Status: PASSED

🔒 Security Checklist

  • No classical cryptographic algorithms
  • Only SHA-3 family hash functions
  • Constant-time operations
  • Proper memory zeroization
  • Input validation
  • Error handling

📝 Review Notes

Please review the security implications of this change carefully.
All cryptographic changes require security team review.


Automated validation passed! This PR is ready for review.

@Nexlab-One
Nexlab-One merged commit ce01ca4 into main Jul 29, 2026
157 checks passed
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.

1 participant