Project maturity

This is the single location for the current project maturity summary and links to its review and lifecycle evidence. Need :status: fields and ADR status metadata remain authoritative for individual artifacts. The charts in Project Metrics read those fields directly.

1.2.0 release qualification, 2026-11-01

The owner authorized version 1.2.0 and complete qualification on current main. CR019 is already accepted and implemented. Candidate 1 passed 244 main automated cases (196 Python / 48 JavaScript), six separate CR019 browser supplements, a fresh Python 3.10 consumer, fresh capacity host and browser checks, maximum-size/hover SVG supplements and licensing checks. The owner confirmed native save/cancel and browser zoom behavior. Scoped CR019 verification advances without changing acceptance or earlier release records.

STV 1.2.0 release qualification records the candidate, exact artifacts, failed provisioning/publication attempts and successful retests, semantic coverage, cleanup approval and limits. Final consolidated gates are retained separately; hosted checks and owner release approval remain before publication. No commit, tag, push, release or deployment is claimed. Other platforms/browsers and occurrence mode remain deferred.

CR019 implemented development increment, 2026-10-28

Remember current view acros... (STV_CR_019) is implemented. The owner accepted the exact stakeholder amendment; CR019 scoped concept review, round 16 records scoped concept acceptance under the owner’s explicit review delegation. Store opt-in snapshots inde... (STV_SWR_073) through Restore presentation withou... (STV_SWR_075), revised Initialize collapsed state (STV_SWR_003) / Own a per-view persistent d... (STV_SWR_063), four browser component revisions, ADR012 and two new case designs are accepted. The input baseline is ae0c0b5a5af6a03e13fd3ef4911888bfaa66442e; exact accepted artifact identities are in the round-16 inventory.

The opt-in checkbox remembers current seeds/project page, rooted expansion, node positions, open-card age/order, pan and zoom. Saving is view-local and browser-local; safe current-graph validation, storage-error status and startup save gating preserve hidden-object/capacity constraints. No dependency or runtime version change, account, server, release or deployment is added.

CR019 development verification retains candidate/source identities, actual reports, commands, corrections and limitations. Results: 48 named Node checks, 107 non-browser Python checks, six feature checks and 40 targeted existing browser regression cases passed. One browser startup error required four retests; it is preserved rather than counted as an all-green suite. Strict documentation, publication, graph/evidence/test-coverage, diagram links/visual review and clean wheel/source-package verification passed. Authored diffs pass whitespace checks; generated minified JavaScript retains dependency template-string whitespace.

Verification is partial for amended obligations: actual development uses Linux Firefox 159.0, not the project’s Windows release platform. Formal case designs remain not_run pending qualification; no test execution or release pass is fabricated. Historical acceptance and 1.1.0 qualification remain valid only for their original identities. PR #6 carries the development change for review/merge.

CR019 owner acceptance and delivery authorization, 2026-10-28

The owner reviewed the exact RST in PR #6 and explicitly accepted Remember current view acros... (STV_CR_019), revised Initially collapse traced o... (STV_SHR_003) and Keep explicitly opened arti... (STV_SHR_057), and new Choose whether to remember ... (STV_SHR_062) through Recover safely when a remem... (STV_SHR_065). Their canonical status is accepted; verification remains not_assessed. Input revision: ae0c0b5a5af6a03e13fd3ef4911888bfaa66442e.

The same owner reply authorizes concept creation, review and implementation for CR019, including acceptance of clean reviewed concept artifacts under the invoked review workflow. Product release/deployment is separate. Historical pending statements below are superseded for this accepted stakeholder input.

CR019 stakeholder amendment awaiting owner review, 2026-10-28

The owner invoked stakeholder elicitation and manage-change to align and accept Remember current view acros... (STV_CR_019) and its stakeholder requirements. This increment is limited to that stakeholder boundary. STV_CR_019: Remember current view across page reloads contains the request, proposals, retained constraints and pending impact analysis.

Revised Initially collapse traced o... (STV_SHR_003) and Keep explicitly opened arti... (STV_SHR_057), plus new Choose whether to remember ... (STV_SHR_062) through Recover safely when a remem... (STV_SHR_065), are draft/not_assessed. The CR is draft. Exact wording awaits explicit owner review; the instruction to reach acceptance is not recorded as approval of newly authored wording. Previous acceptance/results below remain historical for their recorded revisions, including the earlier STV_SHR_057 result; they do not verify this amendment. Current downstream design is not yet reconciled with persistence requirements. No internal concept refinement, product implementation or release is included.

PR #6 carries the reviewable stakeholder increment on cr019-remember-current-view, based on main 3c2647f56898efce1e1b59b261af30f0f905cf61. Authoring checks only: unique stakeholder IDs, draft status and configured model fields checked; Sphinx/traceability validation and runtime verification have not been executed. New stakeholder derivation/test coverage is an explicit downstream gap.

1.1.0 release qualification, 2026-10-25

