ChrisTitusTech / ChrisTitusTech/warframe-linux

E01: P4: experimental inventory provider

Open
#9 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement phase:P4
Dominant language
Go
Stars
4
Forks
1
Avg merge
7m
Merged PRs (30d)
4

Description

Go implementation tracking epic

Selected stack: Go + Wails v2 + React/TypeScript + SQLite. Implementation starts on the next machine. Each child below is a separate PR; do not implement this epic in one PR.

Child tasks

  • E01a: Experimental acquisition boundary with fixtures
    • Merged prerequisites: I01a, F03b.
    • Acceptance: R9: disabled-by-default provider and consent/revoke states, redacted errors, expired-session/permission/cancel fixtures; no live acquisition yet.
  • E01b: Experimental memory/mobile adapter
    • Merged prerequisites: E01a.
    • Acceptance: R9: preserve notices; bounded cancellable acquisition, private DTO conversion, no credential logs or privilege escalation; synthetic failures first, separately authorized live evidence recorded as pending if absent.

Workflow

See TASKS.md, ROADMAP.md, and CONTRIBUTING.md. Aim for 100-400 handwritten changed lines per PR; split above 600 unless inseparable. Merge prerequisites before dependents. Update task evidence and this checklist after each completed PR. Close this epic only when every child passes; optional work can remain deferred.

All tasks are not started. Live game access and publication/merge actions follow the user's explicit authorization. The planning handoff does not claim runtime validation.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading TASKS.md, ROADMAP.md, and CONTRIBUTING.md, then verify the I01a and F03b prerequisites before choosing E01a or E01b. Work in separate PRs as specified; completion requires the listed consent, fixture, cancellation, notice, DTO, and logging safeguards, with no live acquisition unless separately authorized.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, react, sqlite, typescript
Domain
backend, mobile-dev, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.