docs: name the CI exposure in the opening list #91

Merged

branderson merged 1 commits from readme-ci-bullet into main 2026-08-06 10:15:45 -07:00

Conversation 1 Commits 1 Files Changed 1

+8

dejima-agent commented 2026-08-06 10:02:14 -07:00

Collaborator

Copy Link

Copy Source

Summary generated by LLM agent

The opening list — "most of what running an agent unattended actually takes"
— is where a reader decides whether this is a serious tool. It ran to nine
bullets without mentioning the one exposure the container cannot close.

CI appeared around a thousand lines later, under its own heading. That is
after the point where someone has already pointed dejima at a project and
handed a session push access, which is the moment the exposure begins.

This adds a tenth bullet, placed directly after the PR and issue workflow —
where push access is introduced, and therefore where its consequence belongs.

It is deliberately the odd one out. Every other entry is something dejima
provides; this one is something it does not, and says so:

The container bounds what a session reaches directly — not what it can
arrange to have run elsewhere.

Both destinations are named there rather than deferred: docs/ci.md for the
reasoning, and dejima-ci-hardener for the tool that does the work.

Testing

Documentation only. No claim is made here that the existing CI section does
not already make at greater length; this is the same content stated where it
is needed earlier, and the links are the two that section already carries.

**Summary generated by LLM agent** The opening list — "most of what running an agent unattended actually takes" — is where a reader decides whether this is a serious tool. It ran to nine bullets without mentioning the one exposure the container cannot close. CI appeared around a thousand lines later, under its own heading. That is after the point where someone has already pointed dejima at a project and handed a session push access, which is the moment the exposure begins. This adds a tenth bullet, placed directly after the PR and issue workflow — where push access is introduced, and therefore where its consequence belongs. It is deliberately the odd one out. Every other entry is something dejima provides; this one is something it does not, and says so: > The container bounds what a session reaches directly — not what it can > arrange to have run elsewhere. Both destinations are named there rather than deferred: `docs/ci.md` for the reasoning, and dejima-ci-hardener for the tool that does the work. ## Testing Documentation only. No claim is made here that the existing CI section does not already make at greater length; this is the same content stated where it is needed earlier, and the links are the two that section already carries.

dejima-agent added 1 commit 2026-08-06 10:02:15 -07:00

docs: name the CI exposure in the opening list ... 1e65852f2c

The list of what running an agent unattended takes is where a reader decides
whether this is a serious tool, and it ran to nine bullets without mentioning
the one exposure the container cannot close. CI came ~1000 lines later, which
is after the point where someone has already pointed dejima at a project and
given a session push access.

The bullet is deliberately the odd one out. Every other entry is something
dejima provides; this one is something it does not, and says so - the
container bounds what a session reaches directly, not what it can arrange to
have run elsewhere. Both destinations get named there rather than deferred:
docs/ci.md for the reasoning, dejima-ci-hardener for the tool.

Placed directly after the PR and issue workflow, which is where push access
is introduced and therefore where the consequence belongs.

branderson approved these changes 2026-08-06 10:15:37 -07:00

branderson merged commit 5a2d460075 into main 2026-08-06 10:15:45 -07:00

branderson referenced this issue from a commit 2026-08-06 10:15:46 -07:00

Merge pull request 'docs: name the CI exposure in the opening list' (#91) from readme-ci-bullet into main

Sign in to join this conversation.

Reviewers

No Reviewers

branderson

Labels

Clear labels

Compat/Breaking

Breaking change that won't be backward compatible

Kind/Bug

Something is not working

Kind/Documentation

Documentation changes

Kind/Enhancement

Improve existing functionality

Kind/Feature

New functionality

Kind/Security

This is security issue

Kind/Testing

Issue or pull request related to testing

Priority

Critical

1

The priority is critical

Priority

High

2

The priority is high

Priority

Low

4

The priority is low

Priority

Medium

3

The priority is medium

Reviewed

Confirmed

1

Issue has been confirmed

Reviewed

Duplicate

2

This issue or pull request already exists

Reviewed

Invalid

3

Invalid issue

Reviewed

Won't Fix

3

This issue won't be fixed

Status

Abandoned

3

Somebody has started to work on this but abandoned work

Status

Blocked

1

Something is blocking this issue or pull request

Status

Need More Info

2

Feedback is required to reproduce issue or to continue work

No labels

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

branderson dejima-agent

No Assignees

2 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: dejima/dejima#91