The owner requested final-GitHub-Release-driven PyPI and documentation publishing, then complete extended qualification before the next release. STV 1.1.0 adds graph reset, visible-area SVG export, independently configurable detail fonts and page-wide Need metadata controls. The PyPI description is included. Issued 1.0.0 artifacts and historical evidence remain unchanged.

Software baseline 41e57ed and final test baseline 3b32d6b are committed. Candidate 4 passed 229 automated cases (187 Python / 42 JavaScript) with no failures or skips, plus a fresh offline Python 3.10 installed-runtime and clean host check. Main qualification uses Python 3.13.17, Windows 11 and Firefox 158.0.1 on file and HTTP. Four 200-node/ten-card SVG checks remain applicable through exact runtime/fixture equivalence; the 30,000-Need/90,000-link host is identity-verified and current browser measurements ran again.

The owner confirmed native Save As/folder selection and cancellation, then readability and keyboard scrolling at 125%/150% browser zoom. Extended reset races, font hierarchy/reuse, real local media/fonts, immutable/event-owned snapshots and host page controls have recorded criterion coverage. Only scoped verification states advance; acceptance statuses and occurrence-mode deferrals remain unchanged.

Candidate 1 is rejected for SVG export omits visible gr... (STV_PR_016), omitted visible graph nodes in SVG export. Candidate 2 fixes it and passes the initial 196 checks. Candidate 3 retains a test-wrapper reporter-format failure; explicit TAP output resolves it in the final test baseline. Candidate 4’s original documentation navigation warnings and corrected strict retests remain visible in the final record.

STV 1.1.0 final qualification is the final local evidence and scope assessment. CI validation and candidate provenance describes exact qualified asset checks, tag/main ancestry, isolated PyPI Trusted Publishing and matching Pages deployment. PR #4 carries the software and evidence. Successful hosted checks remain a gate before merge/tag/publication; live publication status is recorded by GitHub Releases and Actions, rather than inferred from local tests.

Additional OS/browser combinations, mobile/touch optimization, universal SVG editor support and occurrence mode are not formally qualified by this release. The optional cleanup proposal is retained; nothing was deleted. Post-release workspace review remains due when publication completes.

CR015-018 development implementation, 2026-10-25

The owner invoked concept-implementation for accepted baseline 2c4236a on concept-cr015-018. The four CRs now have implemented status: graph collapse keeps current roots/cards, visible-area SVG export uses safe local resources and browser-managed downloads, tooltip/card font scales default independently to 0.7, and host pages have scoped bulk metadata controls. Implementation criterion review and operating limits records actual source/test mappings, checks, artifacts and limits.

The developer check sets include 42 frontend passes, 87 non-browser passes, 57 broad Firefox passes and later targeted retests after edge corrections. Packaging is verified in an isolated offline consumer without Node. The updated behavioral tables and adjacent Draw.io/SVG sources describe the actual command, error/recovery and download-lease states. Runtime product/dependency versions and existing release artifacts remain unchanged; development archives are isolated.

Verification for the new requirements/CRs is partial, not a new release pass. The nine formal case designs remain accepted/not_run pending complete recorded qualification; development pytest/Node checks are identified separately. No new release, deployment, push or implementation commit is authorized by these results. Prior concept/release history below remains historical evidence for its exact artifacts. The working demo is rebuilt locally for owner inspection.

CR015-018 accepted concept, 2026-10-25

The owner requested the concept on a side branch and delegated acceptance of clean artifacts explicitly. Branch concept-cr015-018 preserves creation commit 2e1eace. Round 15: CR015-018 controls and SVG concept records the scoped review, five resolved findings, semantic paths, diagram assessment and exact acceptance inventory. The source identities are in docs/concept-reviews/round-15-inventory.json. Earlier creation-stage pending statements below are historical, superseded only for this reviewed increment.

Accepted internal revisions: STV_SYS_011, STV_SWR_066 through STV_SWR_072, DIRECTIVE/MODEL/DETAIL_BUILD/BUNDLE/STATE/RENDER/INSPECT/EXPORT, ADR011 and STV_TC_SY_066 through STV_TC_SY_069 plus STV_TC_SW_051 through STV_TC_SW_055. This is 25 modeled artifacts and one ADR. Ordinary architecture/interface/plan and picture acceptance is recorded in the inventory without invented statuses. Existing stakeholder acceptance is preserved; CRs remain accepted, not implemented.

The host-icon/ARIA/mixed-state contract, host readiness gate, capture font/resource readiness and zero-area failure policy were tightened. The metadata diagram was re-exported with source-owned label padding; review round 14 was restored to the review index. No current acceptance blocker remains after the final checks. Product implementation is not authorized by review acceptance and is unchanged. New cases remain not_run with no execution records; requirement verification stays not_assessed. Deferred occurrence mode, full-graph export, universal vector editor support and mobile/touch qualification retain their existing boundaries.

