Define task-scoped Gitea MCP execution profile model #12

New Issue

2026-07-01T11:15:51-05:00

jcwalker3 commented

2026-07-01 11:15:51 -05:00

Parent

Roadmap #10 — Task-scoped MCP execution profiles for LLM-operated Gitea workflows

Problem

We want roles to be fluid across LLM sessions. A specific LLM should not permanently be “the reviewer” or “the merger.”

Instead, each task should select an appropriate MCP execution profile.

Scope

Design and document a Gitea MCP execution profile model.

Example profiles:

gitea-issue-manager
gitea-author
gitea-reviewer
gitea-merger
gitea-owner

Each profile should define:

profile name
authenticated username
allowed operations
forbidden operations
token source name
audit label
whether the profile can approve
whether the profile can merge
whether the profile can push branches
whether the profile can mutate issues

Acceptance criteria

Execution profile concept is documented.
Profile metadata shape is defined.
Allowed/forbidden operation model is defined.
The docs explain that LLMs are not roles; profiles are roles.
The docs explain that a task may use any eligible profile.
The docs require fail-closed behavior if profile identity is unknown.
No tokens or secrets are exposed.

Non-goals

Do not implement profile switching yet.
Do not implement approval or merge workflows yet.
Do not add Jenkins/Ops/deploy behavior.

Proposed labels

mcp · gitea · profiles · security · design

## Parent Roadmap #10 — Task-scoped MCP execution profiles for LLM-operated Gitea workflows ## Problem We want roles to be fluid across LLM sessions. A specific LLM should not permanently be “the reviewer” or “the merger.” Instead, each task should select an appropriate MCP execution profile. ## Scope Design and document a Gitea MCP execution profile model. Example profiles: ```text gitea-issue-manager gitea-author gitea-reviewer gitea-merger gitea-owner ``` Each profile should define: * profile name * authenticated username * allowed operations * forbidden operations * token source name * audit label * whether the profile can approve * whether the profile can merge * whether the profile can push branches * whether the profile can mutate issues ## Acceptance criteria * Execution profile concept is documented. * Profile metadata shape is defined. * Allowed/forbidden operation model is defined. * The docs explain that LLMs are not roles; profiles are roles. * The docs explain that a task may use any eligible profile. * The docs require fail-closed behavior if profile identity is unknown. * No tokens or secrets are exposed. ## Non-goals * Do not implement profile switching yet. * Do not implement approval or merge workflows yet. * Do not add Jenkins/Ops/deploy behavior. ## Proposed labels `mcp` · `gitea` · `profiles` · `security` · `design`

jcwalker3 referenced this issue

2026-07-01 11:16:43 -05:00

Roadmap: Task-scoped MCP execution profiles for LLM-operated Gitea workflows #10

jcwalker3 added the mcp security gitea documentation labels 2026-07-01 11:28:16 -05:00

jcwalker3 referenced this issue from a commit

2026-07-01 12:03:26 -05:00

docs: define task-scoped Gitea MCP execution profile model (#12)

jcwalker3 referenced a pull request that will close this issue

2026-07-01 12:03:47 -05:00

docs: define task-scoped Gitea MCP execution profile model (#12) #21

jcwalker3 referenced this issue

2026-07-01 12:05:58 -05:00