Repository navigation
docs(known-issues): keep observed failures, drop backlog - #149
Merged
Merged
Conversation
The folder had drifted from "platform behaviour we cannot fix, plus the workaround" into design notes and backlog wearing the entry template. Entries 12, 14 and 15 each carried a "Статус реализации: не реализовано" marker; nothing in 01-11 does, because an old entry describes something already worked around in code. CLAUDE.md sends every agent here before touching a failure mode, so an entry that states an unimplemented rule reads as a rule to apply. - 14 deleted. It had no observed symptom, and its three findings are already tracked as issues #139, #140 and #141. It recommended swapping SynchWihSysTree for RecreatePinMap in PlanExecutor on an untested hypothesis. - 13 deleted. No NtoLib code path changes if its rule is followed: the vendor calls CreateItems, we do not. Its one concrete point, that "issued" is not "connected", already lives in 11 and in opc-tree-manager.md 8.3. Its incident figures contradicted 12: "1158 of 1047" against 1158 of 1228. - 15 deleted. Both halves are NtoLib defects, not vendor behaviour: the IsGroup predicate, fixed in a35fd18, and IsHistorySupport, tracked as issue #142. The IsHistorySupport cause moves into opc-tree-manager.md 3.4 where the consequence already was, and the IsGroup cause into the code comment that needed it. - 12 trimmed from 126 lines to 75: the incident, the symptom, why the index is not ours to control, and the organizational workaround. The addressing model it restated stays in the primer, reached by a pointer. - 11 lost two links to Docs/plans/iconnect-investigation-log.md, deleted in 3618ee8. CLAUDE.md now states the gate: an entry needs an observed symptom and a workaround that exists today; work not done yet is an issue. The primer gains the "OPC UA node addressing" section that entry 12 points at.
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
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.
Summary
Docs/known_issues/had drifted from "vendor platform behaviour we cannot fix, plus the workaround" into design notes and backlog wearing the entry template. Entries 12, 14 and 15 each carried aСтатус реализации: не реализованоmarker; no entry in 01-11 does, because an old entry describes something already worked around in code.CLAUDE.mdsends every agent to this folder before touching a failure mode, so an entry stating an unimplemented rule reads as a rule to apply.Type of change
Changes
CreateItems, we do not. Its one concrete point, thatissuedis notconnected, already lives in 11 and inopc-tree-manager.md8.3. Its incident figures contradicted 12: "1158 of 1047" against 1158 of 1228SynchWihSysTreeforRecreatePinMapinPlanExecutoron an untested hypothesisIsGrouppredicate, fixed ina35fd18, andIsHistorySupport, tracked as issue #142Docs/plans/iconnect-investigation-log.md, deleted in3618ee8Knowledge kept, not dropped: the
IsHistorySupportcause moved intoopc-tree-manager.md3.4 where the consequence already was, and theIsGroupcause into the code comment inOpcProtocolAccessor.csthat needed it. Both code pointers to the deleted entry 15 are gone.CLAUDE.mdgains the gate: an entry needs an observed symptom and a workaround that exists today, even an organizational one; work not done yet is a GitHub issue.This PR also carries the
OPC UA node addressingsection inmasterscada-fb-primer.mdthat entry 12 points at, which was sitting uncommitted in the working tree.Testing
dotnet build NtoLib.sln— 0 errors, 0 warningsdotnet test NtoLib.sln— 373 passedterseon the two touched.csfiles — exit 0grepfor links to 13, 14, 15 and to the deleted investigation log — none left outsideDocs/plans/completed/, which is an archive