Validation: strict fresh Sphinx/publication build, full graph/evidence validation with –require-test-coverage and both CSV exports, published diagram targets, canonical acceptance/result-state assertions and git diff –check passed. All six current diagrams and three containing HTML pages were rendered for visual review; the corrected metadata picture was rechecked separately. Native SVG feasibility remains distinct from unexecuted implementation tests. Implementation handover is Implementation concept and handover and Implementation verification plan; execute the risky offline export slice first.

Creation history: CR015-018, 2026-10-25

The owner explicitly reviewed and accepted Collapse all graph relation... (STV_CR_015) through Page-wide Need attribute co... (STV_CR_018) and Collapse all relationships ... (STV_SHR_058) through Expand or collapse all Need... (STV_SHR_061) on 2026-10-25, then invoked concept creation. Their canonical states are accepted; verification remains not_assessed. The owner also approved browser-managed Save As with documented location-prompt settings. Sources and evidence records the approval and Review and scope decisions the resolved scope. This does not accept later internal drafts or authorize product implementation, staging or committing.

Input identity: prepared stakeholder/CR working-tree revisions based on 633bee2a1fb569f5366bdf6a93ec96ed9fbcb04d. At the owner’s request, work moved to main after a safe fast-forward to 8dbbe79; all uncommitted amendments were retained. Repository: https://github.com/sysblacksmith/STV_sphinx-traceability-view. Prior accepted reviews/ADRs/results retain their historical identities.

The concept adds draft Deliver a standalone visibl... (STV_SYS_011), Reset view-local exploratio... (STV_SWR_066) through Bundle safe export resource... (STV_SWR_072), Visible-area SVG snapshot a... (STV_SWE_EXPORT) and proposed STV_ADR_011: Separate exploration, page metadata and SVG capture. Changed component revisions DIRECTIVE, MODEL, DETAIL_BUILD, BUNDLE, STATE, RENDER and INSPECT reopen to draft/not_assessed because their contracts expand; unchanged GRAPH/LAYOUT and all other accepted requirements remain unchanged. No accepted ADR is superseded. The new SVG path is a companion Draw.io/SVG architecture view with real Need links, not a replacement of the retained core.

Nine canonical cases Reset exploration without l... (STV_TC_SY_066) through Bulk-fold host attributes w... (STV_TC_SY_069) and Reset state, page caches an... (STV_TC_SW_051) through Embed only safe output-loca... (STV_TC_SW_055) cover all new requirements. They are draft/not_run without execution links. Existing relevant offline, security, keyboard, capacity and persistent-detail cases remain regression scope; historical passing executions do not verify this increment. Font configuration, reset/cache semantics, page scope, export crop/resources/save/error contracts, packaging and staged delivery are in Internal interfaces and model contract, Implementation concept and handover and Implementation verification plan.

Feasibility checks: installed Draw.io exported view-export.drawio to its adjacent SVG, and the standard normalizer verified its five linked component targets. Headless installed Firefox opened a standalone SVG fixture combining XHTML foreignObject, styled text, nested scroll clipping and vector line geometry; exit 0 and screenshot inspection confirmed the intended text/clip rendering. The new architecture SVG was also rendered and visually inspected: five arrows have separate routing space, clear labels and no unrelated-box crossings. Temporary fixture/screenshots/profiles remain ignored under docs/_build/concept-feasibility. These are native-API feasibility observations, not product test executions or proof of arbitrary host snapshot fidelity. No new third-party dependency is introduced; primary API limitations are cited in ADR011. Full resource/style/capture integration is the first implementation slice and requires the specified tests before claiming runtime correctness.

Creation-stage checks: the shared validator with –require-test-coverage and –repo-root . passed for the generated increment: 18 CRs, 61 SHRs, 11 SYS, 72 SWR, ten software elements and 124 cases; all 920 historical executions remain unchanged. Complete derivation and test CSV matrices were exported to docs/_build/cr015-018-concept-traceability.csv and docs/_build/cr015-018-concept-test-traceability.csv. A strict Sphinx pass initially identified short heading underlines in newly added sections; these were corrected before the final rebuild. The final strict Sphinx/publication build passed; strict graph/evidence/test coverage and all published diagram links passed on that completed output. The new diagram was inspected both as standalone SVG and embedded in the generated architecture page. Canonical-state checks confirmed accepted stakeholder input, draft/not_assessed internal requirements, and draft/not_run cases with no fabricated executions. git diff --check passed; no source/frontend/package input was changed. No runtime product tests were executed or invented.

The concept has selected ownership, APIs, serialization/resource boundaries, error policies, configuration and staged exit criteria. It is ready for scoped concept review and implementation planning; acceptance remains outstanding. The first export vertical slice must validate full integration fidelity before implementation acceptance. Implementation-ready design does not mean implemented or verified software.

v1.0.0 released

