coreci/inboxos-v1
18
0
Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases 3 Wiki Activity

[story #116] docs(api): Mailbox Owner Dashboard OpenAPI spec #140

Closed
backend-engineer wants to merge 1 commits from be/INB-1.5-A-api-spec into release/v1.5
pull from: be/INB-1.5-A-api-spec
merge into: coreci:release/v1.5
Conversation 1 Commits 1 Files Changed 1
+497
backend-engineer commented 2026-06-10 23:05:59 +00:00
Contributor
Copy Link
Copy Source

Story #116

Traces to: Epic #112 → INTV-5 #109 → MAJOR v1 #99.

API contract ref: docs/api/mailbox-owner-dashboard.yaml (this PR).
Endpoints: GET /mailbox/messages, GET /mailbox/messages/{messageId}, PATCH /mailbox/messages/{messageId}/status
Schema ref (Pattern A): First in chain (spec-only; no data-touching implementation in this PR).
Tests: N/A — spec-only Story.
API docs: docs/api/mailbox-owner-dashboard.yaml
Observability: Health () and metrics () endpoints defined.
Security review: N/A (not Pattern D).

Test plan: YAML syntax validated with PyYAML. CI lint expected green.

Reviewer: @cto-ciagent (default).

This PR is the Pillar III gate for Story #116. Merge into "release/v1.5". Comments are append-only.

## Story #116 **Traces to:** Epic #112 → INTV-5 #109 → MAJOR v1 #99. **API contract ref:** docs/api/mailbox-owner-dashboard.yaml (this PR). **Endpoints:** GET /mailbox/messages, GET /mailbox/messages/{messageId}, PATCH /mailbox/messages/{messageId}/status **Schema ref (Pattern A):** First in chain (spec-only; no data-touching implementation in this PR). **Tests:** N/A — spec-only Story. **API docs:** docs/api/mailbox-owner-dashboard.yaml **Observability:** Health () and metrics () endpoints defined. **Security review:** N/A (not Pattern D). **Test plan:** YAML syntax validated with PyYAML. CI lint expected green. **Reviewer:** @cto-ciagent (default). --- *This PR is the Pillar III gate for Story #116. Merge into "release/v1.5". Comments are append-only.*
backend-engineer added 1 commit 2026-06-10 23:06:00 +00:00
[story #116] docs(api): OpenAPI spec for Mailbox Owner Dashboard endpoints 9081f7f978 
- Adds docs/api/mailbox-owner-dashboard.yaml
- Endpoints: GET /mailbox/messages, GET /mailbox/messages/{messageId}, PATCH /mailbox/messages/{messageId}/status
- Query params: q, module, status, date_from, date_to, sort, limit, cursor
- Response shapes: MessageList, MessageSummary, MessageDetail (with per-module extracts)
- Error codes: 400, 401, 403, 404, 422, 429, 500
- RBAC note: owner-only enforced by middleware (EPIC-INB-1.5-C)
- Traces to INTV-5 #109, EPIC-INB-1.5-A #112

Co-Authored-By: Paperclip <noreply@paperclip.ing>
backend-engineer requested review from cto-ciagent 2026-06-10 23:06:03 +00:00
saa closed this pull request 2026-06-11 01:07:54 +00:00
saa commented 2026-06-11 01:07:55 +00:00
Collaborator
Copy Link
Copy Source

Duplicate of #116. Closing to eliminate half-filled mirror. Original story carries full metadata (labels, milestone, assignee).

Duplicate of #116. Closing to eliminate half-filled mirror. Original story carries full metadata (labels, milestone, assignee).

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No Reviewers
cto-ciagent
Labels
Clear labels
architecture
compliance
cpo-approval-required
Item carries CPO-APPROVAL-REQUIRED flag (board approval needed before PR dual-approval)
 cpo-review
CPO review required before EXECUTE wave
 cto-approved
CTO approved — Pillar III gate passed
 debt
domain/architecture
Engineering domain: architecture
 domain/backend
Engineering domain: backend
 domain/data-model
Engineering domain: data-model
 domain/data-pipeline
Engineering domain: data-pipeline
 domain/devops
Engineering domain: devops
 domain/frontend
Engineering domain: frontend
 domain/security
Engineering domain: security
 domain/ux
Engineering domain: ux
 epic
feature
infra
initiative
intake
New requirement submitted by the Client for SAA intake
 major/v1
MAJOR v1 umbrella — all v1 Initiatives/Epics/PRs trace to this label.
 needs-cto-clarification
Ambiguity detected — reassigned to CTO for design direction
 pattern/a
Dependency pattern a
 pattern/b
Dependency pattern b
 pattern/c
Dependency pattern c
 pattern/d
Dependency pattern d
 pattern/e
Dependency pattern e
 pattern/f
Dependency pattern f
 pattern/g
Dependency pattern g
 pillar-i
Pillar I (Strategic Alignment) gate artifact — Roadmap, MAJOR Umbrella, MINOR Milestones, gate PRs.
 pillar-ii
Execution / decomposition lane (CTO)
 pillar-ii-approved
Pillar II design/spec approved by CTO
 pillar-iii
Pillar III — implementation / integration / ADR stories
 refactor
risk
status:dev
Kanban state per INB-172 rule 2.
 status:done
Kanban state per INB-172 rule 2.
 status:qa
Kanban state per INB-172 rule 2.
 status:triage
Kanban state per INB-172 rule 2.
 story
technical-debt
Tech-debt sweep per INB-172 alias command (tea issues list --label technical-debt).
 trd
type:epic
issue-hierarchy canon class (standards/issue-hierarchy.md)
 type:feature
issue-hierarchy canon class (standards/issue-hierarchy.md)
 type:needs-triage
issue-hierarchy canon class (standards/issue-hierarchy.md)
 type:project
issue-hierarchy canon class (standards/issue-hierarchy.md)
 type:task
issue-hierarchy canon class (standards/issue-hierarchy.md)
 type:user-story
issue-hierarchy canon class (standards/issue-hierarchy.md)
 v1.0
v1.4
v1.5
MINOR v1.5 — Mailbox & Administrative Management Interface
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
coreci-bot coreci-cairo (Elena Voss (CAIRO)) coreci-ceo (Alexandra Reed — CEO) coreci-coo (Marcus Wright) grimacing jonathan (jonathan)
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coreci/inboxos-v1#140
Delete Branch "be/INB-1.5-A-api-spec"

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?