General: Remove docs/, record the first HONOR/MagicOS lead in the ledger - #67
Merged
Conversation
Both remaining files under docs/ were added after 0566324, which deleted the folder with the stated policy that source of truth is the code plus its comments and the .claude rules, not separately-maintained docs. They had already decayed in exactly the way that commit predicted. docs/plans/lineageos-adapter.md is fully superseded: the provider-to-mechanism table is a real enum with the reasoning as KDoc in LineageHealthProbe, the qualification rationale is in the device-qualification skill, and the gate, keys and SELinux trap are in rules/privileged-access.md. It is also wrong now, still describing the codename allowlist as empty pending a Pixel 6 run that came back NO-GO. docs/support/kindmail-system-prompt.md was inert. The support assistant loads prompts from Gmail threads, so editing the repo copy changed no reply, and the two copies had drifted in both directions: Gmail carried a Play closed-beta section and the revised Pro wording, the repo carried the LineageOS wizard exception. That paragraph was folded into the live prompt before deletion, along with fixes for the Xiaomi HyperOS 3 and GrapheneOS rows the table was missing. Adds a HONOR/MagicOS entry to the qualification ledger for the Magic8 Pro BKQ-N49 discovery report (issue #66): the 2x2 mode table, both keys reading 1-when-disabled, and the two blockers, no behavioral evidence for either key and no identified gate signal for MagicOS. Also repoints a comment in OemChargingShortcuts that still referenced docs/SAMSUNG_SPIKE_RESULTS.md, deleted in 0566324.
d4rken
added
documentation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
No user-facing behavior change. Deletes the
docs/folder (two files) and adds a HONOR/MagicOS entry to the device-qualification ledger for the Magic8 Pro discovery report tracked in #66.Technical Context
docs/was re-created against a decision already made.0566324deleted the folder with the stated policy that source of truth is the code plus its comments and the.clauderules, not separately-maintained docs. Both surviving files were added after that commit and had already decayed in exactly the predicted way.LineageHealthProbe, the qualification rationale is in the device-qualification skill, and the gate/keys/SELinux trap are inrules/privileged-access.md. The doc still describes the codename allowlist as empty pending a Pixel 6 run that came back NO-GO, so a reader finding it beside the authoritative rules gets misled.SystemPromptCataloghas no file-based storage), so editing the repo copy changed no reply. The two copies had drifted in both directions: Gmail carried a Play closed-beta section and revised Pro wording, the repo carried the LineageOS wizard exception. That paragraph was folded into the live Gmail prompt before deletion, together with fixes for the Xiaomi HyperOS 3 and GrapheneOS rows its device table was missing. Nothing in this diff can restore those, they live in Gmail.user_reported_effectareunsure) andasw_ui_stateis the same_ui_-named shape as the ColorOS_statusmirrors thatOnePlusChargingAdapterdeliberately never writes. No MagicOS gate signal has been identified either. The entry exists so the lead survives outside an inbox, not to justify adapter work.OemChargingShortcutsthat still referenceddocs/SAMSUNG_SPIKE_RESULTS.md, deleted back in0566324.