The owner approved PRSA-001 through PRSA-005 remediation and PR015 final presentation on 2026-10-24. See Round 14: Owner acceptance for v1.0.0. Earlier pending-owner statements below are historical and superseded for this exact scope. The owner requests v1.0.0 without visibility-specific release labels. Repository visibility is a separate setting and is unchanged. Runner improvements and hosted hardening are owner-accepted nonblocking deferrals; PRSA-006 remains open. This is a release authorization, not a requirements change request. The owner explicitly confirmed that release intent belongs here, not in the CR register. v1.0.0 was published on GitHub at 22:51:13 Europe/Berlin on 2026-10-24, with annotated tag commit 77d52d82447db434cf5071c820c9a7135fa21caf. All 122 Python and 36 JavaScript tests and final qualification gates passed. The exact wheel/source/checksum assets have verified hosted digests. See v1.0.0 qualification and v1.0.0 release outcome.

PR014 visible viewport boundary fixed

Mark the visible graph boun... (STV_PR_014) is fixed. Round 11: PR014 visible viewport boundary records scoped concept acceptance and PR014 viewport boundary: development verification retains before/ after reproduction, 70 passing development checks and installed asset evidence. The viewport has a fixed thin grey top border while retaining its 975 px client height and existing clipping/navigation. The normal demo is rebuilt. No graph, layout, state, dependency or version changes; no new capacity/release claim.

CR_013 classified evidence rows implemented

STV_CR_013: Vertical target levels for artifacts and test records is implemented with nine target rows and the owner’s labelled fallback row. Round 10: CR_013 classified evidence rows records the accepted concept and implementation re-review; CR_013 classified evidence rows: development verification retains 134 latest passing tests, including real Firefox file/HTTP and both 30,000-record classification and 200-visible-node capacity checks. Four new canonical case designs have actual aggregate executions. Existing legacy models, source-free wheel consumption, endpoint routing and PR013 stability passed regression. The project demo uses the new classified model. Release qualification remains a separate owner-started activity; unrelated security/hosted gates stay open.

PR013 stable navigation finalized

Keep node positions stable ... (STV_PR_013) is fixed. Round 9: Stable navigation concept and implementation handover records the scoped accepted concept, partial ADR supersession and test-design re-review. PR013 final development verification retains 111 distinct latest passing component, integration, Firefox file/HTTP, capacity and clean-package outcomes. Six new accepted test designs cover stable slots, negative SVG bounds and natural initial order. Fresh centering remains separately verified. Two initial placeholder visibility assertions failed; explicit viewport fitting corrected the test procedure and both retests passed without product changes.

Ordinary x slots and the clicked band stay fixed during group/root navigation; other bands can move for height and shared tests can change associated ranks. The normal documentation/demo is rebuilt. This completes the development fix, not a release; the canceled candidate stays canceled and the next release requires the owner’s explicit instruction. Unrelated PRSA gates remain below.

PRSA-006 local preparation; hosted hardening pending

Limited automated validatio... (STV_PR_012) remains analyzed with partial verification. Pinned CI and manual provenance workflows, checksum generation and an unapplied protection profile are prepared. CI validation and candidate provenance defines their trust boundary and PRSA-006 CI and provenance preparation retains local validation. GitHub’s private-plan restriction prevents rulesets; hosted runs, attestations and chosen protections remain unconfirmed. New/refined workflow and case designs await owner review. No release or remote setting change is performed.

PRSA-005 clean publication remediation

Incremental output retains ... (STV_PR_011) records the authorized fresh-tree publication fix and PRSA-005 clean documentation publication verification retains Sphinx cleanup and failure preservation/rollback evidence. Only the inventoried docs/_build/html tree is a publication input; previous output and diagnostics remain outside it. The revised workflow/interface and new case designs await owner review. Requirement verification is unchanged and no release is started.

PRSA-004 source archive remediation

Source archives include exe... (STV_PR_010) records the authorized source-archive boundary fix. PRSA-004 source archive boundary verification retains the before-fix leaked-log reproduction, passing actual-archive regression and offline rebuilt-wheel host check. The revised packaging policy and new test design await owner review; requirement verification is unchanged. No release is started.

PRSA-001 and PRSA-003 remediation

The owner authorized historical licensing remediation and patched maintainer tooling environments. Historical distributions om... (STV_PR_008) and Build and test environments... (STV_PR_009) record scope, implementation and checks. Historical distribution license supplement supplies the historical supplement without changing archive bytes or Git history. Historical licensing and toolchain remediation records development compatibility checks and current advisory results. The package runtime remains Python 3.10+; documentation/test tooling requires Python 3.11+. Changed tooling documentation, the supplement, new cases and refined offline bootstrap procedure await owner review. No release is started.

PRSA-002 security fix awaiting owner review

The owner authorized remediation of the detail transport-marker bypass. Authored detail transport a... (STV_PR_007) links the affected interface and regression evidence in PRSA-002 development fix verification. New test designs and the interface refinement await owner review. Prior acceptance history is retained; these scoped development checks do not qualify a release or change requirement verification fields. Later audit findings await individual proposal approval.

