Foundational: full scope set, read+write direction, re-consent #17

New Issue

2026-06-27T16:58:00Z

Latte commented

2026-06-27 16:58:00 +00:00

Prerequisite for the expanded roadmap. The project moves from read-only to read + write (character + corp), per owner decision.

Enable the full scope set on the EVE application (all scopes listed by the owner)
Expand config.SCOPES to the full list (env-overridable kept)
Handle re-consent: changing scopes requires familiar login again per character
Update README: drop "read-only by design"; document the new read+write posture and the write-safety model
Split scope groups so a user can opt into read-only vs read+write at login (optional)

Blocks the write features in #15. Part of #14 / #15 / #16.

Prerequisite for the expanded roadmap. The project moves from **read-only** to **read + write** (character + corp), per owner decision. - [ ] Enable the full scope set on the EVE application (all scopes listed by the owner) - [ ] Expand `config.SCOPES` to the full list (env-overridable kept) - [ ] Handle re-consent: changing scopes requires `familiar login` again per character - [ ] Update README: drop "read-only by design"; document the new read+write posture and the write-safety model - [ ] Split scope groups so a user can opt into read-only vs read+write at login (optional) Blocks the write features in #15. Part of #14 / #15 / #16.

Latte referenced this issue from a commit

2026-06-27 17:04:08 +00:00

Foundational: full scope set + read+write direction

Latte commented

2026-06-27 17:04:54 +00:00

Code/docs part done on dev via PR #37:

Expand config.SCOPES to the full set (64 read + 9 write = 73), split into READ_SCOPES / WRITE_SCOPES; FAMILIAR_SCOPES still overrides for a read-only subset
README updated: no longer "read-only by design"; documents read+write + safe-by-default writes

Remaining (owner action + later work):

Enable all 73 scopes on the EVE application
Re-run familiar login per character to re-consent (current tokens only carry the Phase-2 read scopes)
Optional read-only vs read+write split at login UX — folds into write-safety #22

Code/docs part done on `dev` via PR #37: - [x] Expand `config.SCOPES` to the full set (64 read + 9 write = 73), split into `READ_SCOPES` / `WRITE_SCOPES`; `FAMILIAR_SCOPES` still overrides for a read-only subset - [x] README updated: no longer "read-only by design"; documents read+write + safe-by-default writes Remaining (owner action + later work): - [ ] Enable all 73 scopes on the EVE application - [ ] Re-run `familiar login` per character to re-consent (current tokens only carry the Phase-2 read scopes) - [ ] Optional read-only vs read+write split at login UX — folds into write-safety #22

Latte commented

2026-06-27 19:01:48 +00:00

Done. Owner enabled the full scope set on the EVE app and re-logged in all 3 characters; verified live read-only against ESI — all 3 carry 73 scopes and the new-scope reads (contacts, mail, industry, market orders, loyalty, standings) return data with no invalid_scope/403 at character level. The optional read-only-vs-write login split is covered by FAMILIAR_SCOPES (read-only subset) + the write-safety toggle (#22). Closing.

Done. Owner enabled the full scope set on the EVE app and re-logged in all 3 characters; verified live read-only against ESI — all 3 carry 73 scopes and the new-scope reads (contacts, mail, industry, market orders, loyalty, standings) return data with no `invalid_scope`/403 at character level. The optional read-only-vs-write login split is covered by `FAMILIAR_SCOPES` (read-only subset) + the write-safety toggle (#22). Closing.

Latte closed this issue

2026-06-27 19:01:51 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Hiddenden/familiar#17