lantern

poke-test-fixture

Test Fixture

Introduction

This is some introductory text.

Config

database:
  host: localhost
  port: 5432
settings:
  debug: false
  timeout: 30

JSON Data

{
  "users": [{"name": "alice"}],
  "settings": {"enabled": true, "count": 10}
}

Notes

Some notes here.

Documentation

Initial documentation content.

Level 2

Content at H2.

Level 3

Content at H3.

Level 4

Content at H4.

Level 5

Content at H5.

Another Section

Nested Here

Deeply Nested

Some deep content.

Single Fence

Section with exactly ONE data fence for DWIM auto-resolution testing.

count: 42
name: single-fence-test
nested:
  value: deep-value

Multi Fence

Prose content before fences. This section has multiple fences to test ambiguity detection and explicit addressing.

item: first-yaml
priority: 1
item: second-yaml
priority: 2
{
  "count": 100,
  "type": "json-fence"
}

More prose after fences.

Labeled Fences

Section with labeled fences for label-based addressing.

host: localhost
port: 8080
host: backup.local
port: 9090
# Labeled python fence
result = "labeled-script"

Provenance

Document

  • Status: 🔴 Unverified

Fences

poke-test-fixture-config-fence-0

  • Status: 🔴 Unverified

poke-test-fixture-json-data-fence-0

  • Status: 🔴 Unverified

poke-test-fixture-documentation-fence-0

  • Status: 🔴 Unverified

poke-test-fixture-single-fence-fence-0

  • Status: 🔴 Unverified

poke-test-fixture-multi-fence-fence-0

  • Status: 🔴 Unverified

poke-test-fixture-multi-fence-fence-1

  • Status: 🔴 Unverified

poke-test-fixture-multi-fence-fence-2

  • Status: 🔴 Unverified

poke-test-fixture-labeled-fences-fence-0

  • Status: 🔴 Unverified

poke-test-fixture-labeled-fences-fence-1

  • Status: 🔴 Unverified

poke-test-fixture-labeled-fences-fence-2

  • Status: 🔴 Unverified