Release canceled; maintenance fixes accepted

The owner canceled the release preparation and requested the underlying fixes, version centralization, regression tests and acceptance review before another release begins. See STV_CR_012: Cancel release and close preparation findings and Canceled release preparation. The sole maintained version is now in src/sphinx_traceability_view/_version.py and identifies development work. No replacement release is started.

The Windows-path report Detail tooltips fail on lon... (STV_PR_006) is fixed at its scoped regression level. The pinned ELK compiled-dependency notice audit is complete; ADR 007, the two inspector cases and the new path/build-guard case designs are accepted under Round 8: Maintenance acceptance review. Latest development outcomes are 79 passing distinct cases (59 Python, 20 JavaScript); two capacity cases await future release qualification. Existing requirement verification is not promoted.

Maintenance regression evidence retains before/after Windows path evidence, development regressions and the dependency audit. Round 8: Maintenance acceptance review records the scoped acceptance review. Historical release verification is preserved and does not qualify the changed inputs.

1.0.0 release preparation, 2026-10-24

The owner requested the first official GitHub release based on commit 2960b25721df9eb727ae070317e4c2f4746bb909. Version metadata is aligned at 1.0.0. The fresh 1.0.0-candidate-1 execution records 78 passing executable cases (58 Python, 20 JavaScript), no failures/errors/skips, Windows/Firefox file and HTTP capacity runs, isolated installed-wheel use, artifact checksums and all supporting gates. All actual cases have new execution links; prior attempts and acceptance states remain preserved.

1.0.0 readiness assessment records incomplete final qualification: the nested Windows-path system case remains unexecuted, ADR 007 and two inspector test designs still need acceptance review, and the documented ELK/GWT redistribution audit remains open. Requirement verification states are unchanged. Occurrence mode and other agreed limits remain visible. No release commit, tag or publication is implied. The owner approved removal of the 14 listed cache directories; all were removed. The post-release review remains due when publication is known.

Component source organization, 2026-10-24

The owner requested direct software-element-to-code boundaries. The nine existing elements now own matching component directories with sources, unit tests and boundary READMEs; Software elements records the naming convention. Cross-component checks remain in Executable test scripts. The public extension setup and generated asset locations remain stable.

STV_CR_008: Trace software elements to component code and tests records scope, path migration and actual development verification. The source-organization ADR (STV_ADR_007: Architecture-owned component directories) and two new inspector case designs were initially proposed/draft; their scoped acceptance is now recorded in round 8. This refactor does not update requirement verification or supersede historical release execution results.

Requirement filenames and test levels, 2026-10-24

The owner requested explicit requirement filenames and a system/software split of test specifications. See STV_CR_009: Requirement filenames and verification levels. Canonical requirement/test IDs, criteria, latest results and historical execution records are retained. System test cases contains whole-tool checks; Software test cases contains component checks. This organization does not infer new verification results or acceptance.

MIT licensing decision, 2026-10-24

The owner selected MIT and supplied Henning Heikes as the copyright holder. See Licensing and STV_CR_011: MIT license and author attribution. The repository license, package metadata and generated-view legal materials are aligned. Third-party licenses remain separate; an ELK/GWT transitive-source redistribution audit and employer/IP questions are not claimed resolved. Historical release artifacts and verification states remain unchanged.

Current release increment

Method migration and requalification, 2026-10-19

The owner requested migration to the shared test-case/execution model followed by release qualification. Round 7: Test-case and execution traceability migration accepts 81 concrete case designs, covering all 120 requirements structurally. Seventy-six have existing executables; four occurrence-mode procedures and the known long-path regression remain planned and unexecuted. Existing requirement and architecture acceptance is preserved. The shared method now resolves from the renamed the historical tooling repository repository.

This migration changes documentation and records. Product code is unchanged. The known nested-Windows detail-loading report Detail tooltips fail on lon... (STV_PR_006) remains analyzed and outside this migration’s implementation scope. A passing existing suite must not be described as resolving that report’s acceptance criteria. The requested full rerun passed all 76 executable cases (58 Python/browser and 18 JavaScript), with no failures/errors/skips, under Windows/Firefox 158.0 and Python 3.10.9. See 0.2.0-method-2 execution; the first attempt and its corrected documentation assertions remain retained separately.

There are 152 new per-case execution records. All 76 executable cases now have last_result: passed; the four later-mode cases and the known long-path regression remain not_run. The freshly rebuilt capacity fixture contains 30,000 Needs and 90,000 edges. Its unchanged identity was verified before reuse for the rerun; both browser transports were exercised again.

Current verification for Deliver a self-contained do... (STV_SYS_003), Provide original-object ins... (STV_SYS_006), Publish full rendered details (STV_SWR_015), Avoid runtime network loading (STV_SWR_017) and Use portable output URLs (STV_SWR_018) is partial because the known nested-path detail-loading gap remains. Eight other system and 50 delivered software requirements retain their passing disposition; four later software requirements remain not_assessed. Requirement acceptance and historical qualification evidence are preserved. Passing regression and method gates do not establish new product-release readiness while this issue is open.

