docs(adr): add rpc discovery command alternative to ADR-discovery
Add Alternative 4 to the Alternatives Considered section of
ADR-discovery, evaluating a dedicated command
as an approach for local device discovery via PATCH.
Document pros (clear CLI intent, single-responsibility,
independent flag evolution, isolated test surface) and cons
(duplicates SyncDeviceInfo logic, grows CLI surface, no v1
capability delta over ).
Mark as rejected: equivalent functionality is covered by the
extension decided in this ADR; can be
revisited if amtinfo and discovery concerns diverge in a
future iteration.
Also update ADR status from Proposed → Accepted in both
ADR-discovery.md and Home.md, and fix the docs link to point
to the canonical docs repository.
docs: corrected the number of api's
docs(adr): revise discovery storage and agent mechanism decisions
Prior version proposed a separate discoveryInfo column and a
long-running rpc-discovery daemon. Both are replaced:
- Storage: all new fields (OS, LMS, UPID, TLS mode, adapters, etc.)
added as flat keys inside the existing deviceInfo JSON column;
no new column, no schema change, fully backward-compatible
- Agent: extend rpc amtinfo --sync (existing binary) instead of a
new standalone daemon; OS scheduler (Task Scheduler / systemd
timer) owns cadence, reboot persistence, and retry with zero
in-process state
- Auth: document both username/password and pre-issued JWT modes;
JWT preferred for production deployments
- API change #3: expand GET /api/v1/devices with full filter/sort
parameter set (filter[skuType], filter[currentMode],
filter[lmsInstalled], filter[osName], sort, order)
- Inline setup detail replaced with link to DMT documentation
docs: clarified the agent download mechanism to be from GH release
docs: updated the discovery ADR references
docs: added the ADR and Proposal for the discovery related features