Scaled-Tech-Consulting/Gitea-Tools
2
0
Fork 0
Code Issues 17 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Update safety/boundary docs for Jenkins and GlitchTip #79

New Issue
Open
opened 2026-07-02 05:46:39 -05:00 by jcwalker3 · 0 comments
jcwalker3 commented 2026-07-02 05:46:39 -05:00
Owner
Copy Link
Copy Source

Update existing MCP Control Plane documentation to explicitly include Jenkins and GlitchTip boundaries.

Docs to consider:

  • docs/tool-boundaries.md
  • docs/safety-model.md
  • docs/credential-isolation.md
  • docs/release-workflows.md
  • docs/gitea-execution-profiles.md

Acceptance criteria

  • Jenkins boundary is documented.
  • GlitchTip/observability boundary is documented.
  • Read-only-first policy is documented.
  • Mutation gating requirements are documented.
  • Credential isolation is documented.
  • Orchestrator role is documented as coordination, not credential consolidation.
  • Jenkins build triggers are explicitly deferred.
  • GlitchTip-to-Gitea filing is documented as a gated workflow.
Update existing MCP Control Plane documentation to explicitly include Jenkins and GlitchTip boundaries. Docs to consider: * `docs/tool-boundaries.md` * `docs/safety-model.md` * `docs/credential-isolation.md` * `docs/release-workflows.md` * `docs/gitea-execution-profiles.md` ## Acceptance criteria * Jenkins boundary is documented. * GlitchTip/observability boundary is documented. * Read-only-first policy is documented. * Mutation gating requirements are documented. * Credential isolation is documented. * Orchestrator role is documented as coordination, not credential consolidation. * Jenkins build triggers are explicitly deferred. * GlitchTip-to-Gitea filing is documented as a gated workflow.
jcwalker3 added the mcpsecuritydocumentationjenkinsglitchtip labels 2026-07-02 05:46:59 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
architecture
Architecture / structural design
 bug
chore
design
Design / investigation, no implementation
 documentation
Docs / runbooks
 gitea
Gitea MCP workflow
 glitchtip
GlitchTip integration
 important
integration
Integration testing
 jenkins
Jenkins integration
 labels
Label taxonomy management
 mcp
MCP server / tooling
 mutating
Mutating action; requires gating
 nice-to-have
portability
Cross-platform / portability
 read-only
Read-only, no mutation
 refactor
Code refactor / restructure
 release
Release / versioning
 reliability
Reliability / failure handling
 roadmap
Roadmap / umbrella issue
 security
Security / trust boundary
 status:in-progress
Issue is being worked on
 testing
Tests / test coverage
 tracker
Issue tracker hygiene / meta
 workflow
Cross-tool workflow
No Label documentation glitchtip jenkins mcp security
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
jcwalker3 sysadmin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#79
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?