Prior v0.2.0 qualification

The owner approved the centered-layout and interactive-seed MVP and released its stakeholder requirements on 2026-10-18. Concept review is complete in Concept review round 6: accepted centered-layout and seed-selection amendment: revised/new stakeholder requirements 003/047/052/053, software requirements 003/051/052/056/057, ADR 006 and their affected contracts/diagrams are accepted. ADR 005 is partially superseded; previous review snapshots remain historical. See Centered parents and interactive seed selection.

Full v0.2.0 qualification passed against candidate 5: 58 Python/browser and 18 JavaScript tests, with no failures/errors/skips, plus all packaging, documentation, coverage, traceability and diagram gates. See v0.2.0 final release validation and Implementation criterion review and operating limits. A collision defect found during release review is corrected and regression-tested; new-tab navigation tests now wait for the actual destination. Ten system and 53 delivered software requirements are verified passed; four occurrence-mode requirements remain not_assessed. Acceptance statuses are preserved. The candidate is validated for owner release decision; external distribution still requires the existing project-license decision. No publication is implied.

The owner approved the preceding usability stakeholder revisions on 2026-10-18 and delegated review and final implementation for v0.2.0. That internal concept was accepted under Concept review round 4: v0.2.0 implementation release; the subsequent amendment has its own acceptance under round 6 and final verification in the record above. See Draft usability problem resolution and Problem Tickets. User issue handover now uses first-class problem reports directly in docs/problem-tickets/; the shared lifecycle/template update is recorded in Problem-report model and folder handover. The fifth report’s control-order fix is included; see Draft relationship-control ordering. Final verification remains independent of concept acceptance; the previous smoke-only limit is superseded.

Previous baseline

Stakeholder baseline v1 and its explicitly recorded scope amendments are owner-accepted. The internal concept, including the starting-node amendment, is accepted under owner-delegated concept review, rounds 1 through 3. ADRs 001, 002, 004 and 005 are current accepted decisions; ADR 003 is partially superseded by ADR 005 with its unaffected choices retained. Findings STV_REVIEW_001 through STV_REVIEW_009 are resolved. See the individual review records for assessed Need links, authority, revision identities and evidence.

The owner accepted the starting-node stakeholder amendment and selected paged project-root links. Concept refinement and round-3 review are complete; see Starting-node requirement amendment and Concept review - round 3: starting nodes. The requirements and elements in that historical baseline were accepted. Historical review hashes remain snapshots of their respective revisions.

The initial shared-identity MVP is implemented from clean input revision 30aaba98776ecbe648558d278a985691d81bccb4 under the owner’s implementation instruction on 2026-10-18. It includes the installable extension, offline classic-script bundle, multiple seeds, paged project roots, semantic layout, rich static details, original links and independent accessible viewports.

The stable candidate’s executable suites passed. Its publication-only documentation retest passed; the consolidated record is Initial MVP consolidated verification. Initial system/software verification fields are updated against those actual results and the criterion review in Implementation criterion review and operating limits. Stakeholder verification and concept acceptance remain independent; no owner release approval or external publication is implied. Project licensing was subsequently resolved as MIT on 2026-10-24 (see Licensing); numeric performance budgets remain explicitly deferred; separate-occurrence mode, touch and additional platforms are later scope. Implementation checks are specified in Implementation verification plan; scope decisions and their original owner evidence remain in Review and scope decisions and Sources and evidence.

Review and lifecycle records

• Concept review records
  • Concept review - round 1
  • Concept review - round 2
  • Concept review - round 3: starting nodes
  • Concept review round 4: v0.2.0 implementation release
  • Concept review round 5: centered-layout and seed-picker MVP
  • Concept review round 6: accepted centered-layout and seed-selection amendment
  • Round 7: Test-case and execution traceability migration
  • Round 8: Maintenance acceptance review
  • Round 9: Stable navigation concept and implementation handover
  • Round 10: CR_013 classified evidence rows
  • Round 11: PR014 visible viewport boundary
  • Round 12: Persistent per-view details
  • Round 13: Detail acceptance corrections
  • Round 14: Owner acceptance for v1.0.0
  • Round 15: CR015-018 controls and SVG concept
  • CR019 scoped concept review, round 16
• Round 14: Owner acceptance for v1.0.0
  • Authority and boundary
  • Accepted scope
  • Exclusions and release gates
• Documentation organization and migrated history
  • Migrated ADR lifecycle history
  • Migrated readiness and validation notes
  • Implementation readiness and validation gates
  • Post-relocation artifact identities
• Implementation criterion review and operating limits
  • Scope and authority
  • System criterion assessment
  • Software criteria and transition review
  • Integration decisions within the accepted contracts
  • Operating limits and deferred decisions
  • Record integrity
  • v0.2.0 criterion assessment
  • CR014 development criterion review
  • PR015 detail acceptance correction review
  • CR015-018 development implementation, 2026-10-25
  • CR019 remembered views

Maintenance rule

Record project progress and maturity changes here. Give each concept-review round its own RST file with linked assessed Needs and document/ADR references, findings, decisions and check evidence. Preserve prior rounds as historical snapshots. Artifact files contain their specification/design and canonical status; do not append per-review progress paragraphs, review evidence to every Need, or manually repeated status/count summaries throughout the site. Review-only updates touch these central records; edit an artifact only when its content, traceability, origin evidence or canonical status actually changes.

Implementation verification dashboard

The table reads canonical fields; deferred occurrence-mode criteria remain not_assessed. Executable definitions and results are linked from Executable requirement coverage and Initial MVP consolidated verification.

ID	Title	Verification State	Tags
STV_SWR_001	Register the RST entry point	passed	release_initial
STV_SWR_002	Resolve seeds after collection	passed	release_initial
STV_SWR_003	Initialize collapsed state	passed	release_initial
STV_SWR_004	Expose plus controls	passed	release_initial
STV_SWR_005	Expand complete target groups	passed	release_initial
STV_SWR_006	Traverse without depth cutoff	passed	release_initial
STV_SWR_007	Collapse relationship groups	passed	release_initial
STV_SWR_008	Render fixed node summaries	passed	release_initial
STV_SWR_009	Order requirement ranks	passed	release_initial
STV_SWR_010	Insert system architecture rank	passed	release_initial
STV_SWR_011	Place software architecture rank	passed	release_initial
STV_SWR_012	Place classified test evidence in its resolved rows	passed	release_initial
STV_SWR_013	Index both trace directions	passed	release_initial
STV_SWR_014	Normalize replacement mappings	passed	release_initial
STV_SWR_015	Publish full rendered details	passed	release_initial
STV_SWR_016	Open canonical object links	passed	release_initial
STV_SWR_017	Avoid runtime network loading	passed	release_initial
STV_SWR_018	Use portable output URLs	passed	release_initial
STV_SWR_019	Offer occurrence mode later	not_assessed	release_later
STV_SWR_020	Use shared identity initially	passed	release_initial
STV_SWR_021	Retain state across later mode changes	not_assessed	release_later
STV_SWR_022	Key later expansions by occurrence	not_assessed	release_later
STV_SWR_023	Project later shared expansion union	not_assessed	release_later
STV_SWR_024	Close repeated paths safely	passed	release_initial
STV_SWR_025	Compute seed-rooted visibility	passed	release_initial
STV_SWR_026	Report invalid invocation seeds	passed	release_initial
STV_SWR_027	Tolerate host broken traces	passed	release_initial
STV_SWR_028	Create missing-target nodes	passed	release_initial
STV_SWR_029	Indicate empty adjacency	passed	release_initial
STV_SWR_030	Resolve type palette	passed	release_initial
STV_SWR_031	Apply acceptance borders	passed	release_initial
STV_SWR_032	Normalize accepted values	passed	release_initial
STV_SWR_033	Constrain and retain details overlays	passed	release_initial
STV_SWR_034	Provide keyboard interaction	passed	release_initial
STV_SWR_035	Label directional controls	passed	release_initial
STV_SWR_036	Reject invalid model entries	passed	release_initial
STV_SWR_037	Honor resolved declared level ordering	passed	release_initial
STV_SWR_038	Scope state to view roots	passed	release_initial
STV_SWR_039	Implement view-local zoom	passed	release_initial
STV_SWR_040	Implement view-local pan	passed	release_initial
STV_SWR_041	Verify Firefox on Windows	passed	release_initial
STV_SWR_042	Package for the pinned toolchain	passed	release_initial
STV_SWR_043	Enforce visible occurrence capacity	passed	release_initial
STV_SWR_044	Reject over-limit transitions atomically	passed	release_initial
STV_SWR_045	Reuse canonical host definitions	passed	release_initial
STV_SWR_046	Expose an installable entry module	passed	release_initial
STV_SWR_047	Inspect external Needs without local full content	passed	release_initial
STV_SWR_048	Respect host-hidden Need objects	passed	release_initial
STV_SWR_049	Preserve static third-party widget content in details	passed	release_initial
STV_SWR_050	Separate transient hover and explicit persistent details	passed	release_initial
STV_SWR_051	Provide the artificial project entry node	passed	release_initial
STV_SWR_052	Page stakeholder entry links	passed	release_initial
STV_SWR_053	Prefer direct facing-edge routes	passed	release_initial
STV_SWR_054	Set enlarged standard viewport	passed	release_initial
STV_SWR_055	Order controls using target semantic levels	passed	release_initial
STV_SWR_056	Center parent boxes with collision-aware semantic placement	passed	release_initial
STV_SWR_057	Confirm local interactive seeds and restore project overview	passed	release_initial
STV_SWR_058	Stabilize committed navigation geometry	passed	release_initial; navigation_stability
STV_SWR_059	Render complete edge bounds at any graph origin	passed	release_initial; navigation_stability
STV_SWR_060	Use natural ID order for fresh unexpanded rows	passed	release_initial; navigation_stability
STV_SWR_061	Resolve configurable per-object placement at build time	passed	release_initial; classified_rows
STV_SWR_062	Mark the viewport clipping edge	passed	release_initial; viewport
STV_SWR_063	Own a per-view persistent detail collection	passed	release_initial; persistent_details
STV_SWR_064	Present and focus persistent detail boxes	passed	release_initial; persistent_details
STV_SWR_065	Validate and publish the persistent details limit	passed	release_initial; persistent_details
STV_SWR_066	Reset view-local exploration to current roots	passed	change_increment
STV_SWR_067	Validate and serialize independent detail font scales	passed	change_increment
STV_SWR_068	Scale copied detail typography once per presentation	passed	change_increment
STV_SWR_069	Control rendered page metadata through scoped bulk actions	passed	change_increment
STV_SWR_070	Capture a clipped inert visible-area SVG snapshot	passed	change_increment
STV_SWR_071	Save and release SVG downloads without changing exploration	passed	change_increment
STV_SWR_072	Bundle safe export resources for offline snapshots	passed	change_increment
STV_SWR_073	Store opt-in snapshots independently	passed	feature_view_persistence
STV_SWR_074	Validate and reconstruct remembered exploration	passed	feature_view_persistence
STV_SWR_075	Restore presentation without startup interference	passed	feature_view_persistence
STV_SYS_001	Author and resolve embedded views	passed	release_initial
STV_SYS_002	Integrate the host data model	passed	release_initial
STV_SYS_003	Deliver a self-contained documentation bundle	passed	release_initial
STV_SYS_004	Expose the complete host trace graph	passed	release_initial
STV_SYS_005	Preserve semantic layout	passed	release_initial
STV_SYS_006	Provide original-object inspection	passed	release_initial
STV_SYS_007	Isolate view sessions	passed	release_initial
STV_SYS_008	Bound exploration of large projects	passed	release_initial
STV_SYS_009	Deliver the reusable extension	passed	release_initial
STV_SYS_010	Support the initial execution platform	passed	release_initial
STV_SYS_011	Deliver a standalone visible-area SVG without a runtime service	passed	change_increment

CR014 persistent details

The owner accepted the persistent per-view details amendment and clarified reuse, lifetime and configurable capacity. Concept round 12 and ADR 010 are accepted. The implementation passes all 156 distinct executable checks, including file/HTTP default/override capacity, loading races and the rebuilt 30,000-record capacity fixture. The fresh wheel/source distribution passes clean-consumer checks. See CR014 persistent details: development verification for actual attempts, criterion review, source identity and retained failures. No release is started; unrelated draft designs, occurrence-mode deferral and publication gates retain their existing states.

PR015 detail acceptance corrections

The owner reported narrow boxes, inert/unfolded metadata controls and a copied artifact-ID link returning to the view. Correct detail readability,... (STV_PR_015) records the causes and fix. Round 13 accepts the scoped design correction and regression case; PR015 detail acceptance corrections: development verification retains the failing baseline and 127 passing distinct development checks. The dock is now 720 px, copied metadata starts folded and toggles accessibly, and header IDs open actual source Needs. Owner acceptance retest is pending. Capacity and release qualification remain outside this correction; earlier results remain historical.

The PR015 pane-frame follow-up marks the open dock’s full boundary with a thin grey line and removes card shadows. Ten affected Firefox file/HTTP procedures pass; the current normal demo is rebuilt for owner retest. This CSS-only change does not imply a new full regression, capacity or release qualification.

Independent method tooling, 2026-10-25

The owner requested independent publication and authorized implementation of a portable method package and explicit import workflow. STV now keeps method package 1.0.0, including its model, charts, CSS and validators, under tools/method. Documentation and release tools resolve only local files; no skill registration or separate tooling checkout is a build requirement.

This is a documentation/tooling migration. It does not change product requirements, canonical IDs, acceptance flags, verification states or historical execution results. Importer regression checks and existing graph-validator checks passed in the cloud. Full Sphinx, package and Windows/browser qualification are not claimed by those checks; PR CI records the applicable build results. Historical raw attachments remain in the checkout and are excluded from the public website, as described in CI validation and candidate provenance.

Note

The documentation/tooling restructuring took place in commit a807a1b8300151fc1dfc2e64a792d24a48d46f38. Earlier documentation can be found in Git history.

Additional browser smoke check, 2026-10-25

The owner reported a minimal manual STV smoke test using Microsoft Edge. This provides additional browser confidence; browser/OS versions and individual procedures were not recorded. It does not extend the formal release qualification or establish full Edge coverage.